Privacy and data
This help describes AI Video Translator 1.39.0. If you are helping someone and do not know which version they use, ask them to open Settings → About App and read App Version (for example 1.39.0+3; use the part before +). Help for another version: https://aivideotranslator.app/docs/<version>/llms-full.txt (replace <version>; the list of published versions is in https://aivideotranslator.app/llms.txt)
If you use local models, your video is processed on your computer. Cloud providers and connected assistants can receive content in different ways; this page explains those, and the binding privacy policy sets out the terms.
Know what can leave your computer
You don't need an app account, and we have no server that receives your media. The optional services receive only what they need for their purpose:
- Your chosen cloud provider receives audio for transcription or text for translation and voices, after consent.
- Sentry receives scrubbed crash reports when enabled, and feedback you submit.
- Mixpanel receives usage statistics only after you turn them on.
- GitHub and Hugging Face serve model downloads and see your IP address.
- Microsoft or Apple checks your subscription.
- Apple serves missing Mac speech resources after you approve their installation.
On Windows, the app also makes short connection checks to download hosts and provider servers when it starts. It sends no media, keys or filenames in those checks, but the hosts see your IP address as they do with any connection.
On Mac, macOS manages its language, voice and model downloads. Apple features explains what you'll need for Apple's local processing.
Understand assistant access
If you enable local assistant access, a connected assistant can read and edit every registered project the app can access, including ones you haven't opened. You can't set separate permissions for each project or assistant.
Your assistant can receive complete transcripts, translations, notes, glossary, terms, settings, speakers, timing and voice status. If it asks for pictures from your video, it receives those too.
The assistant also receives Help, job status, file locations, edit results and shared history. Your provider keys, server addresses and provider configuration stay in the app.
Free edits don't start processing. If you explicitly ask for translation, voice generation, retranscription or export, it starts without an app confirmation, can cost you money and can't be undone.
Your assistant must never repeat paid work automatically after an error. A successful new transcription clears project history; if work fails or you cancel, results the app already saved can remain.
If you use Shortcuts, it receives your choices, job status and returned files; Siri can receive Help passages. Apple handles them under its terms, and any other assistant handles its processing, including cloud use, under its own terms.
Choosing on-device translation doesn't mean your assistant keeps its processing local. Your external-service consent controls the app's provider requests, which check consent each time, but it doesn't control content returned to the assistant.
When you export, the reply gives the assistant a file location without sending video through the connection. If its host has separate access to your files, it can read or share that video.
The app keeps returned frame images out of logs, crash reports and statistics. Local MCP assistant explains how you control access.
Keep processing local
If you decline external AI services, the app blocks cloud steps and you can still use local providers. It keeps your stored keys but doesn't send them to providers.
- During setup, choose “I don't agree”.
- Confirm “Use on-device only”.
- If you agreed earlier, open “Settings”.
- Open “About App”.
- Turn off “External AI services”.
- Choose on-device providers for each project step.
You can also use Apple's on-device providers or a translation server on your own computer without that consent. These choices keep the app's processing local, but they don't control what your assistant does with content it receives; Providers and API keys explains the server choices.
Work offline
Once you've installed the models, you can transcribe, translate, make voices, separate audio and export offline. For Apple processing, you'll also need its language resources and voices installed beforehand; On-device models helps you prepare.
You'll need internet for downloads, cloud providers, feedback and store checks. If the store can't verify your subscription, Premium may be temporarily unavailable.
Control statistics and crash reports
You'll find both switches under “Privacy and diagnostics” in “Settings”, on “About App”. Usage statistics are off to start with; crash reports are on in released builds.
If you enable statistics, they record feature use and failed steps under a random installation ID. They never include your media, name, email, filenames, paths, transcripts, translations, generated audio or keys.
Crash reports include errors, stack traces, your app version, system details and recent logs. Before sending, the app removes keys, tokens, email and IP addresses, and usernames in paths.
- Open “Settings”.
- Open “About App”.
- Change “Usage statistics” or “Crash reports”.
- After changing crash reporting, restart the app for it to take effect.
If you turn statistics off, the app stops sending them and discards queued events. Neither switch deletes events already received; support can help you request deletion and provide the installation identifier it requires.
Know what feedback sends
When you use “Send Feedback”, you send your message and any name or email you choose to include. Attachments go unchanged, so review them before sending and never include an API key.
If you tick “Attach app log automatically”, your feedback includes the last 500 anonymized log entries. The form describes what you'll send and asks you to confirm.
You can send feedback with crash reports off, and doing so doesn't turn them back on. The speech-bubble button, “Send feedback to support”, opens the form.
Find your files
You'll find your project work, models and exported videos on your computer. The app uses your original video from its existing location without copying it into the project.
- Projects: “Path to Projects” in Settings, normally AI Video Translator in Documents. Each project holds segments, voices, extracted audio, background sound and a final-video copy.
- Models: “Path to AI Models”, normally the app's own data folder.
- Settings: local app preferences.
- API keys: Mac Keychain or Windows storage encrypted for your Windows account, outside projects and preferences.
- Exports: the locations where you saved them.
Delete your data
If you delete a project, you remove its generated work and keep the original video. If you clear settings, you remove preferences and keys but keep your projects and models.
- To delete a project, open “Select Project”.
- Choose “Delete Project” for it.
- Confirm deletion.
- To remove models, open “Manage Models” in “AI Providers”.
- Delete the models you no longer need.
- To reset preferences and keys, open the Settings dialog's “Settings” tab.
- Choose “Clear Settings”.
- Confirm “Clear All Data”.
If you uninstall the app, your project and model folders stay, so you'll need to remove those separately to clear their files. macOS manages Apple's speech resources, languages and voices separately.
Cloud providers keep data you submit according to their own policies. We can't access or delete it, so you'll need to request deletion from the provider.
Plan use at work
Your IT team can keep the app's AI processing local by withholding external-service consent. Statistics start off, and you can turn crash reporting off too.
You install and update the app through Microsoft Store or the Mac App Store; it doesn't have its own updater. Model downloads come from fixed locations, and the app checks published checksums when available.
On Mac, the app runs in a sandbox. It can access its own container, files and folders you choose, and Movies, Music and Downloads; it doesn't ask for microphone access.
You can read component and model licences in “Third-party Licenses” under “Settings”, on “About App”. Some model licences restrict how you can use them; the terms explain this.
Technical details
On Windows, the app encrypts stored credentials with Data Protection (DPAPI). You don't need external-AI consent for loopback Local AI endpoints (localhost, 127.0.0.1, ::1), but you do for LAN and remote endpoints.
Through MCP project reads, get_frame, edit_project, edit_segments, even_out_acceleration and project_history, the host receives scoped content and receipts. Exports stay file-backed, while source frames are sent as JPEG image bytes.
For certificate warmup on Windows, the app sends HTTPS HEAD requests with system curl and doesn't receive response bodies. It checks GitHub, Hugging Face and built-in cloud-provider hosts; it only checks Mixpanel or Sentry if their corresponding switches are on.
These checks run even if you haven't given external-AI consent. Windows can update trusted root certificates through Microsoft; on macOS, the app doesn't make these startup requests.