Privacy and Your Data

Read Frog sits between you and whichever translation provider you choose, so the honest answer to "where does my reading go" depends on which provider that is. This page says what leaves your browser, and to whom.

What stays in your browser

Your settings live in the browser profile's extension storage and are never uploaded unless you ask for it:

• providers and API keys;
• target language, translation mode and range;
• custom prompts, custom CSS, glossaries, Custom AI Actions;
• the auto-translate lists and Site Control;
• the translation cache.

Signing in does not change this. Configuration only leaves the profile when you export it or start a Google Drive sync yourself.

What is sent to a translation provider

To translate a paragraph, that paragraph has to be sent somewhere. Which text is sent, and how much of it, depends on the prompt in use — Prompt Variables shows exactly what each request carries, including the page title, description and the first 2000 characters of page content when your prompt asks for them.

The provider is the one you configured, called with your key, under that provider's own privacy policy. Read Frog does not proxy those requests and does not see their contents — except when the provider is one of Read Frog's own built-in options, where the request goes to Read Frog's server so the allowance described in Account and Plans can be counted.

If you would rather nothing left your machine at all, run a local model through Ollama or LM Studio. Those requests go to localhost.

What Read Frog itself receives

Usage events. The extension reports that a feature ran, not what it ran on. Each event carries the feature name, the surface it was triggered from, the kind of provider (an LLM or a plain translation API, and which one), whether it succeeded, how long it took, and for a Custom AI Action its id and name. No page URL, no page content, no translated text, and no API key is included.

Your account, if you have one. A Notebase is stored on the server by design — that is what makes review and statistics work across devices. What lands there is whatever a Custom AI Action saved, which is usually a word, a definition and the sentence it came from.

Nothing, if you do not sign in. Translation works fully signed out, and nothing about your notes exists to store.

Local files and site access

The extension requests access to all sites because a translation extension that only worked on a list of sites would not be much use. You can narrow that yourself with Site Control, which stops Read Frog running on the sites you exclude.

Reading local files needs a separate permission you grant explicitly in the browser's extension settings; see Translate Local Web Pages.

Deleting things

• A notebase and its cards — delete them in the web app; see Managing Notes.
• Your whole account — account settings on the website, covered in Account and Plans. Not reversible.
• Local settings — Reset in Configuration, Sync & Backups, or uninstall the extension, which removes the profile's extension storage with it.
• Cached translations — Clear cache on the Page Translation and Video Subtitles screens.

The authoritative statements are the privacy policy and terms of service; this page describes how the software behaves.