← Back
Privacy Policy
Privacy Policy
Last updated: July 19, 2026
In short EarTexts itself has no server, no database, and no accounts. Reading text aloud on-screen never leaves your device. Two things do involve outside services: downloading audio (sent to a third-party speech provider — Section 3) and, if you accept cookies, anonymized analytics and advertising (Section 4).

1. What data EarTexts touches

EarTexts is a static, single-page web app with no backend server of its own. What happens to your data depends on which feature you use:

FeatureWhat happens to the data
Typed text (on-screen "Speak" playback)Stays in your browser's memory; sent to your OS's local speech synthesizer, never to any server
Typed text (Download Audio)Sent to a third-party cloud text-to-speech provider for processing — see Section 3
Downloaded audio filesGenerated by the third-party provider, then saved directly to your device; never stored or logged by EarTexts
Language/voice preferencesKept only in the current browser tab's memory for the duration of your session
Browsing/usage data (if you accept cookies)Collected by Google Analytics and Google AdSense — see Section 4

EarTexts does not request microphone access and has no speech-to-text or transcription functionality.

2. No accounts

EarTexts does not ask you to create an account. We have no login system and no way to identify you by name, email, or similar direct identifiers. That said, please read Section 4 below — if you accept cookies, Google Analytics and Google AdSense do collect certain browsing data, as described there.

3. Third-party speech service (Download Audio only) — please read

The on-screen Speak button uses your browser's own built-in Web Speech API, processed entirely using your operating system's local voices. No data is sent to EarTexts or to any third party for this, and it works fully offline.

The Download Audio button works differently, and this is one place your typed text leaves your device: to generate a real, downloadable audio file, EarTexts uses a third-party SDK called Puter.js, which sends your text to a cloud text-to-speech provider (by default, Amazon Polly) for processing. That provider generates the audio and returns it to your browser, which then saves it as a file. This requires an internet connection, and means:

4. Analytics and advertising (Google) — only after you accept cookies

EarTexts uses Google Analytics (GA4) to understand overall usage (e.g. how many people visit, which pages are used) and Google AdSense to show ads that help keep the app free. Both are configured to respect your cookie choice using Google's consent mode:

Google Analytics and AdSense are operated entirely by Google, not by EarTexts. Google's own Privacy Policy governs exactly what it collects and how it's used; EarTexts has no visibility into or control over Google's internal processing. You can opt out of Google Analytics tracking across all websites using Google's browser opt-out add-on, and manage ad personalization generally at Google Ads Settings.

5. Cookies

Here is what may be stored on your device, depending on your choices:

Cookie / storageSet byPurposeDuration
eartexts_consentEarTexts (first-party)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_themeEarTexts (first-party)Remembers whether you prefer dark or light mode. Only set if you clicked "Accept."365 days
_ga, _ga_*Google AnalyticsDistinguishes visitors for aggregate usage statistics. Only set after you click "Accept."Up to 2 years (set by Google)
AdSense cookies (e.g. __gads, __gpi)Google AdSenseAd delivery and, if consented, ad personalization. Only fully set after you click "Accept."Varies (set by Google)

The two EarTexts cookies are first-party (set directly by eartexts.app), contain no personal data or unique identifier, and are never shared with anyone. The Google-set cookies are third-party and governed by Google's own policies linked above. Puter.js or the third-party speech provider may also set their own cookies or request-level identifiers when you use Download Audio, independent of your analytics/ad cookie choice. You can clear any cookies at any time from your browser's site settings, or use the "Cookie Settings" link in the footer to change your EarTexts-specific choice.

Browser storage, not just cookies EarTexts also mirrors the two cookies above into your browser's localStorage, as a backup so your cookie choice and theme preference still stick even if cookies are blocked or don't persist in your particular browser setup. This mirrored data contains exactly the same non-personal values as the cookies (your consent choice and dark/light preference) — nothing additional is stored. Beyond that, EarTexts does not use localStorage, sessionStorage, or IndexedDB to persist anything else. Your typed text and voice/language selection live only in memory for the current tab and disappear when you close or refresh the page. (Your browser's own HTTP cache and, if installed as an app, the offline service worker cache, may separately store copies of EarTexts' own code and icons — never your typed text.)

6. Children's privacy

EarTexts does not knowingly collect personal information from anyone, including children, because it does not collect or store personal information on any server it operates. Text sent through the Download Audio feature is subject to the third-party provider's own policies (Section 3), and analytics/advertising data described in Section 4 is subject to Google's own policies and age-related safeguards. The app is text-reading utility software, not a service that solicits personal data.

7. Changes to this policy

If EarTexts ever changes how it works in a way that affects this policy — for example, adding or removing a third-party service — 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.