Privacy Policy

Last updated: July 2026

WebVoice does not sell personal data. This policy explains what the extension processes locally, what is sent when you choose a cloud feature, and how purchase verification works.

1. Page reading and cleaning

When you use local reading, page text, selected text, cleaning results, reading blocks, playback position, and highlights are processed in the browser or by the operating system voice engine. WebVoice does not upload that text to its own servers for local reading.

2. Local books

EPUB, TXT, HTML, and Markdown files are parsed in the browser. The temporary import slot and the current book document are used only for the active book session. WebVoice does not create a permanent cloud library or save the full book as long-term account data. Your original file remains on your device.

3. Cloud TTS and translation

If you enable a configured cloud TTS or translation provider, the text needed for that request is sent directly to the provider you selected, such as OpenAI, ElevenLabs, Microsoft Azure, Google, Baidu, Tencent, Alibaba, DeepL, or a custom endpoint. The provider's own terms, privacy policy, regional processing, retention, and charges apply. Do not send content to a provider unless you are comfortable with that provider processing it.

4. Purchase and license verification

Checkout is hosted by Stripe. The extension sends the normalized checkout email, a device identifier, and the extension version to the WebVoice license Worker at webvoice-license-api.pdx010203.workers.dev. The Worker uses a Stripe Restricted Key kept outside the extension to check the relevant subscription or lifetime purchase.

For license verification, the Worker stores a license cache in Cloudflare D1. This can include the normalized email, Stripe customer and purchase or subscription identifiers, plan type, status, trial or billing period dates, cancellation state, verification timestamps, and a salted hash of the device identifier. It does not store card numbers or the page and book text. The device hash is used to enforce the current five-device activation limit.

5. Extension storage

The extension stores settings, voice preferences, language choices, checkout email, license status, usage state, device identifier, and optional provider configuration in Chrome extension storage. API keys or tokens that you enter are kept locally on your device and used to call the provider you selected. Do not share your extension profile or API keys.

6. Payments and third parties

Stripe processes payments and may process billing information under its own privacy policy. Cloudflare provides the Worker and D1 infrastructure used for license verification. WebVoice does not receive or store your full payment card details.

7. Retention and choices

License records are retained as needed to verify purchases, enforce device activation, prevent abuse, and provide customer support. Page text and full imported books are not retained by the license service. You can stop using cloud features, remove provider keys from Settings, clear extension storage, or uninstall WebVoice. Clearing local storage removes the locally saved checkout email and license cache; a future verification may request the email again.

8. Contact

For privacy questions or a request about license verification data, email pdx010203@gmail.com. Stripe and Cloudflare may also receive requests that relate to data they process directly.