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 article-like text on pages where Enkode runs so it can replace or mark a portion of that text with translations. Auto-Enkode skips protected sites unless you add an exception. |
| Storage | Saves settings, protected-site rules, auth session, local word-bank mirror, translation cache, tutor content, quiz progress, reading stats, sync outboxes, and short local activity logs so the extension works between sessions and can sync when signed in. |
| Tabs | Identifies the active tab so Enkode can run on request, open the tutor next to the page, and check the active tab's 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, topics, quiz progress, reading progress, and usage records belong to your account. |
What data leaves your device, and why
| Data | Where it goes | Why |
|---|---|---|
| A portion of the sentences on pages where Enkode runs, plus text you select | Our Supabase function → OpenAI | To translate text, explain selected words, lemmatize words, classify topics, generate quiz options, and create tutor lessons. Enkode does not write live request text to its Supabase database unless you save the resulting word or learning item. Token counts are stored for usage accounting, quotas, and rate limits. |
| Words and phrases you save, with their meanings, translations, source sentence, translated sentence, page URL, page title, topic, and review state | Supabase (your account) | To build your word bank and quizzes and sync them across your browsers. |
| Word-bank topic settings | Supabase (your account) | To keep your custom topic list and saved-word topic assignments in sync. |
| Quiz answers | Supabase (your account) | To schedule reviews, score progress, and maintain an answer ledger. Synced rows include correctness, grading reason, quiz style, entry ID, lemma/topic snapshot, and answer time; they do not store your typed guess as a separate field. |
| Daily reading-word counts | Supabase (your account) | To power reading progress and the plant-growth widget. Synced rows include language pair, local date, credited word count, and flush time. |
| Your email, Google account ID, and basic Google profile information | Google → Supabase | To create and identify your account when you sign in. |
| Per-request token usage counts, model name, timestamp, and user ID when available | Supabase (your account) | For cost accounting, daily quotas, rate limits, and operational monitoring. |
| Local browser data | Your browser's extension storage | To make the extension fast and resilient. This includes settings, protected-site rules, translation cache, tutor content, local word-bank mirror, quiz progress, reading stats, sync outboxes, auth session, and short activity logs. Some of this local data may include original sentences, translations, selected words, source URLs, and page titles. |
What Enkode never collects
- Your full browsing history or a list of every page you visit. Source URLs and titles are stored only when tied to saved-word context or local reading-session records.
- Page content from sites where Auto-Enkode is protected, unless you add an exception or manually run Enkode there. The default protected list includes sensitive sites such as email, cloud documents, banking, and payment sites, and you can add your own.
- 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.