CLI Telemetry Privacy

When you opt in during first-run setup, the CLI sends anonymous error reports containing:

• CLI version, operating system, and Python version
• Error messages and stack traces (sanitized — file paths and secrets are stripped)
• Command name and exit code
• A hashed installation identifier (SHA-256 of a local UUID — not reversible to your identity)

The CLI never sends:

• Source code, prompts, file contents, or diffs
• Git commit data, branch names, or repository URLs
• Personal information (name, email, IP address)
• AI-generated code or conversation transcripts

Before leaving your machine, every event is sanitized: file paths are removed, tokens and secrets are redacted, and your installation ID is hashed with SHA-256. The server receives only the sanitized payload — it cannot reconstruct your file system layout or identify you personally.

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.

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.

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.

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

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.