Voice to Mac was built to be private by default. Your voice is processed on your Mac and never leaves it. This page explains — in plain English — what that means, and the few narrow cases where anything is transmitted at all.
The rest of this page backs each of these up in detail. If you only read this section, you'll still have the complete picture.
Transcription runs entirely on-device. We have no server that receives audio, ever.
The app ships no telemetry. This website uses no analytics, no cookies, no fingerprinting.
AI cleanup is optional. When you enable it, text (never audio) goes directly from your Mac to the AI provider you chose, under their terms.
Off by default. If you turn them on, they contain no audio and no transcript text.
Voice to Mac is published by Bubl, a sole proprietorship based in the United States ("we," "us," "our"). "You" means the person using the Voice to Mac application or visiting voicetomac.com.
For any privacy question, request, or complaint: support@bublcx.com. A real person reads everything sent to that address.
We designed Voice to Mac so that we have no technical ability to see your voice, your transcripts, or how you use the app. The following is a complete list of information we can receive, directly or through a service provider:
dl.voicetomac.com. The request includes your IP address, the app version you're running, and the standard User-Agent string — the same information any website receives when your browser visits it.That list is exhaustive. The app does not send usage analytics, report which apps you dictate into, or phone home in any other way. The marketing website uses no analytics tools, no advertising pixels, and sets no cookies.
The following is stored locally and is never transmitted by the app:
~/Library/Application Support/VoiceToMac/voicetomac.sqlite. Only you, and processes you grant access to, can read this file.~/Library/Application Support/VoiceToMac/pipeline.jsonl to help you debug. Each entry contains the first 80 characters of the raw and cleaned transcript, any code context the app gathered (file name, identifiers, language), and — when AI cleanup is used for that dictation — the full AI system prompt, the full JSON request sent to the provider (which itself contains a copy of the transcript up to about 2,000 characters), and the full AI response. This file is local-only and is never transmitted.You can delete all of it at any time by removing the folder ~/Library/Application Support/VoiceToMac and the app's Keychain entries.
AI cleanup is an optional feature that rewrites a transcript for grammar, filler removal, and tone. It is disabled by default. When you enable it, you choose one of these providers and supply your own API key:
When AI cleanup is enabled with a cloud provider, the app sends a JSON request containing your rules-cleaned transcript (capped at about 2,000 characters), your style and formality preferences, and — if Variable recognition is on — the file name and identifier list described below. Your audio is never included. The request goes directly from your Mac to the provider you selected, authenticated with your API key, and flows under that provider's privacy policy and terms of service. We do not proxy, intercept, or log any part of that traffic. If you disable AI cleanup, no transcript text is ever transmitted.
If you enable "Variable recognition" (under the Code pane in the app) while AI cleanup is active, the app also sends a small context summary to the AI provider so it can match your spoken words to the symbols in your editor. That summary can include:
AppState.swift).No source-code bodies, comments, string literals, or full file paths are sent to the AI provider. Two additional tiers control how the app locates your active file and are both off by default:
~/Projects, ~/Developer, ~/Documents, ~/Desktop, ~/Code, ~/repos, ~/src) to locate the file your editor is showing.lsof to see which file your editor process currently has open.Both are local system operations; their results are only used to pick which file's identifiers to include in the context summary described above.
The only third parties that can receive data about you because of our use of them are:
voicetomac.com and dl.voicetomac.com. Sees standard HTTP request logs (IP address, User-Agent, URL) as part of serving the site and delivering the download.The AI providers you can plug into the app (listed in section 4 above) are not our sub-processors — you contract with them directly by supplying your own API key.
voicetomac.com does not set cookies, use analytics, embed advertising pixels, or fingerprint your browser. The Voice to Mac application does not embed any analytics, attribution, or advertising SDKs. The only third-party SDK in the app that can transmit data off-device is Sentry, and only if you opt in to crash reporting (see section 2).
Depending on where you live, you may have rights under the General Data Protection Regulation (GDPR, EU/UK), the California Consumer Privacy Act (CCPA/CPRA), or a similar law. These typically include the right to:
In practice, the only personal information we hold directly is your purchase record — email, license key, and associated metadata — held by Lemon Squeezy and cached locally in the app's preferences on your Mac. To exercise any right, email support@bublcx.com from the address you used to buy the license and tell us what you want done. We will respond within 30 days.
We do not sell your personal information and we do not share it for cross-context behavioral advertising, as those terms are defined under the CCPA/CPRA.
Voice to Mac is not directed to children under 13, or under the equivalent age of digital consent in your jurisdiction (16 in parts of the EU and the UK). We do not knowingly collect personal information from children. If you believe a child has provided us information, contact support@bublcx.com and we will delete it.
Our primary security measure is minimization: by not collecting audio, transcripts, or usage data, the amount of information an attacker could obtain from us is inherently small. For the limited data we do hold (purchase records, opt-in crash reports, server logs), we rely on our service providers' security programs — Lemon Squeezy, Sentry, and Cloudflare each publish independent security documentation.
On your Mac, transcripts and API keys are protected by the standard macOS security model (user-account isolation, Keychain, file permissions). No system is perfectly secure, and we cannot guarantee absolute security of any information.
The publisher is based in the United States. If you use the app from outside the United States, the limited information we hold may be processed in the United States or in other countries where our service providers operate. Where required, we rely on the standard contractual clauses or equivalent transfer mechanisms offered by those providers.
We may update this policy from time to time. Minor edits (clarifying wording, fixing typos, updating a link) take effect when posted. Any material change — for example, adding a new type of data collection, or weakening one of the core privacy guarantees in the summary above — will be announced in the app's release notes and on this page at least 30 days before it takes effect, and the effective date below will be updated.
For any question about this policy, to exercise a privacy right, or to tell us you think we're doing something wrong, email support@bublcx.com.
Effective April 23, 2026. Last updated April 23, 2026.