# Telemetry: what is sent, how to disable. Dimmy Help.

> Telemetry: what is sent, how to disable. Step-by-step help for Dimmy, the native voice dictation app for macOS, Windows, and Linux.

Source: https://dimmy.app/help/telemetry/

[← Back to Help center](https://dimmy.app/help/)

History & Privacy

# Telemetry: what's sent, how to disable

Off until you say yes. Event names and numbers only, never audio, never text, never API keys. Two separate switches.

At first launch Dimmy asks whether it may send usage statistics and crash reports. Nothing is sent until you say yes, and each has its own switch. Two destinations, both in EU data centres: PostHog EU for usage statistics, Sentry EU for crash reports. Events are linked to a random installation ID, so they are pseudonymous, not anonymous. Versions up to 0.7.13 started with both switches on.

## 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](https://dimmy.app/help/use-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.

## Turn it on or off

1. Open Settings → Privacy.
2. Send anonymous usage data: on sends usage events to PostHog, off stops them.
3. Send crash reports: on sends crash reports to Sentry, off stops them.
4. Both take effect immediately. Already-sent events cannot be recalled; write to us to have them deleted.

Settings → Privacy with the two telemetry toggles

## 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](https://dimmy.app/privacy) for the full breakdown.

info

Want even more detail? The [Privacy policy](https://dimmy.app/privacy) lists every event name with what it carries, mirrored from the Rust source.

Was this helpful? 

## In this category

[ History & PrivacyBrowse and search your historyEvery transcription is saved locally and searchable with full-text. Stats show count, time saved, words dictated.](https://dimmy.app/help/history-search/)

Last updated: 2026-05-22

On this page

1. [01 What we send](#what-we-send)
2. [02 What we never send](#what-we-never-send)
3. [03 Turn it on or off](#turn-it-on-or-off)
4. [04 Audit it yourself](#audit-it-yourself)