Privacy Policy

Effective date: April 2026  ·  Version 1.0

Short version: Page2Podcast does not collect, store, or transmit any personal data to any server we operate. Your API keys never leave your browser. The extension reads page content only when you click Generate, sends it directly to Google Gemini and your chosen TTS provider, and saves nothing else.

1. What we collect

Page2Podcast collects no personal data. We do not run any backend servers. There is no analytics, no tracking, no crash reporting that sends data anywhere we control.

2. API keys you provide

To use Page2Podcast you optionally provide third-party API keys (Google Gemini, OpenAI, ElevenLabs). These keys are stored using chrome.storage.sync, which keeps them inside your Chrome profile and syncs them across your signed-in Chrome instances via Google's infrastructure — the same mechanism Chrome uses for your bookmarks and passwords.

3. Page content

When you click Generate, the extension reads text from the currently active tab and sends it to the Google Gemini API to generate a podcast script. This content is sent under your own Google API key and is subject to Google's privacy policy.

We do not store page content. We do not log it. We do not send it anywhere other than the provider you have configured.

4. Audio files

Generated audio is processed entirely in your browser (Chrome extension service worker) and downloaded directly to your device. No audio is uploaded to or stored on any server we operate.

5. Permissions used and why

6. Third-party services

When you use Page2Podcast, your data is processed by the following third parties under their own privacy policies:

We encourage you to review each provider's privacy policy to understand how they handle data sent through their APIs.

7. Children's privacy

Page2Podcast is not directed at children under 13 and we do not knowingly collect any information from children.

8. Changes to this policy

If this policy changes materially, we will update the effective date above and publish the new version. Continued use of the extension after an update constitutes acceptance of the revised policy.

9. Contact

Questions about this privacy policy? Open an issue on our GitHub repository or contact us via the Chrome Web Store listing.