Thank you for choosing Readio. Readio, made by Flynch MB ("Flynch," "we," or "us"), reads books you already own in your Amazon Kindle library aloud with natural voices. This Policy covers the Readio apps for iPhone and Android, the Readio extension for Chrome, and the Readio website (together, the "Service"). Readio keeps your library and preferences on your device. A Readio account is optional in the apps and is needed to listen in the Chrome extension and to buy a plan on the website. Service providers process identifiers, account and purchase details, app interactions, and book passages as described below.
If you do not agree with this Policy, please discontinue use of the Service. Capitalized terms not defined here have the meanings given in the Readio Terms of Service.
1. Information We Collect
1.1 Data Stored on Your Device
Readio keeps its working data on your device, not on our servers:
- The first name and listening preferences (goals, listening moments, voice, pace, and an optional referral code) you provide during setup.
- Your Kindle library list, reading progress, and per-book narration data, so playback can resume where you left off.
- Cached synthesized audio, so pages you have listened to replay without a network request.
Deleting the app deletes this data. The in-app "Disconnect Kindle" option signs out of your Amazon session and clears your library list from the device.
The Chrome extension keeps your settings (voice, speed, volume, and word highlighting) and your Readio sign-in in the browser's extension storage on your computer. Removing the extension deletes this data.
1.2 Readio Account
You can create a Readio account so that one plan works in the apps, in the Chrome extension, and on the website. You sign in with a one-time code sent to your email address, with Apple, or with Google. There is no password.
- We store your email address, an account identifier, the sign-in method, your sign-in sessions, and the state of your plan (the plan, its status, and its renewal or end date) on our server in the European Union, with an encrypted-in-transit backup at a cloud storage provider.
- When you sign in with a code, an email delivery provider receives your email address and the code in order to send it.
- When you sign in with Apple or Google, that provider tells us your email address and an identifier for your account with it. If you use Apple's "Hide My Email", we receive the relay address Apple creates.
- On the website, a cookie keeps you signed in. It is used for sign-in only, not for tracking. In the apps and the extension, a sign-in token is stored on your device.
1.3 Amazon Sign-In
To read your books, Readio opens Amazon's own Kindle Cloud Reader website in a secure in-app browser view, where you sign in directly with Amazon. Your Amazon credentials are entered on Amazon's pages and sent to Amazon only — we never receive, see, or store your Amazon password. The resulting session remains in the browser storage on your device. Amazon's handling of your account is governed by Amazon's own privacy notice. Readio is an independent product and is not affiliated with, endorsed by, or sponsored by Amazon.
The Chrome extension works on Amazon's Kindle Cloud Reader website (read.amazon.com) in your own browser, where you are signed in with Amazon as usual. The extension runs on that website only. It reads the text of the book page on your screen in order to speak it, show the place of the voice on the page, and turn the page. It does not read your Amazon credentials, and it does not read other websites.
1.4 Book Text for Narration
To speak a page, short passages of the book you are currently reading are sent from your device, or from the Chrome extension, through our speech relay to a third-party speech-synthesis provider, which returns the audio. The relay does not store the text or the audio, and responses are marked not to be cached server-side. The provider processes the passages solely to synthesize speech, in accordance with its own privacy and product terms. In the apps, the synthesized audio is cached on your device only.
To check that a listener has a plan and to prevent abuse, the relay keeps a daily count of the characters and requests it served for each listener, with the listener's plan. The listener is identified by the Readio account identifier, by an app identifier, or, for older app versions that send no identifier, by a one-way code made from the day and the network address. The relay also keeps a one-way code of a sign-in token for a short time so that it does not ask about the account on every request. These records contain no book text, no book titles, and no email address.
In the Chrome extension, an account without Readio Pro is read by a voice of your browser or computer instead. That text is not sent to our relay. Some browser voices are online services of the browser's maker, which then receives the text under its own terms.
1.5 Purchases
Subscriptions use the Apple App Store on iOS and Google Play on Android. RevenueCat manages subscription access. RevenueCat receives an anonymous app user identifier and purchase metadata, such as plan, price, currency, and renewal state. If you sign in to a Readio account in the app, RevenueCat also receives your Readio account identifier, so that the plan follows the account. Apple or Google processes the payment. We do not receive your card number or payment account credentials.
Plans bought on the website or from the Chrome extension are paid through Stripe. Stripe collects your email address and payment details on its own checkout page and processes the payment. We receive a customer identifier, the plan, its status, and its renewal or end date from Stripe. We do not receive your card number. A plan bought on the website without signing in creates a Readio account for the email address given at checkout.
1.6 Notifications
If you allow notifications, the permission is used to deliver reading reminders on your device. You can revoke it at any time in your device settings.
1.7 Analytics and Attribution
The Readio apps use PostHog with EU-hosted analytics to understand app use and improve the app. PostHog receives app interactions, screen visits, app lifecycle events, and an anonymous app identifier. Events cover setup, subscription screens, Kindle connection, and narration controls. PostHog and RevenueCat identifiers link subscription events to app interactions.
These events do not include your name, Amazon credentials, book text, book identifiers, or referral code. Session replay and automatic touch capture are off.
On iOS, AppsFlyer supports install and session attribution and connects attribution to subscription events. It receives an app installation identifier and attribution data. AppsFlyer does not start on Android. The Android app does not use the advertising ID.
The website uses PostHog with EU-hosted analytics to count visits. PostHog receives the pages you visit, the site you came from, your browser and device type, and events for store links, sign-in, and plan purchase. The website asks before it uses a cookie. If you accept, PostHog keeps an identifier in a cookie and in your browser's local storage, so that a later visit counts as the same visitor. If you decline or do not answer, PostHog sets no cookie and keeps no identifier in your browser: visits are counted with an anonymous identifier that PostHog derives on its servers and that changes each day. Neither identifier is linked to your account. Your answer is kept in your browser's local storage, and you can change it under "Cookie choice" at tryreadio.com/privacy.
The Chrome extension uses PostHog with EU-hosted analytics to understand extension use. PostHog receives events for install and update, sign-in, opening a book, play and pause, and plan screens and purchases, with a random identifier kept in the extension. After you sign in, these events carry your Readio account identifier, so that use in the extension and in the apps counts as one person. These events do not include your email address, book titles, book text, or the addresses of the pages you read.
As with any request over the internet, PostHog receives your IP address and derives an approximate location from it. The website and the Chrome extension use no advertising trackers.
Readio contains no ads. We do not sell personal data.
1.8 Support and Communications
When you contact [email protected], we collect the information you provide, including attachments, to respond and improve our services.
2. How We Use Your Information
We use the data described above to:
- Read your books aloud and keep your place in them.
- Personalize voices, pace, and reminders to the preferences you chose.
- Sign you in and make your plan work on every device where you use the account.
- Process payments and manage subscriptions.
- Check that a listener has a plan, and prevent abuse of the speech service.
- Understand app use, measure subscription events, and improve the app.
- Respond to support requests.
- Comply with legal obligations and enforce our Terms of Service.
3. Legal Basis for Processing (EEA, UK, and Switzerland)
Where GDPR or similar laws apply, we process personal data based on:
- Performance of a contract (providing the narration you requested, your account, and your plan).
- Legitimate interests (maintaining and securing the Service).
- Consent (notifications, where required).
- Compliance with legal obligations.
4. Sharing Your Information
We do not sell your personal data. Data leaves your device only to the following categories of recipients, each to the extent needed to provide the Service:
- Amazon — you interact with Amazon directly, through the in-app browser view or in your own browser, when signing in and reading; Amazon receives what any browser session with Amazon receives, under Amazon's own terms and privacy notice.
- Speech synthesis — a third-party speech-synthesis provider receives the text passages being narrated and returns audio; a cloud infrastructure provider operates the relay that forwards those requests without storing them. Both act on our behalf under data-protection obligations.
- Subscription management — RevenueCat, Inc. (USA) manages subscription entitlements for the apps and receives an anonymous identifier, your Readio account identifier if you sign in, and purchase metadata.
- Web payments — Stripe processes payments for plans bought on the website or from the Chrome extension, and receives your email address and payment details.
- Sign-in — an email delivery provider sends sign-in codes and receives your email address. Apple or Google takes part in the sign-in when you choose it.
- Hosting — infrastructure providers host our account server in the European Union, its backup, and the speech relay, and process the data described above on our behalf.
- Analytics — PostHog processes app, website, and extension interactions and anonymous or account identifiers on our behalf through its EU-hosted service.
- iOS attribution — AppsFlyer processes installation identifiers and attribution data for the iOS app.
- Store payments — Apple processes iOS payments through the App Store. Google processes Android payments through Google Play.
- Legal authorities when we believe disclosure is necessary to comply with law, protect our rights, prevent fraud or abuse, or respond to lawful requests.
- Business transfers in the event of a merger, acquisition, or asset sale. We will notify you before personal data becomes subject to a different privacy policy.
5. Data Retention and Deletion
Your library, preferences, progress, and cached audio remain on your device. The app removes the corresponding local data when you disconnect Kindle, clear cached data, or delete the app.
We keep your Readio account until you delete it. You can delete it in the app (Settings, then your account, then "Delete account"), or ask us by email as described below. A plan from the website that still renews must be cancelled first. Deleting the account removes your email address, your sign-in sessions, and your plan records from our server; copies in backups expire on the backup's schedule. Deleting the account does not cancel a subscription bought in the App Store or Google Play.
Our speech relay does not retain book passages or audio. It keeps the daily usage counts described in Section 1.4, which we delete on request. The speech provider processes passages for narration under its service retention rules. RevenueCat, PostHog, and, on iOS, AppsFlyer retain service data under their retention settings and contractual obligations. Stripe and the store providers retain purchase records under their own policies. We retain support correspondence only as needed for support and legal obligations.
Request deletion of Readio data
Email [email protected] with the subject "Readio data deletion". State which data you want deleted. Write from the email address of your Readio account if you have one. If available, include an app user identifier or purchase reference so that we can locate anonymous service records. Do not send your Amazon password.
You can request deletion of your Readio account, usage counts, app interaction records, app identifiers, and support correspondence. We also request deletion of associated service records where the provider supports it. We retain records that legal obligations require, such as applicable purchase or tax records. Apple, Google, Stripe, and Amazon control records held for their own services. Deletion of Readio data does not delete your Amazon account or cancel a store subscription.
We respond within the applicable legal deadline. We explain any required retention when we respond to your request.
6. Data Security
We use technical, organizational, and administrative safeguards designed to protect personal information against unauthorized access, loss, misuse, or alteration, including transport encryption for all network requests. No online service is completely secure; please keep your device and software updated and notify us of any suspected compromise.
7. International Data Transfers
We operate in the European Union and rely on service providers located in other countries, including the United States. When personal data is transferred internationally, we rely on appropriate safeguards, such as Standard Contractual Clauses, to protect your rights.
8. Your Rights and Choices
Depending on your location, you may have the right to:
- Access, correct, or delete personal data we hold about you.
- Object to or restrict certain processing activities.
- Receive a copy of your data in a portable format.
- Withdraw consent for processing where consent is the legal basis.
To exercise these rights, email [email protected] with your request. For account, local app data, and service record deletion, follow Section 5.
9. Children's Privacy
Readio targets adults aged 18 and over. We do not knowingly collect personal information from children. If you believe a child has provided personal data without proper consent, contact us so we can remove it.
10. Third-Party Links and Services
The Service includes integrations with websites and platforms we do not control, most notably Amazon's Kindle Cloud Reader. This Privacy Policy does not apply to those third parties. Review their policies before providing personal information.
11. California Privacy Rights
If you are a California resident, you have the right to know the categories of personal information we collect, use, and disclose, as described in Sections 1–4. You may also request deletion of personal information, subject to exemptions under the California Consumer Privacy Act (CCPA). We do not sell or share personal information for cross-context behavioral advertising.
12. EU/EEA Supervisory Authority
If you reside in the European Union, you may lodge a complaint with your local data protection authority. You can find contact details at https://edpb.europa.eu/about-edpb/about-edpb/members_en.
13. Changes to This Privacy Policy
We may update this Policy to reflect changes in laws, technology, or our practices. When we make material changes, we will notify you by in-app notice or by posting an update on our website, and indicate the "Last updated" date at the top. Continued use of the Service after the effective date means you accept the revised Policy.
14. Contact Us
If you have questions, requests, or concerns about this Privacy Policy or our data practices, contact us at:
Flynch MB
Vilnius, Lithuania
[email protected]
We will respond within the timelines required by applicable law.