Privacy policy
Last updated October 28, 2026
This policy explains what personal data myDubber processes, why, where it is kept and for how long, and what you can do about it. myDubber is the Chrome extension, the local backend it installs on your computer, our dubbing server and the site mydubber.com.
Who we are
myDubber is run by Sole proprietor (FOP) Behashevskyi V. M., Nyzhnya Hyivska St, 52, Kharkiv, 61000, Ukraine (“we”). We decide how your data is used, so we are its controller. Write to [email protected] about anything on this page.
In short
- On Local, the dub is made on your own computer. Nothing about what you watch is sent to us.
- On Server, our server receives the address of the video you dub, your languages and the playback position, and makes the dub.
- With an account, we keep your email, your plan, how many minutes you used and a few facts about your setup.
- We sell nothing, show no ads and run no analytics or tracking cookies.
What the extension does
The extension runs only on YouTube pages (www.youtube.com, m.youtube.com), and sends anything only from tabs where you turned the dub on. For those tabs it sends the backend you chose:
- the video’s address;
- the playback position;
- the languages you picked;
- playback events: play, pause, seek, speed, and whether the tab is visible.
It reads nothing else from the page and nothing from your browsing history.
Your settings, such as languages, backend and theme, are kept in Chrome’s extension storage, which Chrome may sync between your own browsers. The state of each tab is gone when Chrome closes. When you sign in, the extension keeps its sign-in tokens in Chrome’s local storage on your computer. It reads the site’s own sign-in cookie on mydubber.com, so that signing in on the site signs the extension in too.
On Local
The local backend runs on your computer and answers only the extension.
- It fetches the video’s audio from YouTube, as your browser would.
- Speech recognition, translation and voices all run on your graphics card. Nothing about what you watch is sent to us or to anyone else.
- The dub is kept in a cache on your disk and deleted 36 hours after you last watched it.
- Its logs stay on your disk. You can send them to us yourself when you report a problem.
When you install or update the backend, it downloads the program from GitHub and the models and tools from their official sources: Hugging Face, Ollama, Python’s package index and Deno. Those services see your IP address, as with any download.
On Server
On Server, the same work happens on our machines:
- Our server receives the video’s address, the playback position and your languages, fetches the audio from YouTube and makes the dub.
- Dubs go into a shared cache, so the next person who watches the same video in the same languages gets it at once. The cache holds the dub, not who asked for it. A dub is deleted three days after anyone last watched it.
- To count your minutes, we record which video you dubbed, when and for how long, linked to your account.
Your account
You need an account for Server and for the Medium and Full profiles on Local. For it we keep:
- Identity: your email address. If you sign in with Google, also the name and picture Google gives us.
- Sign-ins: for each sign-in on the site, its time, your IP address and your browser’s name, so you and we can see and end sessions. Used sign-in codes and tokens are stored only as hashes.
- Plan and usage: your plan, the trial dates, dubbed minutes per period and the videos counted in them.
- Setup: once a day while you are signed in, the extension tells us your backend (Local or Server), profile, extension version and target languages. It never sends video addresses in this report. We use it to support you and to decide what to improve.
- Email preferences: whether you agreed to news and offers, when and where, and whether your address bounces.
Payments
Paddle.com sells Pro to you as our reseller and merchant of record. Paddle takes your card, charges VAT where it applies and sends the receipt, under Paddle’s privacy notice. Your card details never reach us. Paddle tells us your subscription’s status, its period, a customer number and the last four digits of the card, for your account page.
We send account emails: sign-in codes, a used-up limit, a trial about to end or a failed payment. News and offers come only if you ticked that box, and every such email has a one-click unsubscribe link. If you unsubscribe, we keep your address on a do-not-send list, so that you stay unsubscribed.
Cookies
The site sets only the cookies it needs: your sign-in session and the language you picked. Paddle’s checkout sets its own cookies when you open it to pay. There are no analytics or advertising cookies, so the site asks for no cookie consent.
Why we may use your data
- To provide the service you asked for (the contract with you): the account, dubs on Server, minutes and plans, account emails.
- Legitimate interests: keeping the service secure and working, which means sign-in records and server logs, and the daily setup report that tells us what to improve.
- Your consent: news and offers. You can withdraw it at any time.
- Legal obligations: records that tax and accounting law require. Paddle keeps most of these.
Who else processes it
We use these providers. Each receives only what its job needs.
- Hetzner
- What it does
- Runs our servers: the site, the gateway, the media workers
- Where
- EU region (Germany)
- Neon
- What it does
- Hosts our database: accounts, plans and usage
- Where
- EU region (Frankfurt)
- Cloudflare
- What it does
- Stores the shared dub cache (R2) and answers our DNS
- Where
- EU region
- RunPod
- What it does
- Rents us graphics cards that turn audio into dubs; they see audio, not accounts
- Where
- EU region
- Resend
- What it does
- Sends our emails
- Where
- EU region
- Google
- What it does
- Sign-in with Google, if you use it
- Where
- USA, under the EU–US Data Privacy Framework
- Paddle
- What it does
- Payments, as merchant of record
- Where
- UK
- GitHub
- What it does
- Hosts the backend’s installer and updates
- Where
- USA, under the EU–US Data Privacy Framework
Everything we run is in the EU region: our servers, the database, the dub cache, the graphics cards and email. Only sign-in with Google, payments and the installer’s downloads go through providers outside it. Where data leaves the European Economic Area, the transfer relies on the European Commission’s adequacy decisions or its standard contractual clauses.
How long we keep it
- Your account: until you delete it. Then we remove your personal data within 30 days, except what the law makes us keep.
- Usage and the videos counted: as long as your account exists.
- Server logs: with IP addresses, up to 30 days.
- Shared dubs: three days after anyone last watched them, with no link to you.
- Do-not-email list: your address only, for as long as it must stay unsubscribed.
- Payment records: Paddle keeps them as tax law requires.
Your rights
You may ask us for a copy of your data, to correct it, to delete it, to restrict or object to how we use it, or to receive it in a portable format. You may withdraw consent to news at any time. Write to [email protected] from your account’s address, and we answer within one month. To delete your account, write to the same address. If you think we handle your data wrongly, you may complain to the data protection authority where you live.
Children
myDubber is not meant for anyone under 16, and we do not knowingly keep accounts of children.
Voices
Each speaker is dubbed in a synthetic voice modelled on their own, made on the fly for your viewing. We keep no voice model of any person beyond the cache times above, and we never use what you watch to train models.
Changes
When this policy changes in a way that matters, we update the date at the top and, for changes that affect your account, email you before they apply.