Privacy Policy

Last updated — August 2026

VoxAI is built to need as little of your data as possible, because it doesn't run its own server to send it to. This page says exactly what that means in practice.

What VoxAI does not do

Where your data actually goes

When you use a feature, the request goes directly from your browser to the provider that performs it — YouTube's own caption endpoints for transcripts, Groq for Whisper transcription, or Google Gemini / OpenRouter for translation and AI analysis — using your own API key. VoxAI is the messenger, not a middle party that keeps a copy.

Where your API keys live

Your API keys are stored in chrome.storage.local — a storage area private to your own browser profile on your own device. VoxAI never transmits your keys anywhere except directly to the provider that owns them (e.g. your Groq key only ever goes to Groq).

What's cached, and for how long

To avoid burning your API quota re-fetching or re-analyzing a video you've already opened, VoxAI keeps a local cache of transcripts and analyses in your browser. It clears automatically after 30 days and never leaves your device.

Permissions

The extension requests only the Chrome permissions it needs to read the active YouTube tab and call the AI providers you've configured — listed in full in manifest.json in the public source repository.

Changes to this policy

If this ever changes — for example if a future feature needs a server — this page will be updated first, and the change will be reflected in the extension's version notes.

Contact

VoxAI is built and maintained by Anvilon LLC. Questions about this policy can be raised as an issue on the GitHub repository.