Privacy policy

Translations of this policy are provided for convenience; the English text is the version that governs.

Privacy Policy — Read For Me: Text to Speech

Last updated: 2026-10-17

Read For Me reads web page paragraphs aloud. This policy explains exactly what data the extension handles, where it goes, and how to remove it.

Summary

  • Signed out, nothing leaves your device except the paragraph text you ask to have read, sent directly to the text-to-speech provider *you* configured.
  • Signing in is optional. It is only needed for the premium plan, and you can sign in with Google or with an email address and password.
  • Google access stays inside the features that need it. Sign-in reads your Google account identity once; Drive access is requested only when you link it, and covers only the files the extension creates itself. The *Google user data* section below is the full account of what that means.
  • Reporting a problem is opt-in and manual. Nothing about a page is uploaded unless you open Report an issue, read what it will send, and press Send report.
  • We do not use analytics, telemetry, advertising, or tracking of any kind.
  • We do not sell your data, and we do not share it except with the providers needed to deliver a feature you explicitly used.

What data is collected

Data that never leaves your device

DataWhyWhere it is stored
Your API keys for text-to-speech providersTo call the provider you chosechrome.storage.local, readable only by the extension's own pages and background worker. Never injected into web pages and never synced.
Your preferences (provider, voice, speed, disabled sites, tone and language settings, cloud-sync target)To remember how you like the extension to behavechrome.storage.local
Generated audio and its transcriptTo replay a paragraph instantly and to build ZIP and video exportsThe website's own IndexedDB, in that site's origin

Data sent off your device

DataSent toWhyWhen
Paragraph textThe text-to-speech provider you configured (for example OpenAI, Microsoft Azure, ElevenLabs, Google Cloud, or a custom endpoint)To synthesize the audio you asked forOnly when you press play, or when you start a batch generation
Paragraph textThe Read For Me APITo synthesize audio by spending your credits, or to detect the paragraph's tone or languageOnly when you choose to generate speech with credits, and only when premium tone detection or language detection is switched on
Email address and, for Google sign-in, your name, profile picture URL and Google account IDThe Read For Me APITo create and identify your accountOnly when you sign in
A one-way hash of your password, if you choose to set oneThe Read For Me APITo verify you at sign-in. Your password itself is never stored or transmitted after the initial request, and it is hashed with a per-password salt (PBKDF2-HMAC-SHA256).Only when you set or change a password
Your email address and a six-digit confirmation or reset code, if you set a passwordResend (our email delivery provider)To deliver the code that confirms your address or resets your passwordOnly when you sign up, or ask for a password reset
Subscription status and credit balanceThe Read For Me APITo know which features you can use and how many credits remainWhile signed in
Generated audio, its transcript, page title, page URL, site origin, and the paragraph's position in the articleThe Read For Me API, or your own Google DriveTo sync your library so it is available on your other devicesOnly once you switch on Allow sync to cloud in Settings and then press Sync now, or switch on upload-as-you-go
An issue report: your description, the page URL, title, origin, language and metadata, the page's visible text and HTML source, its resource list, and up to three audio files found on the pageThe Read For Me APITo reproduce and fix the problem you reported. The page snapshot and audio are what make a page-specific bug diagnosable without a follow-up round trip.Only when you open Report an issue, enter a description, and press Send report. Nothing is collected before that.

We do not collect your browsing history, we do not read pages you have not asked the extension to act on, and we do not record which pages you visit.

How data is stored

  • On your device: settings and API keys in chrome.storage.local; generated audio in each website's own IndexedDB. Clearing a site's data in Chrome, pressing Clear cache for this site, or uninstalling the extension removes this.
  • On our servers (when you sign in): your account record, subscription status, an append-only credit ledger, and — if you enable cloud sync — the audio you uploaded with its transcript and page metadata, held in Cloudflare R2 storage and a Cloudflare D1 database.
  • In your Google Drive (premium, optional): if you choose Google Drive as your sync target, audio is written directly from your browser to your own Drive. It does not pass through our servers. Unlinking Google Drive in Settings revokes the extension's Google access — the files already in your Drive are left untouched and remain yours.

How data is used

Each item is used only for the feature it belongs to:

  • Paragraph text — to produce the audio you requested, and (on premium, if you enable it) to choose a speaking tone or a speaking voice appropriate to the passage.
  • Account details — to sign you in and to attach your plan and credits to the right account. If you set a password, only a salted hash of it is stored, and the password itself is never retained. One-time confirmation and reset codes are stored only as a salted hash and expire after ten minutes.
  • Failed-attempt counters — to slow down password guessing against your account, we count failed sign-in, code and code-request attempts per account and per source IP address. These counters are short-lived and hold no other information.
  • Credit ledger and usage records — to meter premium usage accurately and to show you your remaining balance.
  • Synced audio and transcripts — to restore your library on another device.
  • Issue reports — to reproduce and fix the problem you described. A report is kept for as long as it is useful for that, and it is stored as one database row plus the page snapshot and page audio it carried. Reports are accepted without an account (a report is often about the page *or* the sign-in flow misbehaving), and filing them is rate limited per account or per IP address so the storage cannot be used as free file hosting. You can file a report from a page where you have disabled reading, because "the extension does nothing here" is itself a problem worth reporting.

Tone and language detection store no text

When tone or language detection is enabled, the API stores only a SHA-256 hash of the paragraph and what it classified, so the same paragraph is never classified twice. The paragraph text itself is not retained for either purpose.

Third-party services

ServicePurposeTheir policy
Google Sign-InOptional account sign-in with Googlehttps://policies.google.com/privacy
ResendDelivering the confirmation and password-reset codes for email + password sign-inhttps://resend.com/legal/privacy-policy
Google Drive (only if you choose it as your sync target)Storing your audio in your own Drivehttps://policies.google.com/privacy
Cloudflare (Workers, Workers AI, D1, R2)Hosting the premium API, running the tone and language classification models when those premium features are switched on, and storing synced audiohttps://www.cloudflare.com/privacypolicy/
StripeProcessing premium subscription payments. We never see or store your card details.https://stripe.com/privacy
Your chosen text-to-speech providerConverting text into speechDepends on the provider you configure

Google user data

Two optional features touch Google user data: signing in with Google, and using your own Google Drive as the cloud-sync target. Neither is needed to read a page aloud.

What is accessed, and when

Google user dataScope requestedWhen it is read
Your Google account identifier, email address, name and profile picture URLopenid, userinfo.email, userinfo.profileOnce, when you sign in with Google — in the extension, or with Continue with Google on readforme-tts.com
The files and folder the extension itself creates in your Drive: the Read For Me: Text to Speech folder, the audio generated for you, its transcript, and read-for-me-index.jsondrive.fileOnly after you link Google Drive in Settings, and only for the sync you asked for

drive.file is a per-file scope: it grants access only to files this extension created, so we cannot list, read, change or delete anything else in your Drive. The Drive scope is requested lazily, when you first link Drive — the ordinary sign-in never asks for it.

How Google user data is used

  • Account identity — to create and identify your account, attach your plan, credits and synced library to it, and show the name and picture back to you in the extension and on the account pages.
  • Drive files — to write generated audio into your own Drive and read it back when you restore your library on another device. Nothing else is done with them.

Google user data is not used to build advertising or user profiles, to determine creditworthiness, or to train machine-learning models. Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Where Google user data is stored

  • The account details received at sign-in (Google's account identifier, your email address, name and profile picture URL) are stored with your account record in our database, and are deleted when you delete your account.
  • Your Drive files stay in your Drive. They are written straight from your browser to Google's Drive API and never pass through our servers, so we hold no copy of them and no audio in Drive is readable by us.
  • Sign-in happens on Google's own consent screen, and your Google password is never sent to us.

Who Google user data is shared with

Nobody. Google user data is not sold, rented, or shared with advertisers, data brokers or any other third party, and it is not used for anything other than the features you switched on. Nobody reads it, except where you ask us to look at your account to fix a problem you reported — an issue report carries the page you were on, never your Google account data or your Drive files.

Revoking access to Google user data

  • Unlink Google Drive in the extension's Settings revokes the extension's Google access altogether, because Google revokes a grant per client — the sign-in scopes are revoked with it. The files already in your Drive stay there and remain yours.
  • Sign out ends our session, and Account → Delete account and data removes the account record that holds your Google account identifier.
  • Access can also be revoked at any time, from any device, at https://myaccount.google.com/permissions — which lists what each app holds and what it was granted.

The website

The marketing pages at readforme-tts.com are served by the same service as the premium API and, like the extension, they run no analytics and set no cookies of their own. They are also served with a Cache-Control: no-transform instruction, which tells Cloudflare — the network that delivers them — not to insert its own JavaScript-detection or web-analytics scripts into them. Nothing is added to a page on the way to your browser.

The subscription section of the home page embeds Stripe's pricing table. That is the only third-party script the site loads: it is served by Stripe, which sees the IP address and the page it was loaded from, and may set its own cookies so it can show the right currency and remember a checkout that was started. Stripe handles that data under https://stripe.com/privacy.

The table appears only while an account is signed in, and the checkout it opens carries that account's opaque identifier, so the plan lands on the right account without anything else about it being sent. What is typed at checkout — an address, a card — goes to Stripe, not to us.

Blocking js.stripe.com hides the pricing table and affects nothing else — an account can still be created, and a plan chosen, from the account page.

Data sharing

We do not sell your data. We do not share it with advertisers or data brokers. We share data only with the services listed above, and only as needed to deliver the feature you used, plus where we are legally required to do so.

Audio stored in your own Google Drive is governed by your agreement with Google, not by us. We cannot read files in your Drive other than the ones the extension created — the extension requests the narrow drive.file permission, which grants access only to files it creates itself.

Data retention and deletion

  • Local data is kept until you clear it. Each site's cache is removed by Clear cache for this site, by clearing that site's data in Chrome, or by uninstalling the extension.
  • Server-side data is kept while your account exists. Issue reports are kept for as long as they are useful for fixing the reported problem.
  • A report you filed while signed out has no account attached, so the account controls cannot reach it. Ask us to remove it at privacy@readforme-tts.com and include the page URL you reported.
  • You are in control. In the extension's settings, Account → Export my data downloads your account details, synced clips, issue reports, credit ledger and usage records as JSON. Account → Delete account and data permanently deletes your synced audio and your issue reports (including their page snapshots and page audio) from storage, and erases your credit ledger, usage records, sessions and subscription association.
  • A minimal record (your Google account identifier, or your email address for a password account, plus the fact that the one-time trial was claimed) is retained after deletion so that deleting and re-registering cannot be used to claim the trial repeatedly. Your password hash, pending codes and failed-attempt counters are deleted along with the rest of the account. No audio, transcript, ledger or personal profile data is retained.
  • Cancelling a subscription does not delete your account; your plan simply lapses at the end of the paid period.

Children

This extension is not directed at children and we do not knowingly collect data from children.

Changes to this policy

If our data practices change, we will update this policy and revise the date at the top. Material changes will also be noted in the extension's Chrome Web Store listing under version history. If a change concerns how Google user data is accessed, used, stored or shared, we will state it here before the change takes effect, and any change to the Google permissions the extension asks for must be consented to again on Google's own consent screen before it takes effect.

Contact

Questions about this policy, or a request to see or delete your data: privacy@readforme-tts.com. Questions about the extension itself can go to support@readforme-tts.com, or through the form at https://readforme-tts.com/contact.