Privacy Policy
Last updated: 6 September 2026
Applies to: the YT Transcript AI browser extension, version 1.2 and later
The extension has no servers of its own. Your keys and preferences stay in your browser, and the transcript only leaves it when you press an AI action, on its way to the provider you configured.
Summary
- The extension does not collect, store or receive any of your data. There are no developer servers.
- Your API keys and preferences are stored only in your browser.
- The video transcript is sent only to the AI provider you configured, and only when you press an AI action.
- No accounts, no sign-up, no analytics, no tracking, no advertising.
- The extension activates only on
youtube.compages. Everywhere else it stays disabled.
Who is responsible
This extension is developed and maintained by Franyer Verjel, acting as data controller for the purposes of the General Data Protection Regulation (GDPR).
In practice no processing of personal data takes place on the developer’s side, because no data ever leaves your device towards the developer’s infrastructure. Contact details are at the end of this document.
What data the extension handles
1. Transcript and video metadata
When you open the side panel on a YouTube video, the extension reads the title, channel, duration, video URL and the list of available subtitle tracks from that page, and downloads the transcript.
This information is held in browser memory while the panel is open. It is not written to disk and it is not transmitted anywhere, except in the case described below.
If you press an AI action (Summary, Insights, Blog post or Custom), the transcript and the corresponding prompt are sent to the AI provider you selected, using your own key. If you never press one of those actions, the transcript never leaves your browser.
2. API keys
Any API key you enter is stored in chrome.storage.local, a local store in your browser. It is not synced to your Google account or to any other device.
Each key is sent exclusively to the provider it belongs to, as the authorization header of your own requests:
| Key | Only destination |
|---|---|
| OpenRouter | openrouter.ai |
| OpenAI | api.openai.com |
| Anthropic | api.anthropic.com |
| Google Gemini | generativelanguage.googleapis.com |
The developer has no access to these keys at any time.
3. Preferences
The active provider, the model chosen per provider, the temperature, the output language, the preferred transcript language and any prompts you customised are stored in chrome.storage.sync.
That store is managed by your browser and, if you have Chrome sync enabled, it travels between your devices through your Google account, subject to Google’s privacy policy. It never passes through a developer server. API keys are never stored here.
4. Model catalogue
So that the model search works without a network round-trip for 24 hours, the public list of models returned by each provider is cached in your browser. This is public catalogue information and contains no personal data.
Where data goes
The extension communicates only with these destinations:
- YouTube (
www.youtube.com,m.youtube.com), to read the subtitles of the video you are watching. - The AI provider you selected, to generate the output you requested and to fetch its model list.
There is no other destination. In particular, there is no server belonging to the extension.
What the AI provider does with the transcript you send is governed by its own privacy policy, and the contractual relationship at that point is between you and that provider:
We recommend reading the policy of the provider you use, especially if you plan to process transcripts of sensitive or confidential content.
What the extension does not do
- It does not collect analytics, telemetry or usage statistics.
- It does not build user profiles or identifiers.
- It does not show advertising.
- It does not sell, share or transfer data to third parties.
- It does not read your browsing history, saved passwords or autofill data.
- It does not access any page other than
youtube.com. - It does not load or execute remote code. All code ships inside the extension package.
Permissions and why they are needed
| Permission | What it is used for |
|---|---|
storage | Save your preferences and API keys in the browser. |
sidePanel | Show the extension interface in the browser side panel. |
scripting | Activate the subtitle reader in a YouTube tab that was already open before the extension was installed, without forcing you to reload it. |
Access to youtube.com | Read the subtitle tracks of the video you are watching. No other data from your YouTube account is accessed. |
| Access to the AI provider domains | Send the transcript and your prompt to the provider you selected, with your own key, and fetch its model list. |
Retention and deletion
Everything the extension stores stays in your browser until you delete it. You can do that in any of these ways:
- Clear an API key field on the options page and save.
- Remove the extension’s data from
chrome://extensions. - Uninstall the extension, which removes its local storage.
The model catalogue cache expires on its own after 24 hours.
Legal basis and your rights
Because the developer neither receives nor stores personal data about you, there is no processing against which to exercise rights of access, rectification, erasure, objection or portability towards the developer: control over the information is yours and direct, through the options described above.
As for the data you choose to send to an AI provider, that transmission happens at your own explicit request when you press an action, and your rights are exercised with that provider under its privacy policy.
If you still have a question or wish to raise a complaint, you can write to the contact address below. You also have the right to lodge a complaint with the data protection authority in your country.
Children
The extension is not directed at children under 13 and does not knowingly collect data from any person, regardless of age.
Chrome Web Store User Data Policy
YT Transcript AI’s use of information received complies with the Chrome Web Store User Data Policy, including its Limited Use requirements.
Changes to this policy
If the extension changes how it handles data in the future, this policy will be updated and the “Last updated” date will change. Material changes will also be noted in the release notes for the version concerned.