Policy
Plain-language information for the beta version of AI Live Translator.
Last reviewed 2026-07-30 · Published by the AI Live Translator product team
This Privacy Policy explains how AI Live Translator handles data for the Chrome extension, public website, account pages, billing flows, and support for the current beta service.
The current product is a listen-only Chrome extension. It translates audio from the browser tab you choose into translated speech and live captions while the source keeps playing.
When you press Start, the extension captures audio from the selected browser tab so the live translation feature can work. The extension also processes your selected target language, caption setting, volume settings, active-session status, and minute entitlement state.
Translated audio is played back during the session and live captions are shown during the session. Raw audio, translated audio, captions, and transcript text are not stored by AI Live Translator by default in the Stage 2A beta build.
Audio capture starts only after you take an explicit action, such as pressing Start in the extension. The extension must show that live translation is running while capture is active.
Pressing Stop ends capture for that tab, stops the live translation session, and ends the active minute timer. The extension is not designed to capture audio in the background without your action.
During an active translation session, audio from the selected browser tab is sent to OpenAI to generate translated speech and captions. The standard OpenAI API key stays on our backend; the browser receives only a short-lived client credential needed for the active session.
We send this audio only to provide the live translation feature. We do not use it for advertising, sell it to data brokers, or use it to determine creditworthiness.
The extension does not collect browser history, screenshots, page DOM content, meeting URLs, video URLs, tab titles, cookies, passwords, keystrokes, local files, contacts, calendars, or email content for the translation flow.
If you create or use an account, we store the account identifier, verified email status, selected sign-in provider, authentication state needed by the web account, and extension-link state needed to connect the extension to your account.
Supabase powers authentication and account storage. Google or Microsoft may authenticate your identity when that sign-in method is enabled and selected. Email-code sign-in uses our configured email delivery provider to send one-time codes.
We store minute balances, trial eligibility, active translation session identifiers, usage-minute events, plan and top-up identifiers, Stripe customer identifiers, Stripe subscription or checkout identifiers, Stripe event status, and top-up purchase records needed for billing and entitlement.
We also process limited anti-abuse signals, such as hashed installation identifiers, verified email status, signup and session timing, content-free usage-minute events, coarse risk signals, and payment or dispute signals. We use these signals for security, fraud prevention, abuse prevention, entitlement enforcement, and service reliability, not for advertising.
Payment card numbers, payment method details, hosted checkout forms, invoices, and payment authentication are handled by Stripe. AI Live Translator stores Stripe identifiers and statuses, not card data.
Website analytics, when configured, measure public website and billing funnel events. Product telemetry and logs are intended to be content-free: event names, status codes, timing, entitlement state, minute reservations or debits, and redacted error categories.
Audio, captions, transcript text, translated text, meeting or video URLs, participant names, emails, provider client secrets, API keys, tokens, request headers, and payment-card data must not be sent to marketing pixels or written to routine operational logs.
Current provider categories include OpenAI for realtime translation, Supabase for authentication and account storage, Stripe for checkout and billing portal flows, Vercel for website and API hosting, our configured email delivery provider for one-time sign-in codes, Google or Microsoft identity services when selected, and analytics or error-monitoring tools if configured.
Raw tab audio, translated audio, live captions, and transcript text are session-only by default and are not retained by AI Live Translator after the active translation session as product records.
Account, billing, minute ledger, security, and anti-abuse records are retained while needed to provide the service, keep accounting records, enforce usage limits, handle payment status and disputes, comply with legal obligations, and protect the service. Local extension preferences may remain in the browser until you change them, clear extension data, or uninstall the extension.
Support and operations should not need raw audio, captions, transcripts, meeting URLs, video URLs, participant names, cookies, tokens, request headers, or payment-card data. Do not include those items in support requests.
Human access to account, billing, security, or diagnostic records is limited to cases such as your requested support, security investigation, abuse prevention, legal compliance, or business operations using aggregated or de-identified data where appropriate.
You can stop translation at any time from the extension. You can change target language, captions, and volume settings in the extension. You can manage an active subscription through the Stripe Billing Portal when it is available for your account.
Contact support to request access, correction, deletion, or export of account information where applicable. Some billing, security, ledger, dispute, and legal records may need to be retained even after an account request.
The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements. We use extension data only to provide or improve the disclosed live translation purpose, operate and secure the service, enforce entitlements, prevent abuse, comply with law, and communicate with you about the service.
If our data practices materially change, we will update this policy and provide any required in-product disclosure before the new practice applies. For privacy requests or questions, contact contact@livetranslation.pro.
