Privacy Policy

Summary

Franker is designed to translate selected webpage text through Chrome’s built-in on-device Translator and Language Detector APIs. Bender Bureau does not receive the selected text, translations, browsing history, or page contents. Franker has no accounts, advertising, analytics, or tracking.

Information processed and stored

Selected text and detected language information are processed locally by Chrome so the requested translation can be inserted into the current page. Franker stores only the preferences needed to operate the Extension.

• Source and target language preferences.
• Translation appearance, placement, and keyboard shortcut settings.
• Temporary translation markers on the current page so inserted translations can be updated or removed.

Chrome services, storage, and permissions

Chrome may download language support the first time a language pair is used. These downloads and the translation process are provided by Chrome and are subject to Google’s terms and privacy practices. Extension preferences may be stored with chrome.storage.sync and therefore synchronized by Chrome when browser sync is enabled.

Franker requests only the browser permissions needed to add its commands, read the user’s current selection after an explicit action, insert or remove translations on that page, and save preferences. It does not use those permissions to build a browsing profile.

Your choices and retention

You can change or reset preferences from the Options page, remove inserted translations at any time, disable Chrome Sync, or uninstall Franker. Page translations are not retained by Franker after the page is closed or reloaded. Uninstalling removes locally stored extension data; Chrome may separately manage synchronized settings according to your Chrome account controls.

Security, children, and changes

Franker does not intentionally collect personal information and is not directed to children under 13. No software can guarantee absolute security. We may update this Policy when the Extension, Chrome APIs, or legal requirements change; the effective date above will be revised when changes are material.