Readixa Extension Privacy Policy

Last updated: September 19, 2026

What the extension does

Readixa translates the subtitles of videos you watch (Netflix, YouTube, Udemy, Coursera and similar sites) into Persian and, on request, translates and analyzes web pages and social media posts. That is its single purpose.

Data we process

• Subtitle, page or post text, only when you have enabled translation or click a translate button. The text is sent to an AI service to be translated.
• Readixa cloud service: if you sign in with a Readixa account, text is routed through readixa.com to AI models. We do not store request text; we keep usage counters only (request count, token count, request type and date) to meter your plan.
• Your own API key: if you enter a key for OpenAI, Anthropic, Gemini or a compatible service, text goes directly from your browser to that service and the key is stored only in your browser's local storage. We never see it.
• Account and sign-in: signing in requires only your email address. A one-time 6-digit code, valid for 10 minutes, is emailed to you; the code is stored hashed on the server, never in plain text. After a successful sign-in an access token is stored in your browser so you stay signed in; you can revoke it from "Sign out" in the extension or from your account page on the site; successful sign-out revokes the token on our server before removing it from your browser. If revocation cannot be confirmed, you remain signed in and an error asks you to retry. We retain your email address, sign-in timestamps and usage counters. Name is optional. Sign-in emails are delivered via Resend. Payments are handled by the payment provider; we never see card numbers.
• Settings and local cache: settings, cached translations, glossaries and your vocabulary notebook are stored in your browser and can be cleared from the settings page at any time.
• Chrome account sync (optional, off by default): if you enable it, your appearance and behaviour preferences are stored in your Google account's sync storage so they follow you to your other browsers. API keys, the sign-in token and your Readixa account details are never synced. Turning the option off deletes the synced copy. This data is held by Google and never reaches our servers.
• Backup files: a file you create yourself with the "Save backup file" button stays on your device and, by default, contains no API keys and no sign-in token. Only if you enable "Include API keys" and accept the warning are those written into the file in plain text — keep such a file somewhere safe.

Data we do not collect

The extension does not collect browsing history, visited pages, keystrokes or site content except at the moment of a translation you requested. There are no advertising trackers or third-party analytics, and data is never sold.

Browser permissions and why

• storage / unlimitedStorage: keep settings and the translation cache on your device.
• downloads: save a subtitle file (SRT) or a share/backup file when you click download.
• scripting and optional access to all sites: only if you turn on "All sites" so subtitles work on other video sites. Off by default.
• Access to supported sites (Netflix, YouTube, …): read the original subtitles and render Persian subtitles over the video.
• Access to AI services: send text for translation.

Page URLs

The address of the page you are on is sent in exactly one case: when you click "Summary". The URL travels with the page text so the model can resolve relative links and cite the source. Page translation, ask-a-question, subtitles and post analysis do not send it. We do not collect, store or analyse your browsing history, and we keep no record of the pages you visit.

Server logs

If you use the cloud service, our server keeps technical logs for security and debugging, as any internet service does: timestamp, request path (for example "translate" or "summarize"), response code, IP address and browser type. The content of your requests is never written to these logs. Usage counters (request count, token count, request type and date) are retained to meter your plan. Technical logs are rotated: once they reach a fixed size limit, the oldest entries are deleted automatically. In practice only the most recent few days remain, and we do not archive technical logs long-term.

Limited Use

Readixa's use of information received from Google APIs, and all user data it handles, adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Specifically: your data is used only to provide the feature you asked for; it is never sold; it is never used for advertising, retargeting or building advertising profiles; it is never used to determine creditworthiness or for lending purposes; and no human reads it except with your explicit permission, to resolve a security issue, or where we are required to by law.

Third parties

Depending on your choice, text is sent to OpenAI, Anthropic, Google Gemini or another compatible service, whose own privacy policy applies. Sign-in emails are delivered via Resend.

Deleting data

Uninstalling the extension removes all local data. To delete your cloud account and usage data, request it from your account page or email us.

Contact

Questions: [email protected]