Last updated: 17 November 2026
Sublate ("the app", "we", "us") is a real-time translation tool that displays translated subtitles and on-screen text as an overlay. This policy explains what the app accesses, why, and how your information is handled.
This policy covers Sublate version 1.2.0 and later. Photo translation and the optional YouTube app feature (Notification access) described below exist only in those versions; if you use an earlier version, the parts about them do not apply to you. Camera TV mode and its read-aloud feature (Sections 2 and 3) exist only in the versions that include them; if your version does not show Camera TV, the parts about it do not apply to you.
Core principle: your media stays on your device; the text to be translated usually goes to an online service. Sublate has no user accounts and runs no analytics of its own. Optional rewarded ads are shown through Google AdMob, and Pro purchases are handled by Google Play (Section 6). The audio, screen images, camera images and photos it processes are handled only on your device and are never uploaded by the app (a translated image leaves your device only if you choose to share it). To translate, the text extracted from them is sent to an online translation service (Google Translate, and DeepL if you configure it), unless an offline language model on your device does the translation (Section 3). Apart from the ad and purchase services in Section 6, the following can also leave the device:
For a YouTube video opened in a browser, its video ID (and, when the video has human-made subtitles in your translation language, that language's code) is sent to YouTube to fetch that video's subtitles in advance.
Only if you allow Notification access for the YouTube app feature (off by default): the title of the video playing in the YouTube app and your device's language and region are sent to YouTube search to find the video ID, which is then used to fetch that video's subtitles. The video's channel, length and position stay on your device.
See Sections 1, 2 and 3.
We have no accounts, no backend server of our own and no analytics of our own. We do not collect or store your personal data on any server.
The free version can show rewarded video ads through Google AdMob, only when you choose to watch one in exchange for extra translation time. When you open the screen that offers a rewarded ad, an ad may be loaded in advance so it can start without delay. AdMob collects your device's Advertising ID and related data (approximate location derived from your IP address, device information, and ad interaction events) to serve and measure ads. Pro subscriptions and the one-time Pro purchase are processed by Google Play. See Section 6.
Apart from the ad and purchase services above, and the free-use records described in Section 9 (which may be copied to your new phone if you restore Sublate with Android's device-to-device transfer, but never reach us), only the following kinds of data derived from your use of the app can leave your device:
The text you translate, which is sent to the online translation service described in Section 3 to perform the translation, unless it is translated on your device with an offline language model (Section 3).
When you open a YouTube video in a browser, the video ID of that video (for example dQw4w9WgXcQ) is sent to YouTube so that the video's existing subtitles can be downloaded in advance and shown without delay. This is a video identifier, not your screen content and not an account identifier. If the video publishes human-made subtitles in your translation language, that language's code (for example tr) is sent with the request. See Section 3.
Only if you allow Notification access for the YouTube app feature (off by default): the title of the video playing in the YouTube app and your device's language and region are sent to YouTube search to find the video ID, which is then sent to YouTube as in item 2. See Sections 2 and 3.
(Separately, the app downloads its offline speech-recognition models and, only if you choose to download it, the optional natural voice for Camera TV from public file hosts, and Google ML Kit downloads its on-device translation models from Google's servers — see Section 6. Those are ordinary downloads; nothing of yours is sent with them. The Google ML Kit library bundled in the app may also send its own technical diagnostics to Google — see Section 6.)
The app requests certain Android permissions strictly to provide its features. The raw audio and screen content captured is processed only in memory, on your device, and is discarded — it is never uploaded or stored. Only the text to be translated can be sent to the translation service (Section 3).
Accessibility Service — Why it is used: To read the subtitle/caption text shown on screen so it can be translated in real time. — What happens to the data: The text is read transiently and sent to the online translation service (§3) to be translated; the result is shown as an overlay. Not stored by us. In a browser showing a YouTube video, the video's address is also read on your device to find its video ID (§3, "YouTube subtitle pre-download").
Display over other apps (overlay) — Why it is used: To draw the translated text on top of other apps. — What happens to the data: No data is read; this only draws on screen.
Screen capture (MediaProjection) — for OCR — Why it is used: When you start screen translation, the app captures screen images to detect text. Requires your explicit consent each session. — What happens to the data: Frames are processed on-device to detect text and then discarded — frames are never sent. The detected text is translated on your device when an offline language model is available; otherwise it is sent to the translation service (§3).
App/media audio capture (AudioPlaybackCapture) — for Speech Recognition — Why it is used: To turn audio that is playing from other apps into subtitles using on-device speech recognition. — What happens to the data: Audio is processed on-device and discarded — audio is never sent or recorded to a file. The recognized text is translated on your device when an offline language model is available; otherwise it is sent to the translation service (§3).
Microphone permission (RECORD_AUDIO) — Why it is used: Used in two ways. Default: Android groups app/media audio capture (AudioPlaybackCapture) under this permission — the microphone itself is not used. Optional "Microphone Mode": some apps and sites block system audio capture; if you explicitly enable Microphone Mode in its consent dialog, the microphone picks up the sound around your device (the media playing from the speaker — which can also include nearby speech) so that such content can still be subtitled. A persistent notification is always visible while capture is active, and you can switch back to system audio anytime in Speech Recognition settings. — What happens to the data: In both modes the audio is processed only in memory, on your device, for speech recognition and immediately discarded — it is never recorded to a file, stored, or uploaded. Only the recognized text is used for translation — translated on your device when an offline language model is available, otherwise sent to the translation service (§3).
Photo translation (a photo you take or choose) — Why it is used: When you take or choose a photo to translate, Android's camera app or image picker gives the app that image so text can be detected in it. — What happens to the data: The image is processed on your device (Google ML Kit) to detect text and is never sent for translation. Only the detected text is sent to the translation service (§3). A translated image is saved to your gallery or shared only when you choose to.
Camera (CAMERA) — Camera TV mode — Why it is used: When you open Camera TV and allow camera access, the app uses your phone's camera to read the subtitles shown on a TV or other screen you point it at. Used only while the Camera TV screen is open in front of you; the camera stops when you leave that screen, and while Camera TV is paused (Pause button) no text is read from the frames. — What happens to the data: Camera frames are processed in memory, on your device (Google ML Kit), to detect text and then discarded — they are never saved to a file, stored or sent. The detected text is translated on your device; it is sent to the translation service (§3) only if your language pair is not available on the device.
Read aloud (Camera TV) — Why it is used: If you turn on read aloud, the translated subtitle is spoken. You choose either your device's text-to-speech engine or the optional natural voice. — What happens to the data: Device voice: the text is passed to the text-to-speech engine installed in Android; the app uses only voices that do not need an internet connection. Natural voice: a speech model that you download once (about 145 MB, Section 6) creates the sound on your device. In both cases the sound is played and discarded — it is never recorded to a file, stored or sent.
Storage (Android 9 and older only) — Why it is used: To save a translated image to your gallery when you choose to. — What happens to the data: Only the image you explicitly save is written to your gallery.
Advertising ID (AD_ID) — Why it is used: Added by the Google Mobile Ads SDK so AdMob can serve and measure rewarded ads. — What happens to the data: Sent to Google AdMob (§6); you can reset or delete it in Android settings.
Google Play Billing — Why it is used: To sell and verify Sublate Pro. — What happens to the data: Handled by Google Play; we receive no payment details.
Showing notifications (the app's own status notification) — Why it is used: To show the required ongoing notification while a translation service runs (Android foreground-service requirement). — What happens to the data: No data collected.
Notification access (NotificationListenerService) — optional, off by default, YouTube app feature — Why it is used: Lets the app recognise the video playing in the YouTube app so its subtitles can be fetched and the translation shown in full sentences at the right time. Used only if you agree on the app's explanation screen and grant Notification access in Android settings. Android warns that the app could read all notifications; Sublate uses this access only for this feature. You can turn it off in the app's settings and remove the access in Android settings. — What happens to the data: Read on your device, only from the YouTube app's media session: the video's title, channel, length and playback position. Sent to YouTube search, only while Caption Mode is on: the title and your device's language and region (§3). Not sent, stays on your device: channel, length and position. Not read: the content of your notifications, or of any other app's media session.
Translation is performed by online third-party services, unless an offline language model on your device does it. Text that needs online translation (subtitle text, on-screen text, text in a photo, text read by the camera in Camera TV, or recognized speech) is sent over your internet connection to Google Translate, and additionally to DeepL if you provide a DeepL API key. These services translate the text and return the result. Their handling of that text is governed by their own privacy policies (see Google's and DeepL's privacy documentation).
When text is sent depends on the feature:
Caption Mode and photo translation: the text is sent whenever it needs translating, unless a recent translation of it is still in the app's memory. When subtitles are downloaded in advance (below), their text can be sent before it appears on screen.
Screen translation (OCR) and speech recognition: when an offline language model is available, the text is translated on your device and is not sent. Otherwise, or if you choose online translation for speech recognition, it is sent.
Camera TV: the text is translated on your device with an offline language model and is not sent. It is sent only if your language pair has no offline model.
Sublate does not store the translated text or send it to any server we operate. On-screen text recognition (OCR), text recognition in photos and camera images, and speech recognition run on your device — only the resulting text can be sent for translation, never the raw screen images, camera images, photos or audio.
Reading the translation aloud happens on your device. With the device voice, the text goes to the text-to-speech engine installed in Android (for example Google's speech engine), and Sublate selects only voices that work without an internet connection. With the optional natural voice, the sound is created by a model on your device. No text or sound is sent to us, and the sound is never saved.
When you watch a YouTube video in a browser while Caption Mode is on, Sublate reads the video's address from the browser's address bar on your device and extracts the video ID from it. That video ID is sent to YouTube (www.youtube.com) to ask for the subtitle tracks the video already publishes, so they can be downloaded ahead of time and displayed without delay. If the video already publishes human-made subtitles in the language you translate into, Sublate also requests that track — that request additionally contains the language code of your translation language (for example tr) — and may display those subtitles instead of a machine translation.
What is sent: the video ID (for example dQw4w9WgXcQ) and, only when such a track exists, the language code of your translation language (for example tr). Not the full URL, not your browsing history, not your screen content, not any account or device identifier.
Who receives it: YouTube — the same service that is already streaming the video to you.
Why: downloading the subtitles in advance makes subtitles appear instantly instead of lagging behind the speech.
YouTube's handling of that request is governed by Google's privacy policy.
This happens only if you turn on the YouTube app feature: you agree on the app's explanation screen and grant Android's Notification access. Without it, Caption Mode keeps working and nothing in this subsection happens.
What is read on your device: the title, channel, length and playback position of the video playing in the YouTube app, only from that app's media session. The content of your notifications is not read.
What is sent, only while Caption Mode is on: the video title and your device's language code and region code (for example tr and TR; the region only if your device has one set) to YouTube search (www.youtube.com). This happens once each time a new video starts playing in the YouTube app; it is not repeated while that video plays, and a failed search is not retried for that video. If you play the same video again later, it can be searched again. No account information, cookie or device identifier is included in that request. As with any internet request, YouTube can see your IP address.
What stays on your device: the channel, length and position. The channel and length are used only to check that a search result is the right video, and the position only to keep the translation in time.
What happens next: if exactly one search result matches, its video ID is used to fetch that video's subtitles as described above (the video ID and, only when such a track exists, the language code of your translation language).
How to stop it: turn the feature off in the app's settings, and remove Notification access in Android settings.
YouTube's handling of these requests is governed by Google's privacy policy.
Apart from the text sent for translation (above), the two cases in this section are the only cases in which anything derived from what you are watching leaves your device. They do not happen for other apps or for other websites.
Sublate is intended for personal use — language learning, accessibility, and understanding foreign-language content. Please respect the copyright and DRM protections of third-party content. The app does not bypass content protection; on protected (secure) screens, capture is blocked by the operating system.
The app is not directed to children under 13 (or the higher minimum age set by the law of your country, for example 16 in some EU countries) and we do not knowingly process children's data. We have no accounts and keep no personal data on any server of our own. The app does not treat any user differently by age: the data described in this policy (for example the text sent for translation, and the Advertising ID and ad data processed by Google AdMob, Section 6) leaves the device in the same way for every user of the app.
These are all of the third parties the app can contact:
Google Translate (translate.googleapis.com, clients5.google.com) — used to translate the text you choose to translate, as described in Section 3.
DeepL (api.deepl.com, api-free.deepl.com) — optional; used for translation only if you add your own DeepL API key.
YouTube (www.youtube.com) — receives the video ID of a YouTube video you open in a browser (and, when available, the code of your translation language), so its existing subtitles can be downloaded in advance (Section 3). Only if you allow Notification access for the YouTube app feature (off by default), YouTube search also receives the title of the video playing in the YouTube app and your device's language and region, to find the video ID (Section 3).
Hugging Face (huggingface.co and the download servers it redirects to) and GitHub (github.com) — used only to download the offline speech-recognition models and, only if you choose to download it, the optional natural voice for Camera TV (Supertonic 3, about 145 MB, from Hugging Face) to your device. These are plain file downloads, each checked against a fixed checksum; no text, audio, screen or camera content of yours is sent to them.
Google ML Kit (on-device text recognition and on-device translation) — runs on your device; its on-device translation models are downloaded from Google's servers. It is a Google library bundled into the app and it brings Google's own diagnostic transport (com.google.android.datatransport) with it, which may report library-level diagnostics to Google under Google's privacy policy. According to Google's ML Kit data disclosure, this can include device information (manufacturer, model, OS version), app information (package name and version), per-installation identifiers that are not meant to identify you or your device, performance metrics, error codes and, for translation, the configured source and target languages. It does not include the text, images or audio being processed. It is sent encrypted (HTTPS) and is used by Google for diagnostics and usage analytics of the library. We do not receive and cannot read anything it may send.
Google AdMob (Google Mobile Ads SDK) — used to show rewarded video ads only inside Sublate's own screens and only when you tap to watch one. Ads are never shown in the translation overlay, in notifications or over other apps. AdMob processes your Advertising ID, IP address (from which an approximate location may be derived), device information and ad interaction events, under Google's advertising policies. In the EEA, the UK and Switzerland we ask for your consent through Google's consent tool before personalised ads are shown; you can change that choice at any time under Settings → About → Ad privacy choices. You can also reset or delete your Advertising ID in Android settings. Subtitle text, on-screen text and recognised speech are never shared with AdMob or used for ad targeting or measurement. AdMob may pass this data to its advertising partners through its ad auction. See how Google uses data: https://policies.google.com/technologies/partner-sites
Google Play Billing — Pro subscriptions (monthly, yearly) and the one-time Pro purchase are processed by Google Play. We do not receive or store your payment details; Google Play's own terms and privacy policy govern the transaction. The app asks Google Play whether you have an active purchase so it can unlock Pro.
Google Play services Block Store: only if you choose to start the trial, keeps a copy of your free-use records on your phone (Section 9). We do not enable its cloud backup and we cannot read this copy from anywhere but the app on your phone.
We operate no analytics, crash-reporting or attribution SDK of our own.
The developer responsible for the app and for the processing described in this policy ("data controller" under the EU GDPR and "veri sorumlusu" under Türkiye's Personal Data Protection Law No. 6698, KVKK) is:
Emirhan Karabulut (Emirsoft), Sivas, Türkiye — sublate.support@gmail.com
Text you choose to translate, when it is not translated on your device (Section 3), is sent to Google Translate (or DeepL, if you add your own key) because that is the service you ask the app to perform — GDPR Art. 6(1)(b); KVKK Art. 5(2)(c).
YouTube video ID (and, when available, your translation language code) is sent to YouTube so subtitles can be shown without delay — our legitimate interest in a working, responsive feature, GDPR Art. 6(1)(f); KVKK Art. 5(2)(f). You can avoid it by not using Caption Mode in a browser; for the YouTube app, see the next item.
Video title, device language and region, and the resulting video ID (YouTube app feature) are read and sent only after you agree on the app's explanation screen and grant Notification access. You can stop this at any time by turning the feature off in the app's settings or removing Notification access in Android settings. Legal basis: your consent, GDPR Art. 6(1)(a); KVKK Art. 5(1).
ML Kit diagnostics are sent by the Google library for its reliability — legitimate interest, GDPR Art. 6(1)(f); KVKK Art. 5(2)(f).
Advertising ID and ad data (AdMob) — processed when you open the screen that offers a rewarded ad (an ad is loaded in advance so it can start without delay) and when you watch one; never while you use the translation modes. In the EEA, the UK and Switzerland, ads are requested only after you respond to Google's consent form; personalised ads only with your consent, GDPR Art. 6(1)(a). Elsewhere, AdMob may show personalised ads based on your Advertising ID; you can turn off ad personalisation or delete your Advertising ID in Android settings. KVKK Art. 5(1) / 5(2)(f).
Purchase status (Google Play) — needed to provide the Pro features you bought, GDPR Art. 6(1)(b); KVKK Art. 5(2)(c).
Block Store copy of free-use records: kept only if you tap "Start trial" after being told about it, so a trial is used once per device; your consent, GDPR Art. 6(1)(a) and Art. 5(3) of the ePrivacy Directive; KVKK Art. 5(1). You can withdraw it by deleting the copy (Section 9). If you continue without the trial, no copy is made.
Model downloads necessarily reveal your IP address to the file host, as any download does — GDPR Art. 6(1)(b); KVKK Art. 5(2)(c).
Screen images, camera images, photos, audio and microphone input are processed only on your device and are never received by us. Microphone Mode additionally requires your explicit choice in its consent dialog.
Withdrawing consent. Where processing is based on your consent, you can withdraw it at any time: turn the feature off in the app's settings (YouTube app feature, Microphone Mode), change your ad choice under Settings → About → Ad privacy choices, or delete the free-use records copy under Settings → About. Withdrawing consent does not affect processing that took place before.
Do you have to provide data? No. You are not required by law or contract to provide any personal data. Some features do not work without the data they need (for example, online translation needs the text to be sent to the translation service), but you can use the other features, translate on your device where a language model is available, or stop using a feature at any time.
Automated decisions. We make no automated decisions about you that have legal or similarly significant effects, and we do not build profiles of you. Google AdMob may use your Advertising ID to personalise ads where you allow it (Section 6).
Text sent for translation: we never receive or store it. Recent translations are kept only in the app's memory to avoid repeating requests and are discarded when the app stops.
Screen images, camera images and audio (including the sound of read aloud): processed in memory and discarded immediately; never written to a file.
Photos you choose to translate: are never sent to us. A temporary copy may remain in the app's cache on your device until Android clears it, you clear the app's data or you uninstall the app.
Video title, channel, length and position (YouTube app feature): held in memory while the feature is working and not written to a file by the app.
Settings, your glossary and saved layouts stay only on your device until you delete them, clear the app's data or uninstall the app. Your DeepL key is kept in encrypted on-device storage. The app does not use Android cloud backup, so none of this is copied to your Google account. Free-use records are handled separately, as described below.
Downloaded models stay on your device until you delete them or uninstall the app.
Free-use records (when you agreed to and started the trial and when it ends, daily free-time and ad-reward times and counts, and clock-check values) contain no name, account, identifier, purchase token, or screen, audio or subtitle content, and are never sent to us. They are kept in the app's storage. If you choose to start the trial, a copy is also kept in Google Play services' Block Store on your phone, to help prevent the trial being restarted by reinstalling. This copy may remain after you uninstall the app and is read again if you reinstall it. We do not enable Block Store's cloud backup, but if you restore Sublate to a new phone with Android's device-to-device transfer, Google Play services may copy it there. You can delete this copy under Settings > About > Delete free-use records. If you continue without the trial, no copy is made. The app also reads the date it was first installed, which stays on your device, to decide whether a trial is available.
A cached copy of your Pro status (plan name only, no purchase token) is kept only on your device and is never sent to us.
Third parties (Google — including AdMob and Google Play —, DeepL, YouTube, Hugging Face, GitHub) keep what they receive under their own policies; we have no access to it.
Depending on where you live, you have rights over your personal data — under the GDPR (Articles 15–22): access, rectification, erasure, restriction, portability and objection; under KVKK (Article 11): to learn whether your data is processed and for what purpose, to request information, to know the recipients in Türkiye or abroad, to request correction or deletion, to object to results of automated analysis, and to claim compensation for unlawful processing.
Because the app has no accounts and we operate no server, we hold no data that can identify you. For data received by Google, DeepL or YouTube, please also contact them directly. For ad data, use Ad privacy choices in the app (EEA/UK/CH) or Android's ad settings. Send requests to sublate.support@gmail.com; we will reply within 30 days.
You may also complain to a data protection authority: in Türkiye, the Personal Data Protection Authority (Kişisel Verileri Koruma Kurumu, kvkk.gov.tr); in the EU/EEA, the supervisory authority of the country where you live.
United States. We do not sell personal information for money. Google AdMob may use your Advertising ID and related data for personalised advertising, which some US state privacy laws treat as "selling" or "sharing" personal information. You can opt out by turning off ad personalisation or deleting your Advertising ID in Android settings, and you can send any request under your state's law to sublate.support@gmail.com.
The services listed in Section 6 may process what they receive outside your country — including in the United States (Google LLC) and the European Union (Google Ireland Limited, DeepL SE). These transfers happen because you use a feature that relies on that service, and each provider processes the data under its own terms and privacy policy. Each provider states in its own privacy terms the transfer safeguard it relies on (for example, an adequacy decision such as the EU–U.S. Data Privacy Framework, or Standard Contractual Clauses). The data goes directly from your device to the provider; it never passes through a server of ours. If you do not want text to be sent abroad, you can use on-device translation where a language model is available (Section 3).
We may update this policy as the app evolves. Before releasing any version that changes what data leaves your device, we update this policy and its "Last updated" date.
For questions about this policy or to exercise your rights, contact: sublate.support@gmail.com