سياسة الخصوصية

يحترم Parallel Translate خصوصيتك ويحصر تدفق البيانات في ما تحتاجه كل ميزة.

• No account is required; we do not track browsing history or build user profiles.
• Settings, caches, API keys, and vocabulary state are stored in your browser.
• Page or selected text is sent only when translation, lookup, vocabulary explanation, or pronunciation needs it.

1. What we do NOT collect

The extension requires no registration or login. We do not collect your name, email, or account, we do not build user profiles, and we do not track or upload your browsing history. There is no analytics backend collecting user data.

2. How data is processed

To provide translation, lookup, vocabulary learning, and pronunciation, the extension processes the following data only when you actively trigger it:

• Page / selected text: when you enable page translation, look up a selection, request vocabulary explanations, or play pronunciation, the relevant text fragment is sent to the service needed to return the result.
• Local settings, cache, and vocabulary state: language preferences, translation settings, site preferences, vocabulary state, translation cache, explanation cache, and speech cache are stored in your browser (chrome.storage and IndexedDB).
• API keys: if you configure your own AI service key, it is stored locally and used only to call the service you selected.

3. Third-party services

When you use the relevant feature, text is sent to one of the following services to return a result. Please refer to their respective privacy policies:

• Translation engines: Google Translate, Microsoft Translator, or an AI service you configure, such as OpenAI, Anthropic, DeepSeek, or a custom OpenAI-compatible endpoint.
• Dictionary and vocabulary proxy: api.paralleltranslate.app, a self-hosted Cloudflare Worker used for definitions, examples, vocabulary lists, and vocabulary enrichment. Requests contain only the word or list identifier needed for the feature.
• Speech: Microsoft Edge TTS receives the text to synthesize and returns audio; browser / operating-system speech services process text according to the platform capability.

4. Permissions

The browser permissions the extension requests, and why:

• host_permissions (all sites): to render parallel text, vocabulary highlights, and the selection panel on the pages you choose to read. This is required for the core reading feature and is not used to track browsing history or build user profiles.
• storage: to keep your settings, vocabulary list, and cache locally.
• offscreen: to play pronunciation audio in the background.

5. Retention & deletion

Local settings, cache, and vocabulary state are stored in your browser. You can clear the cache and vocabulary list anytime in the extension settings, or uninstall the extension to remove local data. Feedback messages and launch notification waitlist emails are stored separately for their stated purposes and anti-abuse protection.

6. Children's privacy

The extension targets learners with a language foundation, is not directed at children under 13, and does not knowingly collect personal information from children.

7. Policy updates

If this policy changes, we will update the "Last updated" date at the top of this page. If we add account, subscription, or payment features in the future, we will update this policy before those features launch and explain the additional data processing in the product.

8. Contact

For questions about this privacy policy, contact [email protected]. For product feedback, email [email protected].

9. Feedback form

When you actively submit content through the feedback form on this site, we store: the message text and optional email you provide; de-identified request metadata used for anti-spam (IP truncated to the subnet level, User-Agent reduced to browser + major version); the page URL and UI language at submission time. This data is used only to read and respond to your feedback and to prevent abuse. It is never used to build user profiles or shared with third parties. We plan to purge old feedback records after 12 months.

10. Launch notification waitlist

When you join the launch notification waitlist, we store your email address, confirmation status, UI language, submission page, de-identified anti-abuse metadata, and consent text version. We send a confirmation email first; only confirmed addresses receive one launch notification email when the extension is available. We do not use the waitlist for newsletters, marketing sequences, or profiling. The future launch notification email will include an unsubscribe or cancellation link.