Privacy Policy
Scope. Statements that playback text stays on your device describe on-device playback in the web application. They do not describe Share. The Chrome extension section is the account of Share: copying a link does not contact the site, the link still contains the selection, and opening that link sends the selection to unlimitedtts.com in the URL query string.
Web Application Privacy
On-device playback in the Unlimited TTS web application is designed to keep the text and audio for that playback on your device. This section does not describe Share or the Chrome extension; those are covered below.
- Device mode (Quick): Uses the Web Speech API built into your browser. For this playback path, text is processed locally by your operating system.
- AI mode (Natural): Runs a neural TTS model (Supertonic TTS-3) directly in your browser using WebGPU or WASM. Text for this playback is processed on-device. The model files are downloaded once and cached for future visits. This playback does not send that text to our servers.
- Browser-supplied online voices (only if you choose them): Some browsers also offer online voices run by the browser vendor's cloud service. The main web app does not list them unless you turn on Show online voices. Your browser sends text to that service only when you choose an online voice and press play with it; on-device voices and Natural voices never do. The one exception to the default is a language that has no on-device voice: its online voices are listed, marked ☁, and still send nothing unless you pick one and play. The vendor's handling of that text is outside our control.
- No signup required: We do not collect names, email addresses, passwords, or any account information for web use.
- No cookies: We do not use cookies for authentication or tracking. Essential browser storage (e.g., cached models, voice preferences) is handled by the browser itself.
- Anonymous browser ID: The main web app stores a random ID in your browser's local storage. It keeps you in the same version of a feature test across visits and is sent only with long-download payment requests, where it links a payment to its download. It is not sent to Google Analytics or Clarity, which receive only the name of the test version you see.
Analytics & Diagnostics
We use non-intrusive analytics solely to find bugs and improve usability:
- Google Analytics: Loaded lazily after page load via
requestIdleCallback. On the main web app it measures aggregate traffic and feature usage, and the text typed into the TTS field is not sent as analytics content. This does not describe Share or/embed/URLs. - Microsoft Clarity: Loaded lazily after page load. Records anonymized session replays and heatmaps to identify UI bugs and broken interactions on the main web app. No text you type into that page's TTS input is captured by Clarity. This does not describe
/embed/or text carried in a URL. - Both analytics scripts are deferred so they never block TTS functionality.
The player at /embed/ does load Google Analytics and Microsoft Clarity when the browser is idle after the page loads. Opening a Share link can send the text query to the site and include it in Google Analytics page_location. Both scripts can access the query string and the page. The statements above about the main web app's TTS field are not a claim that text on /embed/ is never transmitted. Details are in the Chrome extension section.
AI Agent API Privacy
The Unlimited TTS API (https://api.unlimitedtts.com) is a separate paid service for automated agents and systems. Because it generates speech server-side, different privacy considerations apply:
- Text you send: The text you submit for synthesis is sent to our API and forwarded to upstream speech-synthesis providers to generate audio. We do not use your text for model training, advertising, or any purpose other than fulfilling your request.
- Audio storage (optional): By default, generated audio is retained briefly so you can poll async jobs and download the result later. You may opt out of storage entirely by sending
storeAudio=falsein your request. When opted out, audio is streamed to you and immediately discarded — no copy is retained. - Prepaid accounts: API access uses bearer-token credit accounts. We store the account ID, balance, and transaction history necessary for billing. No raw card data is stored by us; Stripe Checkout handles all payment details.
- Rate-limit counters: We maintain rolling-window request counters (bound to your credit account or IP address) to enforce fair use and prevent abuse.
Third-Party Services
- Stripe: Processes all payments for the AI Agent API. Subject to Stripe's Privacy Policy.
- Upstream speech providers: Text submitted via the API is forwarded to the speech-synthesis provider configured at the time of your request. We do not control their data practices; refer to their respective privacy policies.
- Cloudflare: Our API and website are served through Cloudflare. Subject to Cloudflare's Privacy Policy.
Data Lifecycle
| Data | Retention | Deletion |
|---|---|---|
| Web app playback text & audio | None for that playback — processed in your browser | N/A |
| Extension selection and Share link | The extension does not store the selection. A copied link contains it and, by itself, sends nothing. Opening the link sends the query string to unlimitedtts.com; hosting logs and Google Analytics page_location may retain it under those providers' practices. | Extension: nothing is kept to delete. Logs and analytics: per the hosting provider and Google, see Analytics. |
| API-generated audio (default) | A few days | Automatic deletion after retention period |
| API-generated audio (storeAudio=false) | None — streamed and discarded immediately | Immediate |
| API credit account & balance | Until account is inactive or you request deletion | On request |
| Analytics data | Google Analytics: 26 months; Clarity: per Microsoft policy | Per provider policy |
The playback row describes on-device web playback only. A Share link is a separate copy of the selection: copying it sends nothing, and opening it sends the query string.
Chrome extension
The Unlimited TTS Chrome extension can share text you select in Chrome. This section describes that Share action, the embed page it uses, and what the extension stores.
Share
Share compresses the selected text with raw deflate, base64url-encodes the compressed bytes, and places that value in the text query parameter of https://unlimitedtts.com/embed/. The link looks like https://unlimitedtts.com/embed/?text=….
Raw deflate and base64url are compression and encoding. They are not encryption, and they do not anonymize the text. A shared URL contains the selection. Anyone with the URL can reverse the encoding and read the selection. Do not share a link if the selection is private.
- Successful Share: Share only copies the URL to the clipboard. That copy makes no request. The selection is not sent to unlimitedtts.com by the act of copying.
- Clipboard fallback: If writing to the clipboard fails, the extension opens the URL. The browser then makes a GET request to unlimitedtts.com, and the compressed selection is in the query string of that request.
Opening the link later does the same thing, whether you open it, another device opens it, or someone you sent it to opens it. The query string is sent to unlimitedtts.com and can be received by the site and its hosting provider. It may be written to server or hosting logs. The selection is in that query string in compressed form, not as a separate encrypted payload.
Embed page
/embed/ reads the text query parameter, base64url-decodes it, inflates the raw deflate data, and places the plaintext in textarea#text-input and p#embed-transcript.
After the page loads, and when the browser is idle, /embed/ loads Google Analytics, measurement ID G-87Z90QSTWJ, and Microsoft Clarity, project ID wz96jfwzzh. Google Analytics is started with a bare gtag("config", "G-87Z90QSTWJ") call. That records page_location, which is the page address and includes the text query parameter. When /embed/ is opened, the compressed selection in that query can be sent to Google Analytics.
Both scripts run in the page, so both can access the query string and the DOM, including the decoded plaintext in textarea#text-input and p#embed-transcript. The page's own code does not explicitly send that decoded plaintext to Google or Microsoft. Clarity masking on this page is not established. This policy does not claim that Clarity masks the selection, and it does not claim that the text is never transmitted.
Query text may reach hosting and server logs, and Google Analytics page_location, whenever /embed/ is opened. That includes the clipboard-failure path and any later open of a copied link.
Storage
The selection is not persisted. The extension does not use chrome.storage.sync, localStorage, sessionStorage, or IndexedDB. The voice-model cache does not store selections.
chrome.storage.localstores onlyaiVoiceId,aiLang, andaiSpeed.chrome.storage.sessionstoresphase,detail, andprogress, andunlimitedttsStatusTarget(tabIdandframeId). It does not store the selection.- If
chrome.storage.sessionthrows,phase,detail, andprogressfall back tochrome.storage.local. The selection is not part of that fallback.
Deployment checklist
The disclosures above are the final account of the extension. Complete this checklist before Chrome Web Store submission. Submit the extension only after this policy is deployed.
- Deploy the policy. Publish this page so the final text is publicly available at https://unlimitedtts.com/privacy/.
- Check the deployed page. Open that URL and confirm it shows this extension section: Share puts the selection in the
textquery parameter, opening the link can send that query to the site and to Google Analyticspage_location, and storage is limited to the keys named above. - Set the store listing. Use
https://unlimitedtts.com/privacy/as the Chrome Web Store privacy-policy URL. - Then submit. Submit the extension to the Chrome Web Store only after that deployed policy is live.
Contact
For support, privacy questions, data-deletion requests, or to report a concern, email [email protected].
You can also reach the maintainer, Chris Graney-Ward, through the GitLab repository.