Your voice can stay
on your machine.

• Dimmy can run fully offline when you choose local models. If you choose a cloud speech or AI provider, your audio or text goes to that provider, with your own key, under that provider's terms.
• Dictation audio is not kept unless you turn on audio in history. Meeting recordings (audio.wav) are always saved on your computer.
• Usage statistics and crash reports are off until you say yes. Two separate switches. They never contain your audio, your text or your prompts. They are linked to a random installation ID, which is pseudonymous, not anonymous.
• API keys are stored in a local file encrypted with AES-256-CTR and HMAC-SHA256, under a key derived from your user name and computer name.
• The licence service stores a hash of your e-mail, your licence and the devices you activate. Payment is handled by Stripe.

The controller is Konrad Dalla, Via La Piera 67, Bologna, Italy, who develops and sells Dimmy. Contact: [email protected]. Security issues: [email protected].

There is no data protection officer; the law does not require one at this size. Write to the address above for any request on this page.

Dimmy keeps its data in one folder: %APPDATA%\dimmy\ on Windows, ~/Library/Application Support/dimmy/ on macOS, ~/.config/dimmy/ on Linux. Nothing in this folder is sent to us.

Each provider you choose acts on your own account and under its own terms. Which providers can use API data for training is on the data and AI page.

Your data and AI

At first launch Dimmy asks whether it may send usage statistics and crash reports. The two answers are equal, and until you answer nothing is sent. Versions up to 0.7.13 started with both switches on; the consent question arrived with 0.7.14. Values are categories (a provider name, a bucket such as 30_120 seconds), counts, durations or true/false. Free text is never sent.

There is no telemetry path in the code that sends any of the following. Every send is written to the local log with [telemetry], so you can check.

• ✕Your audio.
• ✕The text of any transcription.
• ✕Any prompt, and any LLM output.
• ✕File names, contacts, the names of apps you dictate into.
• ✕Microphone device names.
• ✕API keys or tokens.
• ✕Your e-mail, user name or computer name.
• ✕Calendar attendees, licence or device identifiers.
• ✕IP addresses: PostHog events carry $ip: null, and Sentry EU drops them at intake.

Every telemetry call is written to the local log. 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)

The log also prints the start of the PostHog and Sentry project keys embedded in the build: search for key-diag. That way you can check where events go.

1. 1Open Settings (the gear on the pill, or right-click the menu-bar / tray icon).
2. 2Go to Privacy.
3. 3Send anonymous usage data: usage events to PostHog EU.
4. 4Send crash reports: errors and crashes to Sentry EU.
5. 5A change takes effect immediately. Events already sent cannot be recalled; write to us to have them deleted.

Want to start fresh? Settings → Privacy → Reset anonymous ID makes a new installation ID. Feedback (Settings → Send feedback) sends the text you type, and your e-mail only if you type it, over the crash-report channel; if that is off, the form offers to turn it on and send.

The licence service runs on Cloudflare Workers with a Cloudflare D1 database. It stores:

Purchases are processed by Stripe, through Stripe Managed Payments: Stripe is the merchant of record. It collects the card or other payment data, your billing address and e-mail, calculates and collects taxes, and issues receipts and invoices. We never see your card number. Stripe may offer Link, its saved-payment service; using it is between you and Stripe.

dimmy.app is hosted on Cloudflare. It sets no cookies and runs no analytics. To show the page it loads code and images from unpkg.com, cdn.simpleicons.org, api.github.com and Product Hunt, which receive your IP address like any web request. The forms (buy, waitlist, newsletter, withdrawal) send what you type to license.dimmy.app.

Only Konrad Dalla has access to these accounts.

The speech and AI providers you pick, the subscription CLIs (Claude Code, Codex, Gemini CLI), Telegram, Notion and Confluence are not our processors: Dimmy connects to them on your own account, with your own key or login, and they act under their own terms with you.

Transfers outside the EU: some of these companies are based in the United States (for example Stripe, Cloudflare, Resend). Where data is transferred to the US, the transfer relies on the EU-US Data Privacy Framework where the company is certified, or on the European Commission's Standard Contractual Clauses.

Stripe (including Link) keeps your payment data as its own controller, under its own privacy policy. We keep Stripe's monthly self-billed invoices for 10 years, as Italian law requires for accounting records (art. 2220 of the Civil Code). These invoices do not contain your personal data.

Under the GDPR you can ask for access to your data, correction, deletion, restriction and portability, and you can object to processing based on legitimate interest. Write to [email protected]. We answer within one month.

You can also lodge a complaint with the Italian supervisory authority, the Garante per la protezione dei dati personali (garanteprivacy.it), or with the authority of the EU country where you live.

Delete your account: the licence service has a deletion request at POST /api/account/delete. You send your e-mail, we send you a one-time code, and you confirm with it. On confirmation the licence is marked deleted, the e-mail hash on the licence is replaced by a random placeholder, any subscription is cancelled, and your lead and waitlist rows are removed. The audit log, which holds the e-mail hash, stays, to prove the request was honoured. Records that tax law makes us keep are kept for that period. If you prefer, write to us and we do it for you.

Telemetry is linked only to the installation ID. To have it deleted, send us that ID (in the analytics_id file), then reset it.

Dimmy uses AI models: speech-to-text, text cleanup, command mode and meeting recaps. Their output can be wrong. Under the EU AI Act (Regulation 2024/1689) these are neither prohibited practices nor high-risk uses under Annex III; the obligation that applies is transparency, under Article 50.

• Every recap saved to recap.md carries a machine-readable marker (<!-- dimmy-ai-generated: true; by: Dimmy; model: … -->), and the app shows "AI-generated summary. Review it before sharing." above it.
• Some things happen without a review step, because you set them up that way: dictated text is pasted into the app in front of you, history is saved, a recap runs when a meeting stops, and a recap can be sent to Notion automatically if you turn that on. Review AI output before you share it.
• We do not train models on your data. Dimmy integrates third-party models without modifying them.
• Dimmy does not identify people from their voiceprint, infer emotions or do biometric categorisation. Speaker labels in meeting transcripts ("Speaker 1", "Speaker 2") only separate voices inside one recording.

This is our own assessment, not a certification, and it is not legal advice. Which cloud providers can train on your words if you bring your own key is on the data and AI page. Your data and AI

Material changes are announced in the release notes and the date at the top changes. The ground truth is PRIVACY.md in the app repository; git log PRIVACY.md shows every change.