This page describes, in plain language, what Enkode's browser permissions are used for, what data leaves your device and why, and what Enkode never collects. It mirrors the answers on Enkode's Chrome Web Store privacy-practices listing. For the full policy, see the Privacy Policy.
Single purpose
Enkode translates portions of the pages you read to teach you a language.
Why Enkode requests each permission
| Permission | What it's used for |
|---|---|
| Access to the sites you visit (host access + content scripts) | Reads the text of a page so Enkode can replace a portion of it with translations. It runs only to translate what you read, and skips protected sites. |
| Storage | Saves your settings, your word bank, and translation caches so the extension remembers them between sessions. |
| Tabs | Identifies the active tab so Enkode can enkode it on request and check its address against your protected-site list. |
| Side panel | Opens the AI tutor in Chrome's side panel next to the page. |
| Identity | Signs you in with Google so your word bank and progress belong to your account. |
What data leaves your device, and why
| Data | Where it goes | Why |
|---|---|---|
| A portion of the sentences on pages you enkode, plus text you select | Our Supabase function → OpenAI | To translate it. Processed in transit and not stored on our servers — only per-request token counts are kept. |
| Words you save, with their source sentence, page URL, and page title | Supabase (your account) | To build your word bank and quizzes and sync them across your browsers. |
| Quiz answers | Supabase (your account) | To schedule reviews and track your progress. |
| Daily reading-word counts | Supabase (your account) | To power the plant-growth progress widget. |
| Your email and Google account ID | Google → Supabase | To create and identify your account when you sign in. |
| Per-request token usage counts | Supabase (your account) | For cost accounting and usage limits. |
What Enkode never collects
- Your browsing history.
- Page content from protected sites — a built-in default list of sensitive sites (email, cloud documents, and banking) plus any sites you add. Enkode does not read or translate those pages.
- Passwords, form entries, or payment card details. Enkode reads page text only; it never reads the contents of input fields.
Compliance
Enkode's use and transfer of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. We do not sell your data, and we do not use it for any purpose unrelated to teaching you a language.