Privacy Policy
How TextToVoice handles conversion text, generated audio, browser history and website analytics.
Updated：
Scope
This policy describes the website’s current data handling. The basic text-to-speech tool does not require an account. Third-party speech, infrastructure and analytics services also apply their own policies.
Text and speech processing
When you generate speech or play a preview, text, the voice identifier, volume, rate, pitch and output format are sent to our Cloudflare Worker. The Worker converts text to SSML and forwards it over a WebSocket to Microsoft Edge’s online Read Aloud endpoint at speech.platform.bing.com. Microsoft produces the audio, which is streamed back through Cloudflare to your browser for playback or download.
In the active Worker version 07e0f54f inspected on 7 October 2026, we found no database, object storage, cache writes or content logging. Audio responses use Cache-Control: no-store, and Workers Logs and Traces were disabled. This describes the inspected application configuration; it does not establish zero retention across Cloudflare, Microsoft or their infrastructure, or a verified retention period for this third-party connection.
Microsoft’s Read Aloud privacy information describes the Microsoft Edge feature. Cloudflare’s privacy policy describes its processing roles and infrastructure services. Neither document by itself confirms the complete handling or commercial licensing of this third-party integration. Browser history is separate local storage, described below. Conversion is not offline; avoid submitting confidential or unnecessary personal information.
Data in your browser
Theme, voice effects, language-banner dismissal and audio history metadata are saved in localStorage. History metadata may include input text, the voice and generation time. Audio files are stored in IndexedDB.
This data belongs to the current website origin and browser profile; it does not automatically sync between devices. Downloaded MP3s are separate files. Other people using a shared device may be able to access local history.
Visits and analytics
The production website configures Google Analytics and Baidu Analytics to understand visits, feature use and performance. Network providers may receive technical information such as IP addresses, browser information and request times when processing requests.
Our custom feature events do not send input text or audio contents; they describe previews, generation, downloads and performance metrics. Third-party analytics scripts may still use cookies or similar identifiers. Production analytics are not loaded in localhost development or previews.
Information you email us
When you contact us, your address, message and attachments are used to handle your enquiry. Send only the details needed to resolve it. Email is processed by the relevant email services. This website has no separate contact-form submission service.
Managing and deleting data
Use the tool to delete individual audio entries or clear history. This does not delete downloaded files or other preferences such as your theme. To remove all local settings, history and cookies, use your browser’s site-data controls. Download any audio you want to keep first.
For questions or requests to access, correct or delete information about you, email [email protected] and explain the scope of your request. Available rights and requirements depend on applicable law and the data actually held. We cannot remotely delete independent files on your device.
Updates and contact
This page and its date will be updated when the described practices change. Contact us with questions about this policy, third-party processing or retention.