Help is a
click away.
Everything you need to get the most out of LingoFlip — and exactly what happens (and doesn't) with your data.
🔒 Privacy, in one sentence.
LingoFlip collects nothing — no analytics, no accounts, no tracking, no history of what you translate. The only data that ever leaves your browser is the exact text you select, and only after you click “Übersetzen”: it is sent over HTTPS to Google's public translate endpoint (translate.googleapis.com) to fetch your translation. Nothing else is transmitted.
Full privacy policy: Privacy.
Questions.
How do I translate something?
Select text on any http(s) page → a small “Übersetzen” action appears next to your selection → click it. The text is replaced inline. Click it again to flip back to the original; one more click re-shows the cached translation — without a second request.
What gets sent, and where?
Only the selected text and your target language — and only when you click. The request goes to translate.googleapis.com; Google can process that text under its own rules. LingoFlip runs no translation server of its own.
What is stored locally?
Your target language and setup state in chrome.storage.sync, plus a local usage counter. Selected texts are never stored as history or profile.
Can I change the target language?
Yes. Open the compact toolbar popup and pick any language under Zielsprache — German is the default. The change applies immediately and syncs across your devices.
Why was my selection rejected?
Empty or editable selections, internal extension pages, selections spanning multiple block elements, or texts over 5,000 characters are skipped — on purpose, to stay minimal and predictable.
Why does it ask for permissions?
storage for your settings, and access to translate.googleapis.com for the translation call. Content scripts run only on normal http/https pages — nothing else.
Something isn't working.
Reload the page and try again — the public translation endpoint can be rate-limited or briefly unavailable. If it persists, email us and we'll help.