Privacy Policy for Read Frog

Last updated: October 19, 2026

This Privacy Policy applies to Read Frog, the Read Frog browser extensions distributed through browser extension stores, the website at https://www.readfrog.app, user accounts, Notebase, MCP connections to AI assistants, and related online language-learning features.

Read Frog is designed to keep as much data as practical in your browser. Some features require network access, such as cloud translation, Read Frog's Built-in AI, text-to-speech, account login, Notebase sync, Google Drive sync, website analytics, extension product analytics, and payment processing for paid subscriptions. Extension product analytics is on by default in the Chrome and Edge versions and off by default in the Firefox version, and you can turn it on or off at any time.

Data Stored on Your Device

Read Frog stores data in your browser storage so the extension can work.

  • Your settings and feature configuration, including language choices, provider settings, custom actions, site control lists, UI preferences, and other extension options.
  • Provider credentials and connection settings that you enter yourself, such as API keys, model selections, and custom base URLs.
  • Local working data used to improve performance and recover settings, such as translation cache entries, article summary cache entries, AI subtitle segmentation cache entries, backup data, and request statistics.
  • If you enable Google Drive sync, a Google OAuth access token is stored locally so the extension can access your Google Drive appDataFolder, and the last synced Google account email is stored locally to keep sync state consistent.
  • Your "Help improve user experience" choice and, once extension product analytics has been on, the random installation identifier it uses.

Account and Notebase Data

If you create or sign in to a Read Frog account, we may process account information such as your name, email address, authentication provider, account identifiers, session data, preferences, and feature access status.

Notebase stores structured learning content that you create or save, such as vocabulary, definitions, example sentences, translations, reading notes, custom fields, card templates, generated flashcards, review history, and scheduling metadata.

When you save to Notebase from the browser extension, the note holds the fields of the custom AI action you saved from, typically the text you selected and what the AI wrote about it. Read Frog does not add the address of the page you were reading to the note.

When you use features that run on Read Frog's servers, such as Built-in AI, saving notes, and reviewing cards, our servers record usage events about them in PostHog, such as the feature, the result, the model tier, and note or notebase identifiers. These events are linked to your account ID and, for some events, your email address. For Built-in AI used without signing in, usage is counted under a key derived from your IP address that changes every day. These events do not include the text you send or the content of your notes.

When you save notes from the extension while "Help improve user experience" is on, the extension also sends a request header that tells our servers whether the save came from a custom AI action or a note suggestion and whether it was part of the onboarding guide. When that setting is off, the extension does not send this header.

Data Sent to Third Parties When You Use Networked Features

MCP Connections to AI Assistants

When you connect Read Frog to an AI assistant such as ChatGPT or Claude through Model Context Protocol (MCP), that service can request the Read Frog data covered by the permissions you approve. Depending on those permissions, this includes account details, notebases and fields, note content, card templates, rendered cards, study settings, and review history. Write permissions also allow the connected service to create, modify, or delete the corresponding data and perform study actions on your behalf.

Read Frog receives the tool arguments needed to carry out these requests and returns the authorized results to the connected service. That service handles the information it receives under its own terms and privacy policy. Read Frog stores authorization records and credentials needed to maintain the connection. MCP execution logs record operational information such as the tool, client identifier, outcome, and duration; they do not record tool arguments, note bodies, account profiles, or credentials.

You can withdraw a connected service's authorization in Read Frog's MCP settings. This removes its stored consent and revokes its connection credentials. Disconnecting does not delete information already received by that service; use its controls or contact it to request deletion. Learning content saved through MCP is retained as account and Notebase data, as described below.

Translation, AI, and Text-to-Speech Providers

When you use translation, AI, subtitle, custom action, or text-to-speech features that rely on a remote service, Read Frog sends the data needed to complete your request to the provider you selected.

  • This may include selected text, typed text submitted for input translation, page text chosen for translation, subtitle text, prompts, language settings, voice settings, and provider-specific request parameters.
  • If you enable AI content-aware features, Read Frog may also send the current page title and extracted article text so your selected model can generate a more context-aware translation.
  • Custom AI actions and note suggestions can also send the current page title, the full address of the page, and extracted page text when the action's prompt includes them, as some built-in actions do.
  • Depending on the provider you choose, this data may be sent to services such as Google Translate, Microsoft Translator, Microsoft Edge TTS, OpenAI-compatible providers, or other third-party or self-hosted endpoints you configure.
  • If you choose Read Frog's Built-in AI, for example for translation, language detection, custom AI actions, note suggestions, or video subtitles, the request content described above is sent to Read Frog's servers, which forward it to our AI service provider, Microsoft Azure OpenAI, to generate the result. Our servers keep a record of how much you used so it can be counted against your plan's allowance, not the text of the request.
  • If you use AI subtitles, the extension sends the video's address and length to Read Frog's servers. Our servers retrieve the video's audio, transcribe it with Microsoft Azure AI Speech, and store the transcript with the video's address and title so the same video does not need to be transcribed again.

Google Drive Sync

If you enable Google Drive sync, Read Frog uses Google OAuth and Google Drive APIs to read and write a configuration file in your Google Drive appDataFolder.

  • The synced file may include your full extension configuration, including provider settings and API keys, because Google Drive sync uploads your configuration as stored by the extension.
  • Read Frog also requests your Google account email address so it can determine which Google account last synced the local configuration.

Read Frog's use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Payment Processors

Paid subscriptions may be processed by third-party payment processors such as Stripe. We do not store complete credit card numbers on Read Frog servers. Payment processors may collect payment method details, billing contact information, transaction metadata, tax information, and fraud-prevention signals according to their own policies.

Website Analytics

Read Frog uses PostHog on the website to understand traffic sources, page views, and conversion funnels such as install button clicks and account sign-up steps.

  • Website analytics events may include page paths or URLs, referrers, UTM parameters, browser and device metadata, event time, basic page engagement signals, button surface, selected browser store, authentication funnel step, and account identifiers after you sign in or verify your email.
  • After you sign in or verify your email, Read Frog may associate website analytics with your account ID and basic account properties such as email address and display name so sign-up and product usage events can be measured consistently.
  • Website analytics does not include passwords, payment card details, extension page content, translated text, subtitle text, API keys, Google OAuth tokens, or the values typed into sign-up or login forms as event properties.

Extension Product Analytics

The Read Frog browser extension sends product usage events to PostHog so we can measure feature reliability, latency, and usage patterns. This is controlled by the "Help improve user experience" switch in the extension, under Options > Preferences > User experience. It is on by default in the Chrome and Edge versions and off by default in the Firefox version, and you can turn it on or off at any time.

  • Each event records that a feature ran, not the content it ran on: the feature (such as page translation, selection translation, input translation, video subtitles, text-to-speech, custom AI actions, note suggestions, saving to Notebase, or the glossary), where you started it (such as the popup, the selection toolbar, the context menu, or a keyboard shortcut), whether it succeeded, a general reason when it failed (such as a network error, a missing API key, or a reached quota), how long it took in milliseconds, and the type of translation or AI provider (such as Google Translate, an OpenAI-compatible provider, or Read Frog's Built-in AI).
  • Depending on the feature, an event can also include the target language, the source language, the page translation mode, the number of characters translated, the ID and name of a custom AI action, and the number of notes saved and how the save was completed.
  • Events include the hostname of the website you were on when you used the feature, such as en.wikipedia.org. Only the hostname is sent, not the rest of the page address, the page title, or page content.
  • Events also include a random installation identifier created by the extension, the extension version, the event time, and basic technical details added by the analytics library: browser name and version, operating system, browser language, time zone, and device type. The installation identifier is not linked to your Read Frog account.
  • The extension starts PostHog with automatic event capture, page view and page leave tracking, session recording, referrer and campaign tracking, feature flags, and person profiles turned off, and keeps PostHog's state in memory instead of in cookies or browser storage. Before sending an event, it removes page addresses, page titles, screen sizes, and any property that could hold text, prompts, model names, or credentials. Our PostHog project for the extension is set to discard IP addresses.
  • Read Frog does not send page text, selected text, translated text, subtitle text, prompts, AI responses, note content, API keys, Google OAuth tokens, page titles, or full page URLs to PostHog as part of these events.
  • When you turn the switch off, the extension stops sending these events and stops sending the note-save context header described under Account and Notebase Data.

Uninstall Survey

When you uninstall the extension, your browser opens a survey page hosted by Tally. The page address includes the extension version, the browser the extension was built for (Chrome, Edge, or Firefox), the browser version, the operating system, and the interface language, so Tally receives them when the page opens, even if you do not answer. This happens whether or not "Help improve user experience" is on, and helps us understand uninstall feedback at a high level.

How We Use Data

  • To operate the extension, website, accounts, and Notebase.
  • To remember your settings and sync your learning content.
  • To perform the translation, AI, subtitle, and text-to-speech tasks you request.
  • To sync your configuration to your Google Drive account if you enable that feature.
  • To process subscription payments and manage paid feature access.
  • To measure website traffic sources and conversion funnels.
  • To measure feature reliability and improve the product through extension product analytics while it is on, and through usage events recorded by our servers.
  • To understand broad uninstall trends through the uninstall survey.

What We Do Not Sell

We do not sell your personal information. We do not use your extension, Notebase, or account content for advertising. We only send data to third parties when it is necessary to provide a feature you chose to use, such as a connected AI assistant, your selected provider, Microsoft Azure for Built-in AI and AI subtitles, Google Drive sync, or payment processing, or for the PostHog analytics and the uninstall survey described above.

Retention

  • Data stored locally by the extension remains on your device until you change it, clear it, reset the extension, clear caches or backups, or uninstall the extension.
  • Account and Notebase data is kept as long as needed to provide the service, comply with legal obligations, resolve disputes, prevent abuse, and maintain backups.
  • Data stored in your Google Drive appDataFolder remains in your Google account until it is replaced or removed from that storage location.
  • Analytics data is retained only as long as reasonably needed to operate, debug, and improve Read Frog, subject to the retention settings of our analytics processor.

Your Choices

  • You choose which translation, AI, and text-to-speech providers to use. If you do not use a remote provider, Read Frog does not send request content to that provider.
  • You can export configuration with or without API keys, reset settings, clear caches, remove backups, or uninstall the extension.
  • You can disconnect Google Drive sync by logging out of Google Drive inside the extension.
  • You can turn extension product analytics on or off at any time with the "Help improve user experience" switch in the extension, under Options > Preferences > User experience.
  • You can contact us about account, Notebase, billing, or privacy questions at [email protected].

Security

Read Frog uses the endpoints and providers you configure. Many built-in services use HTTPS, but if you connect Read Frog to a custom or self-hosted endpoint, you are responsible for the security and privacy practices of that endpoint.

Third-Party Services

When Read Frog sends data to a third-party provider, payment processor, analytics service, or survey service that you selected or enabled, that third party's own privacy policy also applies. Please review the privacy policies of the providers and services you choose to use.

Changes to This Privacy Policy

We may update this Privacy Policy from time to time. When we do, we will post the updated version on this page and update the date above.

Contact Us

If you have questions about this Privacy Policy, you can contact us: