← Back to QuickLingo

Privacy Policy for QuickLingo: Translator & Explainer

Last updated: September 22, 2026

This Privacy Policy explains what information the QuickLingo Chrome extension ("QuickLingo," "the Extension," "we," "us") collects, how it is used, and the choices you have. QuickLingo is built to work with as little data as possible — there are no user accounts, and text you translate is never stored on our own servers.

1. What QuickLingo Does

QuickLingo lets you highlight text on any webpage and instantly translate it or get a plain-language explanation. Results can appear either in a floating widget on the page, or — in page mode — as small cards placed next to the text you selected.

2. Information We Collect

a) Text you choose to translate or explain. When you use the Translate feature, the selected or typed text is sent directly to Google's public translation service to produce the translation. If that service is unavailable or temporarily rate-limited, the same text is sent to MyMemory (translated.net) instead, as a fallback. When you use the Explain feature, the text is sent to our backend server (a Cloudflare Worker), which forwards it to a third-party AI provider (Groq) to generate the explanation. We do not store the content of your translations or explanations on our own servers — it passes through only to generate a response.

b) Auto-explain (optional, off by default). Page mode includes an "Auto-explain" setting. While it is switched on, each new card's text is sent for an explanation automatically, without a separate click. It sends the same kind of text to the same provider described above — only the timing differs — and you can switch it off at any time from the page-mode bar.

c) An anonymous installation ID. When you install QuickLingo, the Extension generates a random identifier (not linked to your name, email, or any personal account) and stores it on your device. This ID is sent to our backend solely to enforce free-tier usage limits and check Pro license status. It cannot identify you personally.

d) Information stored locally on your device (via chrome.storage.local, never transmitted to us except where noted):

You can clear this data at any time by uninstalling the Extension or clearing your browser's extension storage.

e) Payment information (Pro subscribers only). Payment is handled entirely by LemonSqueezy, our third-party payment processor. QuickLingo never receives or stores your payment card details. See LemonSqueezy's Privacy Policy for details.

3. What We Do NOT Collect

4. Third-Party Services We Use

ServicePurposeWhat's sent
Google TranslateTranslationSelected/typed text, target language
MyMemory (translated.net)Translation — fallback only, when Google's service is unavailableSelected/typed text, source and target language
GroqExplain (Free and Pro)Selected/typed text, target language
LemonSqueezyPayment & license verificationBilling details, license key
CloudflareBackend hostingAnonymous install ID, Explain text, usage counters

5. Permissions QuickLingo Requests, and Why

6. Children's Privacy

QuickLingo is not directed at children under 13, and we do not knowingly collect personal information from children.

7. Data Retention

8. Your Choices

You can clear your local history and saved words at any time from within the Extension, or uninstall it entirely to remove all locally stored data. Since QuickLingo does not maintain user accounts, most data requests can be fulfilled by clearing local storage. For questions about data sent to our backend, contact us below.

9. Changes to This Policy

We may update this Privacy Policy from time to time — for example, if we add a new AI provider for the Explain feature. Changes will be posted on this page with an updated "Last updated" date.

10. Contact Us

If you have questions about this Privacy Policy, please contact us at: quicklingo.support@gmail.com

This document is a general privacy policy for a small Chrome extension and is not a substitute for legal advice. If QuickLingo grows significantly or targets users in regions with specific privacy laws (e.g., GDPR, CCPA), consider having this policy reviewed by a legal professional.