Legal

Privacy Policy

Effective date: February 2026  ·  Last updated: February 2026
Your data is not sold to third parties

We do not sell, rent, trade, or otherwise transfer any user data to third parties — under any circumstances, including approved use cases.

The extension has no backend server that receives your data. There is no user account system, no analytics pipeline, and no advertising infrastructure.

The only external network requests made by this extension are: (1) subtitle text sent to the AI API endpoint you configure, and (2) translation prompt templates fetched from our Cloudflare Pages endpoint. Neither involves personal data.
Data is not used for purposes unrelated to core functionality

The extension's sole purpose is translating YouTube subtitles. Every network request it makes is directly in service of that function.

Subtitle text is sent to the AI API endpoint you configure (e.g. OpenAI, Gemini, DeepSeek, or our free built-in tier) solely to obtain a translation. This data is not used for model training, profiling, advertising targeting, or any other secondary purpose by us.

When using the free built-in tier, subtitle text is routed through our Cloudflare Worker proxy to a third-party AI provider (via Portkey). The proxy injects the API key server-side and does not log or store your subtitle content. The third-party AI provider's own privacy policy governs their handling of request data.

Your API keys, language preferences, and display settings are stored exclusively in your browser's chrome.storage.local and never leave your device.

Data is not used to determine creditworthiness or for lending

This extension has no financial, credit, or lending functionality whatsoever. No data collected or processed by this extension is used — or could be used — to assess creditworthiness, financial risk, or eligibility for any financial product.

What data is processed and where

The table below describes every category of data the extension touches.

Data Where it goes Stored?
YouTube subtitle text Sent to your configured AI API endpoint for translation In transit only
AI API key Stored locally; sent only to your configured API endpoint as an auth header Local only
Language preferences Stored locally in chrome.storage.local Local only
Display settings Stored locally in chrome.storage.local Local only
Browsing history / URLs Not accessed or transmitted Never
Personal identity data Not collected Never
Analytics / telemetry Not collected Never

Third-party AI providers

When you configure your own AI model, subtitle text is sent directly from your browser to that provider's API. We have no visibility into or control over how that provider handles the data. Please review the privacy policy of your chosen provider:

OpenAI Privacy Policy  ·  Google Privacy Policy  ·  DeepSeek Privacy Policy

When using the free built-in tier, requests are routed through our Cloudflare Worker (ycct-proxy.whatareyou.workers.dev) which proxies to an AI provider via Portkey. The Worker validates a shared extension secret to restrict access, injects the API key, and forwards the request. No request content is logged or stored by the Worker.

Chrome permissions explained

storage — Used to save your settings (API keys, language preferences, display options) locally in your browser. Data never leaves your device via this permission.

sidePanel — Used to display the settings panel inside Chrome's native side panel UI.

https://www.youtube.com/* — Required to inject the translation button and caption overlay into YouTube pages.

https://*/* — Required because users can configure any HTTPS endpoint as their AI API (e.g. a self-hosted model, a corporate proxy, or any OpenAI-compatible service). The extension cannot know in advance which host you will configure, so broad HTTPS access is necessary. This permission is used exclusively to make translation API calls to your configured endpoint.

Changes to this policy

If we make material changes to this privacy policy, we will update the effective date above. Continued use of the extension after changes constitutes acceptance of the updated policy.

Questions about this privacy policy?

Open an issue on GitHub or reach out via the Chrome Web Store listing.