Dublio Privacy Policy

Last updated: 15 October 2026

Dublio dubs and subtitles your videos in another language, and it does that work on your phone. This policy explains, in plain words, what the app keeps on your phone, what it sends, and to whom.

In one paragraph

Dublio has no account and no sign-in, and we run no server that receives your videos. Your videos, their sound, the subtitles, the translations and the voices the app makes are processed on your phone and never uploaded. What does leave the phone is listed in full below: the language files the app downloads the first time it needs them, anonymous usage statistics and crash reports sent to Google Firebase, never file names, titles or any text from your videos, the app’s settings from Firebase, a time check for the free plan, ads from Google AdMob on the free plan, the subscription through Google Play or the App Store, and an e-mail to us only if you write one.

1. What this policy covers

This policy applies to the Dublio app for Android and iOS (package and bundle identifier com.inceptionapps.dubstudio). This website has its own privacy notice.

2. No account, no identity

You do not register, sign in, or give us a name, e-mail address or phone number to use Dublio. We do not run a server that receives your videos, your subtitles or the dubs you make. The only identifiers involved are the ones Google’s and Apple’s services use: a random app instance ID for Firebase (section 6) and, on the free plan, your device’s advertising identifier (section 7).

3. What happens on your phone

Everything Dublio does to a video, it does on the phone:

To tell speakers apart and to copy a voice, the app works out a numeric description of how each voice sounds. It is computed on the phone, used only to prepare that video, and never used to identify anyone. It is not sent to us or to anyone else.

Your videos, their sound, the subtitles and translations, the speaker clips and the voices the app makes are never uploaded by the app.

4. What the app keeps on your phone

All of the following is kept in the app’s storage on your phone. None of it is sent to us.

5. Language files and voices

Some of the files Dublio needs to recognise, translate and speak languages are too large to come with the app. Each one is downloaded once, the first time you choose a language or an option that needs it, and the app tells you before the download starts.

Once the files you use are on the phone, preparing a video needs no internet connection.

6. Usage statistics, crash reports and app settings

The app uses three Google Firebase services. Google processes this data for us.

ServiceWhat it receivesWhen
Google Firebase Analytics Which screens are opened and which features are used, for example: a video or subtitle file chosen; the choices made for a preparation, such as the languages and the kind of voice; a preparation or an export started, finished, paused, resumed, cancelled or failed, and at which step; in the player, the dub or the subtitles switched on or off, the speed, full screen, how the subtitles look, the mini player and the floating window; language files downloaded or deleted; the app’s language or theme changed; update notices; the free plan’s limits, the ad before a free preparation and the ad breaks shown; the Pro offer and the result of a purchase; rate and share tapped, and the stars you give when asked for a rating; and the topic you chose when writing to us. Languages are sent as short codes such as en, video lengths and file sizes as ranges such as 5 to 15 minutes, and errors as a kind. With them, a random app instance ID and the device information Google collects. While you use the app
Google Firebase Crashlytics Crash reports: where in the app’s code it went wrong, the device model, the operating system and app version, free or Pro, and the list of the screens and actions above from just before the crash. Also a report when a preparation fails for an unexpected reason and when an export fails, with a short technical message from which file names and paths are removed. When the app crashes or a preparation or export fails
Google Firebase Remote Config A request for the app’s settings, such as whether ads and the subscription are on, how often the player’s ad breaks come, the free plan’s limits, maintenance and update notices, and where language files can be downloaded from. It carries an app instance ID. When the app fetches its settings

Never sent to Firebase: file names, video titles, subtitle or dubbed text, file paths, links, or any identifier of ours for you or your device.

Test builds of the app send nothing to Firebase. In the EEA, the UK and other regions where consent is required, what usage statistics may keep follows your choices in Google’s consent form (section 7). How Google handles this data is described in the Firebase privacy information.

7. Ads, consent and the advertising identifier

On the free plan, the app may show ads supplied by Google AdMob in two places:

Whether ads are shown, and how often the player’s breaks come, are settings we can change without an app update.

To serve ads, Google uses your device’s advertising identifier (the Advertising ID on Android, the IDFA on iOS) and device information. The advertising identifier is a resettable identifier kept by the operating system, not by us. You can reset or limit it in your device settings at any time.

Consent (EEA, UK and other regions where it is required). Before ads start, the app shows Google’s consent form where the law requires your consent. Your choices are passed to Google with each ad request. If your choices do not allow ads to be requested, the app does not start ads at all. Your choices also decide what usage statistics may store: until you allow it, including when you have Pro or ads are off and the form is not shown, Google Analytics receives only signals without identifiers, and nothing is stored on your device for it. You can change your choices at any time in the app under Settings → Privacy choices; the row is shown where the law requires consent, also to Pro subscribers.

Tracking question (iOS). On iPhone, after Google’s consent form, the system asks whether the app may track you before ads start. If you decline, the IDFA is not used; you may still see ads, which are less relevant.

The app does not pass your videos, subtitles, file names or anything about what you prepare to the ads. What Google does with ad requests is governed by Google’s own policies, linked above.

Pro subscribers see no ads, neither before a preparation nor in the player.

8. Subscription, payments and the free plan

Dublio Pro is a monthly or yearly auto-renewing subscription sold through Google Play on Android and the App Store on iOS.

We never see your payment details. Card numbers, billing addresses and store account details are handled by Google and Apple and are never passed to the app. When the app needs to know whether you have Pro, it asks the store on the phone and learns only whether a subscription is active. We keep no purchase records on a server of our own. Google Analytics may record a purchase event by itself, with the product, price and currency, never payment details.

On the free plan, a single preparation can also be bought once, through Google Play or the App Store, where we offer it. The store handles the payment exactly as for the subscription; the app only learns that the purchase went through, and keeps the store’s purchase number on the phone so the same purchase is never counted twice.

The free plan’s count is kept on the phone and is not sent to us (section 4). So that the month cannot be changed by setting the phone’s clock, the app reads the current time from a server before a free preparation starts: an empty page at www.google.com, or Apple’s connection-check page at captive.apple.com where Google cannot be reached. Without an internet connection, a free preparation does not start. The request carries nothing about you or your videos; like any request, it shows Google or Apple your IP address.

9. Ratings, sharing and writing to us

Everything in this section happens only when you choose it.

10. Permissions and why they are asked for

Android

Videos and subtitle files are opened through the system file picker, which gives the app access only to the files you choose. Saving an exported file uses the system’s save dialog, where you choose the place.

iOS

Not requested at all

Dublio does not ask for your location, camera, microphone, speech recognition, contacts, calendar, phone, SMS, or your photo, video or music library. The speech in a video is recognised by the app itself, on the phone, from the file you chose.

11. Device backups

If your phone’s backup is switched on, Android may include some of the app’s data, such as settings and preparations, in the backup to your own Google account, under Google’s terms. On iPhone, the app keeps its files out of iCloud Backup. The free-plan counter (section 4) can be part of a backup too: on Android through Google’s Block Store, and on iPhone with the Keychain in an iCloud or encrypted computer backup. A backup belongs to your Google or Apple account, not to us, and we have no access to it.

12. What we do not do

13. Children

Dublio is not directed at children under 13, and we do not knowingly collect personal data from children. If you believe a child has sent us personal data in an e-mail, please contact us and we will delete it.

14. How long data is kept

Full instructions, including how to ask about the usage data, are on the data deletion page.

15. Changes to this policy

When the app starts using a new service or sending new data, this policy changes before that version reaches you, and the date at the top of the page changes with it.

16. Contact

For any privacy question or request about Dublio, use the contact page or write to inceptionapplication@gmail.com. We aim to answer within 30 days.

↑ Top