1. What data EarTexts touches
EarTexts is a static, single-page web app. It does not run its own backend server, and it does not send your text, audio, or transcriptions anywhere over the network. Everything happens locally using your browser's built-in Web Speech APIs:
| Feature | What happens to the data |
|---|---|
| Typed text (Text → Voice) | Stays in your browser's memory; sent to your OS's local speech synthesizer, never to a remote server |
| Microphone audio (Voice → Text) | Processed by your browser's built-in speech recognition, which may briefly use your browser vendor's own cloud service (see Section 3) — EarTexts itself never receives or stores it |
| Downloaded audio files | Generated and saved directly to your device; never uploaded anywhere by EarTexts |
| Language/voice preferences | Kept only in the current browser tab's memory for the duration of your session |
2. No accounts, no tracking, minimal cookies
EarTexts does not ask you to create an account, does not use analytics scripts, and does not include any advertising code. We don't know who you are, and we have no way of identifying you across visits or across other websites. The only cookies EarTexts sets are described in Section 5 below, and they exist purely to remember your own preferences on this site — never to track you.
3. About your browser's speech engine
The one nuance worth being upfront about: some browsers (notably Chrome) implement microphone transcription using a cloud speech-recognition service operated by the browser vendor (e.g., Google), rather than doing it fully on-device. When that's the case, your audio is sent from your browser directly to that vendor's servers for processing — not to EarTexts, and not through any server we operate. That data flow is controlled by your browser and governed by your browser vendor's own privacy policy, not by us. Other browsers (such as Safari on-device dictation) may process speech entirely locally. You can check your specific browser's documentation for details on how it handles voice data.
4. Microphone permission
Microphone access is requested and stored by your browser, tied to this page's origin. EarTexts cannot access your microphone without that browser-level permission, and you can revoke it at any time from your browser's site settings — doing so takes effect immediately, with no account or profile to update on our end.
5. Cookies
When you first visit EarTexts, a banner asks whether you're comfortable with a small preference cookie. Here is exactly what EarTexts stores, in full:
| Cookie name | Purpose | Duration |
|---|---|---|
eartexts_consent | Remembers your cookie-banner choice so we don't ask again every visit. Set regardless of which option you choose, since it is strictly necessary to respect your choice. | 365 days |
eartexts_theme | Remembers whether you prefer dark or light mode. Only set if you clicked "Accept" on the cookie banner — if you chose "Essential only," this cookie is never created and your theme simply follows your system setting each visit. | 365 days |
Both cookies are first-party (set directly by eartexts.app, not by any third party), contain no personal data, no unique identifier, and are never shared with anyone. EarTexts sets no advertising, analytics, or cross-site tracking cookies of any kind. You can clear these cookies at any time from your browser's site settings, or by revisiting the "Cookie Settings" link in the footer to change your choice.
6. Children's privacy
EarTexts does not knowingly collect personal information from anyone, including children, because it does not collect personal information from anyone at all. The app is text-and-voice utility software, not a service that solicits or stores personal data.
7. Changes to this policy
If EarTexts ever changes how it works in a way that affects this policy — for example, if a future version were to add optional cloud sync — we'll update this page and revise the "Last updated" date above before that change takes effect.
8. Contact
If you have questions about this policy, please reach out through the channel where you obtained this App.
See also our Terms of Service for the rules governing use of the App.