Telemetry: what's sent, how to disable

Dimmy ships with anonymous opt-out telemetry. Two destinations, both in EU data centres, both GDPR-aligned: PostHog EU for usage analytics, Sentry EU for crash reports. Each one has its own toggle.

What we send

• App version, OS, CPU architecture.
• Event names (app.started, transcription.completed, llm.applied, ...).
• Numbers and durations (audio length in seconds, processing time in ms, word count).
• Provider category tags (local, groq, openai, ...) but never the URL, never the API key.
• Which transcription engine ran, as a category tag on transcription.completed (batch, deepgram_stream, local_stream, chunked_caption).
• model.download_completed: which kind of local model finished downloading (whisper, llm, parakeet) and whether it succeeded. Never the model path or filename.
• consent.logged: which step the meeting recording-consent gate reached (shown, accepted, cancelled, announced, declined), so we can measure drop-off. Never the participant names, the spoken announcement, or any meeting content. Ties to meeting recaps.
• Crash stack traces (truncated and secret-redacted).

What we never send

• The audio you record.
• The text of any transcription.
• Any prompt or LLM output.
• API keys, even in error messages.
• Your IP, hostname, or username.
• File paths beyond a categorical tag.

Disable it

1. 1Open Settings → Privacy.
2. 2Toggle Send anonymous usage data off (stops PostHog).
3. 3Toggle Send crash reports off (stops Sentry).
4. 4Both take effect immediately. Already-sent events cannot be recalled.

Audit it yourself

Every telemetry call is logged locally with [telemetry] prefix. Open your Dimmy log file and grep for [telemetry] to see exactly what was sent and when. See Privacy policy for the full breakdown.