Text2Voice privacy policy
Last updated September 2026
Text2Voice reads web pages aloud. Doing that means sending the text of the page
you asked it to read to this service, and on to a speech provider. This page sets
out exactly what is sent, what is kept, and for how long.
The extension does nothing until you ask it to. It reads a page
only when you press the toolbar button, choose an item from the right-click menu,
or use the keyboard shortcut. It does not run in the background, does not watch
what you browse, and has no access to a page until you invoke it on that page.
What is sent when you read a page
- The text you asked to have read. The extension extracts the
article from the page and sends it to this service, which passes it to
OpenAI's text-to-speech API to be spoken. Navigation, adverts, tables and
code are removed before sending.
- Which reader you chose, and the reading speed.
The page's address and title are not sent, and are not recorded
anywhere.
What is stored
- Your email address and account identifier, from signing in
with Google. Used to identify your account, apply your allowance and, if you
subscribe, connect you to your subscription.
- Generated audio, cached for up to 90 days and keyed by a
hash of the text and the voice. This is what stops the same passage being
purchased twice, and it means audio for text you have had read may be reused
to serve another reader who asks for the same passage in the same voice.
- Usage counters — words, characters, requests and estimated
cost per day — used to apply your daily allowance and to bill fairly.
- Product events: which reader was used, how many pieces a
page was divided into, how far through a reading you got, and where it
ended. These never include the page's address, title or text.
- Subscription state if you pay: a Stripe customer and
subscription identifier, the plan, and when access runs to.
What is not stored
- The addresses or titles of pages you read.
- Your browsing history, or any page you did not ask to have read.
- Card details. Payment is handled entirely by Stripe; this service never
sees a card number and never receives one.
- Your Google password. Sign-in is handled by Google through Firebase
Authentication; this service receives only a verified token.
Who else receives data
- OpenAI — the text to be spoken, in order to synthesize it,
and a short excerpt when a reader who comments is chosen, in order to write
the remark.
- Google Cloud — hosting, storage and Firebase
Authentication.
- Stripe — payment processing, for subscribers only.
Data is not sold, and is not shared with anyone else.
What is kept in your browser
- Your default reader and reading speed, synced by Chrome across your signed-in
browsers.
- Your session token, stored locally on the machine you signed in on and not
synced.
Retention and deletion
- Cached audio is deleted automatically after 90 days.
- Usage counters are kept per day and are not tied to anything but your
account identifier.
- To delete your account and everything held against it, email the address
below. Signing out from the extension's settings removes the session from
your machine but does not delete your account.
The website
This policy covers the extension. The website at
trytext2voice.com is a separate, static
page, and it uses Google Analytics to count visits and see which sections people
read. That is the only thing the website measures.
Analytics storage is off by default for visitors in the EEA, the UK and
Switzerland, so no cookies are set and no identifier is retained for them —
Google receives an unattributed page view and nothing more. The extension itself
sends nothing to Google Analytics, on any page you read, anywhere.
Children
This service is not directed at children under 13 and accounts are not knowingly
created for them.
Changes
If what is collected changes, this page changes with it, and the date above is
updated.