Privacy Policy
Last updated: October 30, 2026
The app
Video and audio transcription, subtitle syncing, format extraction/conversion and cleanup all run entirely on your device — those files are processed locally and are never uploaded to our servers or anyone else's. The app contacts our servers to activate or validate your license key, to check for updates, and — only if you connect a credits account — to translate with credits (see below).
AI translation (DeepSeek)
Subtitle translation is the one feature that is not offline: the subtitle text you choose to translate is sent to DeepSeek so that DeepSeek's servers can translate it. Only subtitle text is sent — never your video or audio files. Review DeepSeek's own privacy policy for how they handle it, and avoid AI translation on text you don't want leaving your device. How the text gets there depends on how you pay:
With your own API key, the app sends the text directly to DeepSeek. We do not see, store or proxy this traffic.
With credits in the app, the app sends the text to our server, which passes it on to DeepSeek under our account and returns the translation. We do not store the subtitle text or the translation. For each translation we record its number of lines, its languages, how much of DeepSeek's capacity it used, what it cost in credits and when it ran — not the file's name. Connecting the app to your account stores a sign-in token for that copy of the app, its device type, and when it was connected and last used; you can disconnect it at any time from Connected apps.
With the online translator on this website, the files you upload are stored on our server while they are translated, then deleted. The translated file is kept for 30 days so you can download it, then deleted; the record of the job (file name, languages, line count, credits) stays in your history.
Other AI features that use DeepSeek
The same applies to every feature that calls DeepSeek, not only translation: AI Clean Up sends the subtitle text it rewrites, the vocabulary Suggest button sends the names of the checked files or the title you type, and the translation step of Dubbing sends the dialogue text. Your own API key is used directly where one is set. Nothing else is sent, and never video or audio. DeepSeek is operated from China, so text you send it is processed there under DeepSeek's own policy; do not use these features on text you are not willing to send.
Dubbing and voices
Dubbing runs entirely on your computer: your video, its audio, the separated dialogue, the voice samples and the generated speech are never uploaded to us or anyone else. Voices are copied from short samples of a speaker that you choose; those samples and your voice library are files stored on your computer, and only leave it if you share or export them yourself. Only the translated text goes out, as described above.
Downloads the app makes
To keep the installer small, the app downloads some components the first time you use the feature that needs them: speech, OCR, speaker-detection and dubbing models, and tools such as FFmpeg, ffsubsync and yt-dlp. These come from the hosts that publish them, which see your IP address like any download. The YouTube Transcript screen contacts YouTube directly from your computer to read the captions of the link you paste; if you choose AI transcription there, it downloads that video's audio and transcribes it locally.
Your account and credits
A website account stores your name and email address, and either a password (stored only as a hash) or your Google account ID if you sign in with Google. We keep a record of the credits you buy and use. Payments are processed by Stripe; we never see or store your card details.
This website
When you buy a license we store your email address, your order details and the license keys we issue to you. Payments are processed by Stripe; we never see or store your card details. See the Stripe privacy policy.
Free online tools and API
Files you upload to the free tools at /tools (or send to their API) are processed in memory and handed straight back — we don't keep the file or its contents. For each request we log the tool used, the file's name, type and size, the options chosen, whether it succeeded, and the IP address and user agent, so we can see how the tools are used and stop abuse.
The same goes for text pasted into the transcript cleaner at /tools/transcript-cleaner: it is processed in memory and handed straight back, and we log the options chosen but never the text itself.
The online subtitle editor at /tools/subtitle-editor and the subtitle checker at /tools/subtitle-validator are different: they open, check, edit and save your file entirely in your browser, and the file's contents are never sent to us. Unsaved work is kept in your browser's local storage until you download or discard it. When you open, check, fix or save a file, the tool tells us the file's name, size and format, how many subtitles it has and, for the checker, how many issues it found or fixed, and for the editor's Clean up and Position how many subtitles they removed, changed or moved — the same details we log for the other tools — along with your IP address and user agent.
The editor can also open a video file (MKV, MP4, WebM or MOV) to list the subtitle tracks inside it and play the video beside the subtitles. The video is read and played by your browser only — it is never uploaded, however large it is. When you open one, the editor tells us the video's name, size and format, how many subtitle tracks it holds and how many of them are text, how long listing them took, which track you opened (its subtitle format and language), and whether your browser could play the video — along with your IP address and user agent.
Contact form and pricing feedback
When you write to us through the contact form, we receive your name, email address and message by email, and use them only to reply to you. If you leave the pricing page and answer our short "why didn't you buy?" question, we receive your answer by email, along with your email address only if you choose to give it. Neither is added to a mailing list.
License activation
When you activate the app we store a device identifier, a device name, the IP address and user agent of the activation request. We use this only to enforce the per-license activation limit and to let you manage your devices.
Cookies
This website uses a session cookie required for forms to work. We do not use advertising or cross-site tracking cookies of our own. The pricing page shows customer reviews through a widget from Senja, which loads from Senja's servers: Senja therefore receives your IP address and browser details when you open that page and may set its own cookies, under its own privacy policy. Signing in with Google or paying with Stripe also involves those companies, under their policies.
Who handles your data
The website is operated by AI Subtitle Studio; write to info@aisubtitlestudio.com with any question about this policy. Service providers that handle data for us are Stripe (payments), DeepSeek (translation text, as above), Google (sign-in, if you use it), our web host (DreamHost) and Senja (reviews widget). We keep license, order and credit records for as long as the license or account exists and as tax law requires, and delete an account on request.
Your rights
You can request a copy or deletion of your data at any time by emailing info@aisubtitlestudio.com.