#dataEvery section below corresponds to specific code paths in the Rust core. The full list of events and their payloads is below.
A random UUIDv4 generated on first launch, stored locally in ~/.config/dimmy/analytics_id (or %APPDATA%\dimmy\analytics_id on Windows). It only exists to de-duplicate "1 user did X 5 times" from "5 users each did X once". Reset it any time from Settings → Privacy → Reset anonymous ID. It is never linked to anything that could identify you.
A fresh UUIDv4 generated on each app launch, not persisted. Lets us answer questions like "how many transcriptions per session?" without tracking open or close events.
Attached to every event:
app.startedWhen the app launches. Includes cold-start time in milliseconds.app.session_endedWhen the app closes. Includes total session duration (seconds) and number of transcriptions in the session.transcription.completedWhen a transcription succeeds. Path (local whisper.cpp vs cloud provider), provider category (groq / openai / anthropic / gemini / deepgram / openrouter / local: only the tag, never the URL or API key), audio duration in seconds, processing time in milliseconds, word count (the number only, never the words), language ISO code (e.g. en, it), whether filler removal ran (boolean), whether LLM post-processing ran (boolean).transcription.failedProvider category and error category (e.g. 401, timeout).transcription.cancelledAudio duration up to the cancel.llm.appliedProvider category, style name, tone name, processing time. Never the prompt. Never the output.llm.failedProvider category and error category.When you change any of these in Settings, we log that the change happened. For free-text fields we never log the value, just that something changed.
feature.hotkey_triggeredWhen the global hotkey starts a recording. Helps us understand whether people prefer hotkey or button.feature.api_key_setWhen you save an API key, we log the scope (stt / llm) and the provider category. The key itself never leaves your machine.perf.startup_msCold-start duration in milliseconds.perf.gpu_statusOn each launch: which GPU backend was compiled (vulkan / cuda / metal / cpu), whether the previous launch crashed during GPU init, whether a sticky known-bad marker is set.error.gpu_crashOnly on the launch immediately after a GPU crash: which backend, which call site (e.g. whisper_load: <path>, with paths scrubbed).Atomic increment operators on a small set of cumulative per-user counters. They let us segment active users from users who installed but never tried it, without scanning every event.
Attached to your anonymous-ID record so dashboards can build cohorts and retention curves.
When the app crashes or hits an error path, we send to Sentry EU:
The Settings → Send feedback form goes to Sentry as a tagged message. The text you type is included verbatim. The email field is optional and only included if you explicitly type it. We never auto-fill it from anywhere.
There is no telemetry path in the codebase that sends any of the following. Audit the source if you want to verify, every send site is logged with [telemetry] in the local log.
Two destinations, both hardcoded in the binary, both in EU data centres, both GDPR-aligned.
Anonymous usage events. The endpoint is hardcoded and cannot be overridden at runtime.
Stack traces, error messages (truncated and secret-redacted), and the optional text you submit through the Feedback form.
We control both projects. Only the Dimmy team can read the data.
Every telemetry call is logged locally. Open the log file and look for lines starting with [telemetry].
Example of what you'll see in the log:
[2026-05-11 09:47:06] [telemetry] track event=transcription.completed [2026-05-11 09:47:06] [telemetry] spawn send for event=transcription.completed (payload 275 bytes) [2026-05-11 09:47:06] [telemetry] send: HTTP 200 OK (sent=4)
You can also confirm the PostHog and Sentry project keys embedded in the build: search for key-diag in the same log. The prefix is logged once per process, so you can verify we're sending to the project we claim and nowhere else.
Want to start fresh? Settings → Privacy → Reset anonymous ID rotates your per-install UUID.
Material changes are announced in the release notes. The ground truth lives in PRIVACY.md inside the app repository. Run git log PRIVACY.md to see the full history of changes.
Questions, deletion requests, or anything else: [email protected]. Security issues: [email protected].