File handling
Your book stays in the tab
Local book files are read and narrated in your browser and are not uploaded. There is no account and no cloud voice service. This page shows what stays in the tab, what leaves it, and how ads are handled.
What stays on your device
- The book or document bytes you open from your device
- The text and chapter structure used by the app
- The generated audio while it is playing
- Your reading position and library, kept in your browser
- Voice, speed and theme preferences
What leaves your device
| Action | What leaves the device | Why |
|---|---|---|
| Open a local file | Nothing | Parsing and speech are local |
| Open the app | The speech runtime is downloaded from a public CDN | So speech can run on your device; cached after the first visit |
| First use of a voice | The voice model and the voice's files are downloaded from a public model host | So speech can run on your device; cached after that |
| Paste a URL | A direct request to that URL | Fetching the article |
| Show an ad | A request to the ad network, with standard request data | Serving the ad; see the privacy policy |
| Visit or install the app | Standard request metadata to the site host/CDN | Serving the site and app assets |
What is not collected
There is no account, no upload endpoint and no server-side book storage. Ad data is handled by the ad network; the privacy policy covers it.
How to verify it
- Open DevTools → Network and clear the log.
- Open a local EPUB or PDF and start playback.
- Look for a request that carries the file. The app does not upload the file; ad requests are separate and are covered by the privacy policy.
- After the voice has been prepared, switch to airplane mode and press play.
On-device voice vs cloud read-aloud
| Dimension | This app | Cloud read-aloud |
|---|---|---|
| Where speech is generated | In your browser | On a remote service |
| File upload | No for local files | Usually yes |
| Account | No | Usually yes |
| Offline | After setup | Usually no |
| Languages | English only today | Often many |
Read more about local text to speech · What works offline · Compare read-aloud approaches.
Threats and limits
Local processing reduces the data you hand to a service; it does not make a compromised device safe. Browser extensions, malware, a shared computer and the hosting provider's request logs are outside the app's control. The voice is a third-party component with its own license; the source is not publicly distributed.
Limits
- The hosting provider still sees normal HTTP metadata.
- The voice is fetched once for your device.
- A URL import fetches that URL directly.
- Ads make requests to an ad network.
- Generated audio is not saved as a library.
- No open-source or self-host claim: the repository is private.
Questions
Short answers to the things people ask before opening a file.
Do you upload my book?
No for local files. The file is read and narrated in your browser. There is no upload endpoint.
Do you train on my data?
There is no account or server-side book storage, so there is no book data to train on. The app uses a third-party voice; see the privacy page for the network requests involved.
Can I use it offline?
Yes, once the app and its voice are cached. The first visit needs internet.
Is it open source?
No. The application source is not publicly distributed. Third-party components have their own licenses.
Does it need an internet connection?
The first visit does, so the app and its voice can load. After that, local files can be read offline.
Try it with your own file
Open a local book and check the network panel.