Your account: email address, display name, and a hashed password, stored with our authentication service (PocketBase, hosted on our own servers in the EU).
Your content: the ebooks and texts you upload or import, the text extracted from them, and the audio narration generated for you. These are stored so your library and listening positions work across sessions and devices.
Usage needed to run the service: playback sessions, narration jobs, plan and billing status, and standard server logs (IP address, timestamps, requested endpoints) kept for security and debugging.
What we do with it
For Premium voices, we send text to Inworld to generate your audio narration. Standard voices are generated on our own servers in the EU or, when your device supports it, on your device itself; for them, text is not sent to a third party for narration, and audio made on your device stays in its storage until it is cleared or replaced. We also send book text and metadata to OpenAI to help identify book structure and enrich book information, and, when you enable Enhanced narration, to add expressive markup. We do not sell your data or share it for advertising.
On iOS and Android, payments are processed by Apple or Google Play and subscription status is managed through RevenueCat. On the web, payments are processed by Stripe. We never see or store card numbers; we store your plan and subscription status.
We use PostHog (EU endpoint) for product analytics and error diagnostics, linked to your account identifier. This includes app interactions, device and app information, and approximate location inferred from your IP address. We also use self-hosted Umami for website traffic analytics. These help us understand feature use and playback problems. Session replay and automatic interaction capture are disabled. We do not use advertising trackers or sell your data.
Creator referrals: when you open a creator’s Book2Speech link on the web, we remember its public creator code in your browser for up to 30 days (local storage and a first-party cookie). When you sign up, we link a new account to the first creator code it used, to apply the creator’s first-payment offer and to calculate the creator’s commission from your web subscription payments (excluding tax and refunds). Our short-link service counts visits to the link without knowing who you are. Creators see only totals, never who signed up or what they bought.
When you submit optional in-app feedback, we store your ratings, comments, and relevant book and listening context. We forward this feedback with your account name and email to our private Discord feedback channel so we can investigate and respond.
Retention and deletion
Uploaded books, generated audio, and listening history stay in your library until you delete them. Deleting a book removes its files and generated audio that no other account references.
You can delete your entire account from Settings → Delete account, in the app. This removes your books, audio, sessions, usage records, subscription record, and the account itself. Web subscriptions are cancelled during deletion; Apple and Google Play subscriptions must be cancelled separately through the store. Payment providers may retain records required for accounting or fraud prevention. For deletion of analytics records associated with your account, contact support@book2speech.com. Server log lines age out within 30 days.
Your rights
You may request a copy of your data, correction, or deletion at any time by using the in-app tools or contacting support@book2speech.com. If you are in the EU/EEA, you have the rights provided by the GDPR; the data controller is the operator of book2speech.com.
Contact
Questions about this policy: support@book2speech.com.