Privacy Policy

1. Introduction

VidDub is a Chrome extension for real-time video dubbing. This Privacy Policy explains what information we collect, how we use it, and your rights regarding your data.

2. Information We Collect

2.1 Account Information

When you sign in, we receive basic profile information from your authentication provider (Google, Microsoft, or email): your account identifier (Firebase UID), email address, display name, and profile photo URL. This is used to identify your account, sync your subscription state, and provide support.

2.2 Data Logged on Backend Server

When you use VidDub, our backend server may log Firebase UID, video ID, platform, target language, provider, result, duration, error code, and timestamp. These fields are used to operate the service, manage subscription state, route processing, and monitor reliability. Quota accounting records (minutes dubbed per day) are tied to your account.

2.3 Dubbing History

If you are signed in, each dubbing session is saved to your account history so you can see what your credits were spent on: video ID, platform, target language, and result. It does not include the video's title or its page URL — the readable video name is kept only on the device that ran the dub and is never sent to us, so a session dubbed on another device shows its ID instead. History is kept until you delete it — there is no automatic expiry. You can view it in the extension and on this dashboard, and delete it all at once from either surface at any time.

2.4 Content Processed to Provide Dubbing

To dub a video, the extension sends the video's subtitle/transcript text and its title to our backend for translation and speech synthesis. When a video has no subtitles at all, a transcript has to be generated from its audio, and how that audio reaches us depends on the source. For some sources our backend can fetch the audio itself and the extension uploads nothing. Otherwise your browser reads the media, separates out the audio track only, and uploads that. If the audio cannot be separated, VidDub stops and tells you; it never uploads a video whole. You always know when this happens: VidDub asks before the first such upload from a site, and you can choose to allow that site without being asked again — the sites you have allowed are listed in the extension's Options → Privacy, where you can stop allowing any of them at any time. The upload is used only to generate subtitles for that video and is deleted as soon as transcription finishes; if it is interrupted or fails, a cleanup job removes it within 12 hours. Cached results are scoped to your account. VidDub never saves a media file to your device.

2.5 Local Extension Data

The extension stores user settings, cached subtitles, translations, TTS audio cache, and active processing state locally in your browser.

2.6 Anonymous Crash Diagnostics

VidDub may send sanitized error diagnostics to help debug production issues. Diagnostics do not include video URLs, video titles, channel names, subtitles, transcripts, translations, TTS text, cookies, API keys, authentication tokens, or page content.

To understand how well the product works overall, VidDub also keeps a random, anonymous installation identifier on your device and may send coarse usage and retention signals — for example a bucketed count of dubbing sessions, the number of days the extension has been installed, a coarse quality rating of your dubbing sessions overall (such as whether playback has generally been smooth or degraded), and a one-time anonymous "uninstall" ping when the extension is removed. These signals contain no personal information, no video URLs/titles, and no exact timestamps, and are governed by the same diagnostics setting — turning diagnostics off stops them and clears the uninstall ping.

Since August 2026 one of those signals carries a site's domain name, and only when VidDub could not dub that site: either you clicked the VidDub toolbar icon on a site it has not been built for and the attempt did not end in a working dub — nothing dubbable was there, the player was served from a domain VidDub was not allowed into, or VidDub's own code failed to start — or VidDub was running on a page and its dubbing button never appeared. A page VidDub dubs successfully never sends a domain. This tells us which sites to add support for and which bugs broke a site we already support. Only the shortest registrable form of the domain is sent — videos.example.co.uk/watch?v=abcd becomes example.co.uk — never the path, the query string, or the video's identity. Two domain names are sent: the page you opened, and — when the video is delivered by a different company — that video player's domain, for example a page on example.com whose video comes from mediadelivery.net. The player's full address is never transmitted, and a site that serves its own video names no second company. We need the player's domain because one player company can sit behind dozens of sites we cannot dub: without it, thirty broken sites read as thirty separate problems rather than one. It is capped at one report per site per day with a daily ceiling on distinct sites, it carries the same random installation identifier rather than your account, and turning diagnostics off stops it entirely.

2.7 Optional Feedback Screenshots

On VidDub's feedback forms — including the page shown after uninstalling — you may choose or paste up to three PNG, JPEG, or WebP images. Nothing is read from your clipboard unless you explicitly paste into the form, and only image files are considered. Each image is decoded and re-encoded in your browser before upload, removing EXIF metadata such as GPS coordinates. The pixels may still show private information, so please review every image before sending. Screenshots are used only to investigate feedback, are available to administrators through short-lived signed links, and are deleted after 90 days.

2.8 Information Not Collected

• Video files — except the audio track of a local/private video that you explicitly confirm uploading for subtitle generation (see 2.4)
• Browsing history — with one narrow, disclosed exception: the domain names (never a full address) of a site VidDub could not dub and of the video player on it, described in 2.6
• Keyboard, mouse, microphone, or camera data; clipboard data is not read except for an image you explicitly paste into a feedback form as described in 2.7
• Precise location — a coarse, IP-derived country code may be used to pick sensible default languages

3. How We Use Data

We use logged data to provide and improve the service, optimize performance, monitor reliability, debug sanitized crashes, manage costs, and comply with legal requirements.

4. Data Retention

Retention depends on the record type. Your dubbing history is kept until you delete it — there is no automatic expiry. Feedback text and structured responses are kept for up to 365 days; attached screenshots are deleted after 90 days. Short-lived operational records, such as paid-playback minutes and abandoned private upload sessions, are removed by a scheduled cleanup that runs every six hours. Cached synthesised speech and transcripts held on object storage are not covered by these periods: synthesised speech is keyed by content and shared between users, while a transcript generated from a file you supplied is stored under an account-scoped path. You can delete your dubbing history at any time from the extension or the dashboard, or request deletion by contacting us.

5. Data Sharing

We do not sell or rent your data. We share data only with service providers acting on our behalf to provide the service, under confidentiality obligations, or with law enforcement if legally required. Our processing providers include cloud infrastructure (Cloudflare, Google Firebase, Microsoft Azure, Modal) and AI processing services: subtitle text is processed for translation and speech synthesis, and in a limited fallback mode may be processed by Google translation and Microsoft speech endpoints.

6. Your Rights & Account Deletion

You may request access, deletion, portability, or withdrawal of consent by contacting support.

Account deletion: you can delete your VidDub account and associated data (profile, dubbing history, quota records, feedback) from the self-service deletion page. The deletion flow removes linked billing customer data where available, deletes backend account records, and then deletes the Firebase Authentication account. It does not clear the cached synthesised speech and transcripts held on object storage, described in section 4. Some minimized billing or fraud-prevention records may be retained where required by law. You can also delete your dubbing history yourself at any time from the extension or the dashboard, and clear all local data from the extension's settings page.

7. Security

We use TLS/SSL to protect data in transit. No transmission method is 100% secure, and we cannot guarantee absolute security.

8. Changes

We may update this policy from time to time. Material changes may be communicated by email, in-app notification, or the updated date on this page.

9. Contact

For privacy questions, contact [email protected].