Skip to content
Iria Monitor

CLI Telemetry Privacy

What the Iria Monitor command-line tool collects and how we handle it.

What we collect

When you opt in, the CLI sends diagnostic reports and periodic health diagnostics containing:

  • CLI version, available build revision, report origin, operating system, and Python version
  • Reviewed technical messages, exception types, error codes, fingerprints and Iria module/function/line frames without source lines or local variables
  • Known command and operation names, HTTP route/status, numeric failure details, counts, collection and delivery health, last-success times and recovery, and update choices and outcomes for aggregate statistics
  • A stable pseudonymous installation identifier, the SHA-256 hash of a random local UUID, used to count affected installations and recurring failures. Explicit synthetic tests also include a temporary random test-run identifier.

What we do NOT collect

Automatic diagnostic report payloads exclude:

  • Source code, prompts, file contents, or diffs
  • Your repositories' commit data, branch names and repository URLs; full filesystem paths and unrestricted URLs
  • Device tokens, provider account identities, raw command arguments, arbitrary subprocess output and unrestricted context
  • AI-generated code or conversation transcripts

How data is processed

The CLI filters reports before recording them locally and again before sending. The relay validates the fields again, including encoded context. Reports use bounded technical fields and omit unknown free text. A stable SHA-256 hash of a random installation UUID links recurring reports from the same installation. This is pseudonymous data, not guaranteed anonymous data. Diagnostic requests do not attach a device token or provider account identity and do not require SaaS login. As with any network request, the receiving infrastructure can see the source IP address.

Legal basis

We rely on your explicit consent (GDPR Art. 6.1.a). Telemetry is off by default. During first-run setup, the CLI asks whether you want to opt in. If you decline, no data is sent and no local events are recorded going forward.

Data retention

On your machine: unsent events are automatically deleted after 7 days. If you decline consent, all local data is purged immediately.

On our servers: telemetry data is retained for 90 days, then permanently deleted.

How to opt out

You can disable telemetry at any time by running:

iria-monitor config set telemetry_enabled false

This stops both local recording and server transmission immediately.

Data deletion requests

To request deletion of telemetry data associated with your installation, contact us at hello@iria.tech.

Changes to this policy

We may update this page to reflect changes in what we collect or how we process it. Each telemetry payload includes the CLI version, so we know which version of this policy was in effect when you consented.