Account Live stats
← Back to home

Legal

Privacy Policy

Effective date: August 27, 2026

1. Overview

This Privacy Policy explains how livdub handles information when you use our website, Chrome extension, Android app, and related services.

livdub is a bring-your-own-key (BYOK) live dubbing product with anonymous Free use and optional Google-authenticated paid Plus accounts. Live dubbing runs on your device: tab, phone, or microphone audio is captured locally and sent to Google Gemini Live Translate using your Gemini API key. livdub servers are not on the live translation path and do not store arbitrary-site audio for replay or reuse. Chrome stays ad-free. Android Free may show Google AdMob ads; Plus never initializes the ads SDK.

livdub is not affiliated with, endorsed by, or sponsored by Google. Google and Gemini are trademarks of Google LLC.

2. What livdub servers do not receive

For live dubbing and anonymous usage sharing, livdub servers do not receive:

  • your Gemini API key (it stays in Chrome extension storage on your device);
  • tab audio or dubbed audio;
  • full page URLs or page titles in usage events;
  • precise location;
  • caption text, transcripts, recordings, or exported files;
  • Plus identity or payment data associated with browsing or translation content.

Separately, when your browser or the extension talks to our website or APIs, our hosting provider may process ordinary network request metadata such as IP address and user agent for security and reliability. A coarse country code may be derived from that request geography and rolled into anonymous public stats (for example, which country contributes the most minutes for a language). We do not publish IP addresses or install identifiers in those aggregates.

3. Information We Collect

  • Audio (on your device → Google only). When you start a dub, the extension captures active-tab audio and streams it from your device to Google Gemini under your API key. livdub does not relay that audio through our servers for translation. Google processes it under Google's terms and privacy policies for your Gemini relationship.
  • Local extension settings. Stored on your device in Chrome extension storage, including your Gemini API key, selected language, a legacy installation identifier, a separate random telemetry identifier, a non-extractable device private key, local session history, telemetry detail preference, and related UI metadata (for example a site domain or host, and while a session is active an optional tab title for the popup). Your Gemini API key is never sent to livdub.
  • Anonymous usage events. When an eligible dubbing session ends (generally at least five seconds), the extension may send a summary. These events are kept separate from Livdub account and billing records. They use a random telemetry identifier that is not the legacy installation identifier used for founding qualification, the signed device identifier used for quotas, or an account identifier. Events include event type, a session ID, target language, UTC day and hour, and duration. At ingest, we may also attach a coarse country derived from request geography (not precise location) and store it only in anonymous day-level rollups.
    • Less detail: language, session length, and timing — no website domain.
    • More detail (default): the same fields, plus the website registrable domain (for example, youtube.com), not the full URL.
    You can switch Less / More detail in the extension Usage stats page. Clearing extension storage removes the local identifiers, local history, and stored key on that device.
  • Android ads (Free only). The Android app may show Google AdMob banners, start interstitials, and optional rewarded ads after the daily Free minutes are used. Google’s ads SDK and User Messaging Platform (UMP) may process an advertising ID (AAID), coarse device and network signals, and consent choices so Google can fill ads and honor regional privacy prompts. livdub does not send AAID, advertising identifiers, or ad-click data to livdub servers, and does not join them to device keys, Google account email, or telemetry identifiers. Rewarded extra minutes are granted only after Google’s server-side verification callback, using a one-shot nonce bound to the signed Android device — not an advertising ID. Plus never initializes AdMob. Uninstalling the app, Android’s ads settings, and UMP choices control this path.
  • Device authentication and quota. The extension registers a public cryptographic device key. We store that public key, device status, signed-request nonces, Free cohort, active lease, active translation time, daily allowance and grace use. The private key remains non-extractable on your device. The old install identifier is eligibility metadata, not an authentication credential.
  • Plus account and billing information. If you use Plus, we use Google authentication with only the email scope. We store a keyed hash of Google's stable account identifier, encrypt your verified email at rest, and store a separate keyed email hash for exact lookup. In Google Chrome, the extension sends a short-lived Google access token to Livdub once over its signed device channel; we validate it against Livdub's Chrome Extension OAuth client and discard it. Other supported Chromium browsers use a short-lived authorization-code flow protected by one-time state, nonce, PKCE, and a redirect bound to the signed extension device. Website sign-in also uses a server-side Google authorization code. Google access and ID tokens from all paths are validated and discarded without being stored. We store account-device membership (Plus allows two registered devices; a third sign-in replaces the least-recently used device), entitlement and non-browsing usage state, checkout/payment identifiers, subscription status, purchase amount, payment method, refund and dispute state, and administrative audit records. Stripe and Link collect your name, email, phone number, billing address, and payment method to process the purchase. Livdub does not receive complete card details.
  • Website and API request metadata. Visiting the marketing site or calling our APIs may generate standard hosting logs (IP, user agent, timestamps) as described above. The marketing site may also use Google Analytics and/or Cloudflare Web Analytics (or a similar analytics service) to collect site usage data such as page views, approximate visitor country or region, and performance metrics; see Cookies and Local Storage and How We Share Information. Website analytics are separate from anonymous usage events from the extension and do not receive tab audio or your Gemini API key.
  • Communications. If you email us, we keep what you send and related support records. If you use Plus, we may send transactional account, billing, and security notices (for example payment failure, cancellation, payment disputes, and device changes) to the verified Google email. These are not marketing messages.

4. Chrome Extension Data Handling

Capture starts only after you begin a dubbing session. An offscreen document handles tab capture, the Gemini Live connection with your key, and playback. Preferences and your Gemini API key remain local unless you clear extension storage or uninstall. You can stop dubbing from the extension at any time.

5. How We Use Information

We use information to:

  • operate the marketing website and optional public aggregate stats;
  • authenticate devices, issue session capabilities, enforce daily allowances and concurrency;
  • show Android Free ads through Google AdMob after UMP consent, and grant rewarded extra minutes only after a verified AdMob callback;
  • authenticate Google accounts, provide Plus, process purchases and refunds, send transactional Plus notices, and prevent account or payment abuse;
  • receive and roll up anonymous usage events from the extension;
  • debug, secure, maintain, and improve the service;
  • detect abuse and enforce policies;
  • comply with legal obligations;
  • respond to support requests.

6. AI Translation Providers

Live dubbing sends audio from your device to Google Gemini using your API key. Free-tier Gemini usage may be used by Google to improve products as described in Google's policies. We do not use arbitrary-site live audio to build a shared livdub replay or translation cache.

7. How We Share Information

Free users do not need an account. Plus uses a minimal Google identity and limited billing records, which we keep separate from anonymous browsing and translation aggregates. We do not build a profile of what an account watches, translates, records, or exports. Other limited information can include hosting logs, marketing-site analytics, and information you send to support.

Where we do hold or process limited information, we may share it as follows:

  • Service providers that host our infrastructure, deliver transactional email (Cloudflare Email Sending), or help with support.
  • Payment provider. Stripe processes subscription checkout, billing and refunds, including through Link. Stripe and Link receive the name, email, phone number, billing address, and payment method needed for those transactions under their own policies.
  • Analytics providers. When you visit the marketing website, Google Analytics and/or Cloudflare Web Analytics (or a similar provider) may receive site usage data — for example page views, approximate country or region, device or browser information, and performance metrics — under those providers' policies. That path does not include tab audio, Gemini API keys, or anonymous usage events from the extension.
  • Google ads (Android Free). AdMob and UMP run in the Android app for Free users. Google may receive an advertising ID and device/network signals to fill ads. livdub does not receive those identifiers and does not join them to device keys, Google account, or telemetry.
  • Google authentication. When you choose to connect or sign in to a Livdub account, Google authenticates you and provides Livdub a stable account identifier and verified email. Livdub requests no Google profile, Drive, Gemini, Cloud, or offline-access scope. This is separate from both anonymous extension telemetry and the Gemini live-audio path.
  • Google (your BYOK path). When you dub, audio goes from your device to Google Gemini under your API key. That is your relationship with Google, not livdub sharing personal information from our systems.
  • The public, in aggregate. The website may show rollups from anonymous usage events — for example total minutes and sessions, language totals, activity by UTC hour, (when enough data exists) top domains, and which country has the most minutes for a language (from request-geography country codes, not precise location). These aggregates are not tied to a Livdub account or install id.
  • Legal and safety recipients when required by law or reasonably necessary to protect rights, safety, or the service.
  • Business transfers. If we ever transfer assets in a merger or sale, limited information we hold may move with the service, subject to appropriate confidentiality where applicable.

We do not sell personal information. We do not create shared reusable dubbed output from arbitrary captured tab audio.

8. Cookies and Local Storage

The website uses a secure, HTTP-only cookie when you sign in to the account dashboard. The cookie contains a random session token; Livdub stores only its hash. Short-lived HTTP-only state cookies protect Google sign-in against request forgery. The marketing website may also use Google Analytics and/or Cloudflare Web Analytics (or a similar analytics service) to understand traffic, performance, and improve the site. Google may set cookies or collect usage data as described in Google's Privacy Policy. Cloudflare Web Analytics typically uses a privacy-oriented beacon and does not rely on cookies for that measurement. Website analytics apply to the marketing site only; they are separate from anonymous usage events sent by the extension, and they do not receive tab audio or your Gemini API key.

The extension uses Chrome extension storage for local preferences (language, Gemini API key, legacy installation identifier, independent random telemetry identifier, session history, entitlement display state, a time-limited Livdub account credential after Google authentication, and Less / More telemetry detail) and IndexedDB for its device key. Native Google access tokens used in Chrome are removed from Chrome's token cache after validation. Browser-neutral authorization codes are single-use, and Livdub does not store the resulting Google access or ID tokens.

9. Retention

We retain server-side information only as long as reasonably needed to operate public stats, debug issues, comply with law, resolve disputes, prevent abuse, administer billing/refunds, and enforce agreements. Expired nonces, Google sign-in flows, dashboard sessions, checkout attempts and leases are deleted on scheduled retention windows. Payment, transactional-email send metadata (kind, identifiers, delivery status — not the recipient address or message body), and audit records may be kept as required for tax, accounting, fraud, chargeback and legal obligations. Aggregate anonymous telemetry may be retained longer than ephemeral live audio processed on your device and by Gemini.

Live tab audio is processed ephemerally by the extension and by Gemini under your key. livdub does not retain that audio as a shared cache. Local session history stays on your device until you clear it or uninstall.

10. Security

We use measures designed to protect information, including a design that keeps live arbitrary-site audio and Gemini API keys off livdub servers. No method of transmission or storage is completely secure. You are responsible for safeguarding your Gemini API key.

11. International Transfers

livdub and its providers may process information in the United States and other countries. Google may process Gemini audio in locations described in Google's policies.

12. Your Choices and Rights

Most privacy controls are self-service on your device:

  • stop a live dubbing session anytime from the extension;
  • switch Less / More detail for anonymous usage sharing on the extension Usage stats page;
  • clear Chrome extension storage to remove your Gemini API key, local session history, install identifier, and device private key on that device;
  • view or revoke registered playback devices from the account dashboard (a third Plus sign-in also replaces the least-recent device);
  • cancel a Stripe subscription through the dashboard's billing portal link;
  • sign out of the Livdub account dashboard;
  • uninstall the extension, Android app, or stop using the website.

Free users generally have no account record. If you have Plus, contact legal@livdub.com to exercise applicable access, correction, deletion, or other privacy rights. Some billing, security, and audit records may need to be retained. Your Gemini key and local history stay on your device and are cleared by you. To delete a Livdub account, follow Delete your Livdub account.

13. Delete your Livdub account

This section is the account-deletion request for the Livdub Chrome extension, Android app, and website. Free use does not create a Livdub account; uninstalling the app or extension is enough. Plus accounts are created with Google sign-in (email scope only). You can request deletion without installing Livdub.

Steps:

  1. If you pay for Plus, cancel first so billing stops: Android Play subscriptions in Google Play, or Stripe billing from livdub.com/account. Deleting the Livdub account does not cancel Google Play or Stripe by itself.
  2. Email legal@livdub.com from the same Google address you used for Plus.
  3. Use the subject line Delete my Livdub account and say that you want the Livdub account and associated personal data deleted.
  4. We confirm the request and complete deletion within 14 days, and no later than 30 days, unless a shorter period is required by law.

Deleted. The Plus account record, keyed hash of the Google account identifier, encrypted email and email hash, account–device membership, Plus entitlement for that account, and dashboard sessions. After deletion you can still use Livdub Free on the same device; that device’s local Gemini key and quota identity are not the account.

Retained, and why. Payment, tax, accounting, fraud, chargeback, and legal records (including Stripe or Google Play records those providers keep under their own policies); transactional-email send metadata (kind, identifiers, delivery status — not the message body); and administrative audit records required to comply with law, resolve disputes, or prevent abuse. Anonymous usage telemetry is not tied to a Livdub account and is not deleted as part of account deletion. Advertising identifiers on Android are processed by Google AdMob, not stored by livdub; reset or opt out in Android ads settings. Data only on your device (Gemini API key, local session history) is removed by you: clear extension storage or uninstall.

14. California and Other State Privacy Notices

If applicable privacy laws give you additional rights, we will honor those rights as required. We do not sell personal information. On Android Free, Google AdMob may use the advertising ID and related signals to show ads; that advertising activity is Google’s, not a livdub sale of your dubbing history. We do not join advertising identifiers to device keys, Google account identity, or telemetry. Chrome has no ads. Plus does not initialize the ads SDK. You can reset or opt out of the advertising ID in Android settings and use the in-app UMP consent form where required. If our advertising practices change, we will update this Policy and provide required choices.

15. Children

livdub is not directed to children under 13, and we do not knowingly collect personal information from children under 13. Contact legal@livdub.com if you believe a child provided personal information to us.

16. Changes

We may update this Privacy Policy from time to time. The updated version will be posted on this page with a new effective date. Material changes may include additional notice as appropriate.

17. Contact

Contact: legal@livdub.com.