Telemetry and privacy

Where your data goes

WIRE runs entirely inside your Snowflake account. Work items, agent results, and configuration stay in your account, and AI calls go to Snowflake Cortex under your account's Cortex terms. Your existing governance controls apply to everything WIRE reads and writes.

Telemetry is off by default

WIRE doesn't require an event table and doesn't share telemetry unless you opt in. All four of its telemetry event definitions, ERRORS_AND_WARNINGS, USAGE_LOGS, TRACES, and DEBUG_LOGS, are optional.

Opt in to share diagnostics

If Evolution Analytics is helping you diagnose a problem and asks for diagnostics, you can opt in:

USE ROLE accountadmin;

-- One time, if the account doesn't have an event table yet
CREATE EVENT TABLE my_db.my_schema.wire_events;
ALTER ACCOUNT SET EVENT_TABLE = my_db.my_schema.wire_events;

GRANT MANAGE EVENT SHARING ON ACCOUNT TO ROLE wire_sysadmin;

ALTER APPLICATION wire_native_app SET SHARE_EVENTS_WITH_PROVIDER = TRUE;

To stop sharing, set SHARE_EVENTS_WITH_PROVIDER = FALSE.

Health status

Separately from telemetry, WIRE reports a single health status, OK, PAUSED, or FAILED, when an agent run finishes and when the Configuration app loads. It uses Snowflake's built-in SYSTEM$REPORT_HEALTH_STATUS. It carries no data about your account, queries, or records: only one of those three words and when it was reported.

Snowflake limits it to one report every 55 minutes and keeps only the most recent value.