FeedDub
DemoObsługiwane serwisyCennikPytania
Sign inChrome Web Store

Privacy Policy

Effective 2026-09-27

FeedDub is a browser extension that dubs online videos into another language. This policy covers the FeedDub extension, the website feeddub.com, and the servers behind them ("FeedDub", "we").

We collect only what we need to dub the videos you choose, run your account and membership, and keep the service working. We do not sell your data, show ads, or use your data to train AI models.

1. Account information

Website sign-in uses the same Google account and membership as the extension. A necessary HttpOnly session cookie lasts up to 30 days; a login nonce cookie expires after 10 minutes. Signing out removes the website session cookie. Activation-code redemption stores the campaign, code hash, account ID, redemption time and granted expiry to prevent reuse and administer access. Administrators can view redemption records; full codes are only shown once when generated.

You can use the free allowance without signing in. The extension creates a random device ID, which our servers use to count your daily allowance. If you choose to sign in with Google, we receive and store your Google account ID, email address, name and profile picture link. We also record when your account was created, when it was last used, and when your free trial started.

We use this to identify your account, apply your trial or membership, and contact you about your account or payments.

2. Payment information

Payments are handled by Dodo Payments, which acts as the merchant of record. Your card number, bank details and wallet credentials go to Dodo Payments and never reach us.

From Dodo Payments we store your customer ID, subscription and payment IDs, the plan you bought, amount, currency, status, dates, and whether a payment was refunded or disputed. We use this only to decide what your membership includes.

3. Videos you choose to dub

The extension supports five video platforms: YouTube (including embedded YouTube players), Netflix, TED, Bilibili and Coursera. On these sites, it detects the player and can retain subtitle or media information locally so it is available for dubbing. It does not request access to Chrome's browsing-history API. The IDs of videos you use with FeedDub may be processed for dubbing, quota checks and diagnostics, as described below.

When you start dubbing, the extension reads the video's subtitles. On supported platforms where audio transcription is available, it can use audio instead: either your browser extracts it, or, for public videos, our server downloads it. Netflix dubbing uses available subtitles and does not transcribe DRM-protected audio. The subtitles or audio, the site name and the video ID are sent to our servers, which split the text into sentences, transcribe audio, translate the sentences and generate speech.

Hovering over the microphone can also prepare dubbing before you click. This may check the video's cached results and your allowance, read or process subtitles, and request translations or generated speech. Preloading translations that would consume a new free video allowance waits until you start dubbing.

Website access is limited to the supported platforms, approved media hosts and the service endpoints needed to provide FeedDub. Temporary rules for reading Coursera audio apply only to the current tab, the Coursera page and approved media hosts; they are removed when dubbing stops or the tab closes.

The results (sentence lists, translations, transcripts, generated speech and downloaded audio) are stored on our servers per video, so the same video loads faster for anyone who watches it later. A video's sentence list records the ID of the account that created it. Nothing else in these files identifies you.

4. Usage and diagnostic data

“Help improve FeedDub” is on by default and can be turned off in the extension popup. When enabled, the extension sends usage and diagnostic events during preparation and dubbing so we can find bugs and measure speed and cost. Each event may include:

  • your account ID if signed in, a random ID created when the extension is installed, and a session ID
  • extension version, Chrome major version, operating system type and browser language
  • the site and video ID (not the page address), the source and target languages, and the chosen voice
  • how long each step took, how many sentences were translated or spoken, and where playback was
  • the type of any error and a shortened error message

These events do not include page addresses, your IP address, or subtitle text. We keep them for 90 days.

Free usage has a daily allowance for new videos. To count it, we store today's video IDs against your signed-in account or, if signed out, your random device ID. The daily quota record resets each day; this is separate from the diagnostic retention period above.

Website analytics and ads measurement

Our public pages and the payment return page load two Google tags: Google Analytics measures page visits and Chrome Web Store clicks, and Google Ads measures which ads lead to installs and purchases. Google receives a cookie-based identifier, browser and device information, page paths and the referring site, and processes your IP address to derive approximate location. We do not send account details, payment information, URL query strings or video content to Google. Google signals and Analytics ad personalization stay off. Neither tag runs on the account page, and neither is included in the extension.

Google Analytics runs automatically without a confirmation step and is not controlled by Cookie settings or earlier analytics preferences. Google Ads measurement is on by default and can be turned off under Cookie settings in the footer. Turning ads measurement off sets its Google consent state to denied and deletes its existing cookies. Analytics cookies last up to 180 days and ads cookies up to 90 days; event-level retention is controlled separately in Google. Your choice is stored locally in your browser.

5. Data stored in your browser

The extension keeps your settings, your sign-in session, random device and install IDs, events waiting to be sent, and the result of the latest version check in Chrome's extension storage. Uninstalling the extension deletes all of it.

6. Service providers

These companies process data on our behalf, and each receives only what its task needs:

  • Cloudflare: hosts our servers, databases and file storage; its Workers AI transcribes audio when our main speech recognition provider fails.
  • Google: Google sign-in; Google Cloud BigQuery stores extension diagnostics; Google Analytics automatically measures website usage; Google Ads measures ad results unless you turn ads measurement off under Cookie settings.
  • Dodo Payments: payments, subscriptions, invoices and refunds.
  • OpenRouter and DeepSeek: translate subtitle text.
  • Microsoft: turns translated text into speech. When our servers cannot reach Microsoft, your browser may request the speech from Microsoft directly, and Microsoft then receives your IP address.
  • Alibaba Cloud Model Studio (Singapore region): transcribes audio for videos that have no subtitles.

These providers may process data in the United States, Singapore and other countries.

To read subtitles or audio, the extension talks to the video site using your existing session there. That site's own privacy policy applies to your use of it.

We do not share your data with anyone else, except when required by law.

7. How long we keep data

  • Account and membership data: while your account exists. Deleting your account on the account page clears your profile straight away, except payment records we must keep for tax and legal reasons.
  • Usage and diagnostic events: 90 days.
  • Sign-in sessions: expire after 30 days unless renewed.
  • Per-video results: kept to serve later viewers. The account ID stored with a sentence list no longer points to you once the account is deleted.

8. Your choices

  • Sign out at any time from the extension popup.
  • Turn off “Help improve FeedDub” in the extension popup to stop optional usage and diagnostic reporting. Requests needed to provide dubbing, check your account and apply usage limits still occur.
  • Delete your account yourself on the account page, on the website.
  • Email support@feeddub.com to access or correct your data, or to ask us to delete it.
  • Uninstall the extension to remove everything it stored in your browser.

9. Google user data

FeedDub's use of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. We use your Google account information only to sign you in and run your account, never for advertising, and we do not transfer it except to the service providers listed above as needed to run FeedDub.

10. Security and children

All connections between the extension, the website and our servers use HTTPS, and access to our databases is limited to the services that need it.

FeedDub is not intended for children under 13, and we do not knowingly collect data from them.

11. Changes

If we change this policy, we will post the new version on this page and update the effective date above.

Questions about this policy: support@feeddub.com

FeedDub
DemoObsługiwane serwisyCennikPytaniaChrome Web StorePomocZarządzaj subskrypcjąPrywatność
© 2026 FeedDub