This notice explains what Audio Captions processes when you use the Chrome extension, optional Desktop Companion, cloud transcription, translation, transcript sync, and billing.
Caption sources
Existing subtitles
When a page exposes subtitles, the extension reads the caption text and timing from that page. No audio transcription is required.
Private Desktop Companion
The extension sends captured tab audio over the loopback interface to the Companion running on your computer. Audio and transcription remain on that device. The release Companion downloads its English speech model on first use and can then caption without sending audio to us.
Cloud performance
When you choose Cloud performance—or Automatic mode selects it because the Companion is unavailable—short audio chunks are sent to our Cloudflare Worker and forwarded to our speech-to-text processor, Deepgram. Audio seconds are counted to enforce your plan allowance. Cloud audio is used to return transcription and is not added to your transcript library as audio.
Browser compatibility
If explicitly selected, an English-only model runs inside Chrome. Its first use downloads model files from the model host allowed by the extension.
Captions while the side panel is closed
Subtitle captions can keep showing after you close the side panel. While they run, the extension's background process keeps the caption text and any translations for that video in Chrome's session storage on your device. Chrome keeps that storage in memory, does not write it to disk, and clears it when the extension is disabled, reloaded or updated, or when the browser restarts.
Accounts and saved transcripts
Without sync, transcripts and settings are stored in Chrome extension storage. When you sign in and enable sync, we process your email address, session identifiers, plan entitlement, usage counts, and the transcript text and metadata you choose to sync. Cloud data is stored using Cloudflare Workers and D1. Login email is delivered through Resend.
Translation
Translation offers a choice of providers. Which route runs depends on the provider you choose, on whether the side panel is open, and on what your browser provides. Premium DeepL translation requires a trial or Pro plan. The Free provider does not.
- Free provider, side panel open. When Chrome's built-in translator is available for the language pair, Chrome translates the selected text on your device. Otherwise, or when that translator fails, the selected text and the target language are sent to Google's translation service.
- Free provider, side panel closed. Captions keep translating in the background. The background process cannot use Chrome's built-in translator, so it sends the text to Google's translation service even where the side panel would translate on the device. Closing the side panel therefore changes where Free translation runs. [VERIFY before publishing that Chrome gives the background process no built-in translator. If it does, this route is on-device and this item must change.]
- Premium DeepL translation. The selected word or sentence and the target language are sent through our Worker to DeepL. The DeepL API key stays on our server. Translation characters are counted for quota enforcement.
- Your own DeepL API key. The text is sent directly from the extension to DeepL. Your key is stored only on your device, and it is never sent to us.
In sentence and word modes the text is the sentence or word you tap. In automatic mode it is each caption line as it appears. Looking up a word with the Free provider also sends that word to Google's dictionary service for alternative translations, whichever translation route runs. [VERIFY that the dictionary request is made for every Free word lookup, including when Chrome translates on the device.] Provider keys operated by us are never included in the extension.
Payments
Subscription checkout and account billing are hosted by Lemon Squeezy, our merchant of record. We receive subscription identifiers, status, renewal dates, and a customer portal URL. We do not receive or store full payment-card details.
Diagnostic reports you choose to send
When whole-video transcription fails, the sidebar offers a “Send report to developer” button. Nothing is sent unless you press it — there is no automatic or background reporting, and the notice shows you the exact report before you send it. A report contains the address of the media that failed, the error, the transcription engine in use, extension and Companion versions, your operating system and browser version, and a bounded excerpt of the Companion’s local log. It never contains audio, transcript text, page titles, or the contents of your files; the log excerpt records the host of an address rather than the whole address, and a local file only as its type rather than its path. Reports are deleted after 90 days.
Retention and your controls
- Login codes expire after 10 minutes and sessions after 30 days.
- The local library is bounded and can be cleared from the extension.
- Transcript sync can be disabled at any time.
- Signed-in users can export or delete eligible cloud account data.
- Diagnostic reports you chose to send are deleted after 90 days.
- Operational usage counters and billing records are retained as needed for service integrity and legal obligations.
Security and logging
Production logs are designed not to contain transcript text, audio, email addresses, login codes, media URLs, provider keys, or session tokens. No system is perfectly secure; please report suspected issues using the support contact below.
Contact
For privacy requests, questions about this notice, or to exercise your data rights, contact support@audiocaptions.com. We respond to verified requests within 30 days.