Privacy Policy for Read Frog Browser Extensions
Last updated: March 16, 2026
This Privacy Policy applies to the Read Frog browser extensions distributed through the Chrome Web Store, Microsoft Edge Add-ons, and Firefox Add-ons. It explains what data the extensions store locally, what data may be sent to third parties when you use optional networked features, and what controls you have.
Read Frog is designed to keep as much data as possible in your browser. Most settings, caches, and feature state stay on your device unless you choose a feature that requires network access, such as cloud translation, text-to-speech, Google Drive sync, or optional product analytics.
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.
- If your version of Read Frog includes the optional "Help improve user experience" setting and analytics is enabled, the extension stores your analytics preference and a random installation identifier.
Data Sent to Third Parties When You Use Networked Features
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.
- 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.
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.
Optional Product Usage Analytics
Some versions of Read Frog include an optional setting labeled "Help improve user experience". When that setting is enabled, Read Frog sends product usage events to PostHog so we can measure feature reliability, latency, and usage patterns.
- These events may include a random installation identifier, extension version, browser name and version, event time, feature name, UI surface, success or failure result, and latency in milliseconds.
- In builds that include this setting, the current product behavior is enabled by default on Chrome and Edge and disabled by default on Firefox until you turn it on.
- Read Frog does not send page text, translated text, subtitle text, API keys, Google OAuth tokens, or full page URLs to PostHog as part of these usage events.
Uninstall Survey
When you uninstall the extension, Read Frog may open a Tally-hosted survey page. The uninstall URL includes the extension version, browser type, browser version, operating system, and UI language so we can understand uninstall feedback at a high level.
How We Use Data
- To operate the extension and remember your settings.
- 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 measure feature reliability and improve the product if optional analytics is enabled.
- To understand broad uninstall trends through the optional uninstall survey.
What We Do Not Sell
We do not sell your personal information. We do not use your extension content for advertising. We only send data to third parties when it is necessary to provide a feature you chose to use, such as your selected provider, Google Drive sync, PostHog analytics, or the uninstall survey.
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.
- Data stored in your Google Drive appDataFolder remains in your Google account until it is replaced or removed from that storage location.
- Optional 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.
- If your version of Read Frog includes the analytics setting, you can turn it off at any time in Settings > Config > About.
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 that you selected or enabled, that provider'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:
- By email: mengxi@readfrog.app
- By GitHub issue: https://github.com/mengxi-ream/read-frog/issues