The three states of your data
1. Local. Nothing leaves.
Out of the box, Dimmy transcribes on your machine with local models (Whisper, Parakeet) and can rewrite with a local LLM. During dictation, audio stays in memory and is not written to disk. No account, no API key, works offline. Your words never reach us, or anyone: there is no Dimmy server involved. For your dictated content, we are not in the loop at all.
2. Anonymous telemetry. Numbers, never words.
To fix crashes and understand usage we send anonymous event names and numbers (counts, durations, error categories) to servers in the EU. Never audio, never text, never prompts, never API keys. IP addresses are discarded, not stored. Two independent toggles turn it off in Settings. The full event-by-event list, with payloads, is on the privacy page.
3. Cloud, if you choose it. With your key.
You can plug in a cloud provider for faster or fancier models, with your own API key or your own subscription. Then, and only then, your text or audio travels: directly from your computer to that provider, never through us. Which provider sees your words is your choice, so we tell you exactly what each one can do with them. That's the table below. The same applies to any integration you switch on: enabling it sends the relevant content (for example a recap to Notion) to that service, and to no one else.
If you use your own key: who can train on your words?
Checked on the providers' official documentation, July 2026. Policies change: re-check before sending anything sensitive. "No" means the provider states it does not use API data to train its models by default.
| Provider | Trains on your data? | Worth knowing |
|---|---|---|
| OpenAI API | No | No training on API data by default. Different product from consumer ChatGPT. |
| Anthropic API | No | No training by default. |
| Groq | No | No training; zero-data-retention available in the console. |
| Deepgram | No | Trains only via its Model Improvement Program. Standard API rates can include it: send mip_opt_out=true to stay out. |
| Google Gemini (paid) | No | Paid API: no training on your data. |
| Google Gemini (free tier) | Yes | The free API tier may use your content to improve products, including human review. Don't send anything sensitive here. |
| Together AI | No | No training; zero-retention toggle in settings. |
| Fireworks AI | No | No training by default. |
| OpenRouter | Depends | Depends on the downstream provider. ":free" models often allow training: turn off trainable providers in your OpenRouter settings. |
| Claude subscription (via CLI) | If enabled | Consumer accounts train by default (opt-out): the "Help improve Claude" toggle is on unless you turn it off in your claude.ai settings. Some safety-flagged chats may still be used regardless. |
Two honest traps to remember: the Gemini free tier, and a consumer Claude subscription with "Help improve Claude" left on (it is on by default). Everything else, with your own paid key, does not train on you by default.
Meetings: consent first, always
Recording a meeting involves other people's words, not just yours. So Dimmy won't start without an explicit consent step, every single session: a dialog asks you to confirm you have everyone's consent, offers a spoken and copyable announcement for remote participants, and keeps a local, append-only log of what was confirmed and when. Recording without consent is not a setting you can toggle away. The audio, the transcript and the recap stay on your computer, like everything else. Dimmy gives you the tools to ask for consent, but obtaining valid consent, and complying with the recording laws that apply to you, remains your responsibility.
Where Dimmy stands on the EU AI Act
Dimmy is an AI system, and we are its provider under the EU AI Act (Regulation 2024/1689). Based on our analysis it sits outside the heavily regulated tiers: voice dictation, transcription and meeting summaries are not among the prohibited practices, nor among the high-risk uses listed in Annex III. At that level no conformity assessment or certification applies, and none exists to be obtained, so you will never see us claim one. What does apply is transparency, and that deserves a precise answer rather than a slogan.
The transparency rules (Article 50) apply from 2 August 2026. Following the Commission guidelines adopted on 20 July 2026, here is how they land on a tool like this. Dictation, transcription and grammar or style rewriting count as standard editing: they don't change the substance of what you said, so no marking duty attaches to them. Summaries are a different matter. Condensing an hour of meeting into a recap does restructure meaning, so an AI-generated recap has to carry a mark, readable by machines, saying it came from AI.
For products already on the market before that date the law allows until 2 December 2026 to add that marking, and that is what we are building. The rest of what the rule asks for is already true here: Dimmy never passes for a human, it is always clear that transcriptions, rewrites and recaps come from AI, every output is shown to you and stays yours to accept or discard, we don't train any model on your data, and Dimmy does not identify who is speaking from their voiceprint, does not infer emotions, and does no biometric categorisation. If our reading turns out to be wrong, or the guidance moves, we will say so on this page and fix it.
Don't trust us. Check.
The code is public under AGPL-3.0, every telemetry event is listed with its exact payload on the privacy page, and the app logs locally everything it sends. Claims you can verify beat promises you have to believe.
This page is a plain-language explanation, not legal advice, and provider policies are theirs, not ours: always check the provider's current terms before sending sensitive data. Everything here reflects how Dimmy works to the best of our knowledge on the date shown above.