Privacy policy
Effective date: 4 October 2026
This policy covers the Readexa app for Android and iOS. Readexa is a reader: most of what you do in it stays on your device. This page lists every case where data leaves your device, who receives it, and why.
What stays on your device
- Your books, comics and imported files.
- Saved web articles and chapters.
- Reading progress, highlights, notes, flashcards, reading goals and stats.
- Text-to-speech audio from voices you download, which run on your device. System voices are handled by your phone's own speech engine, under its own privacy terms.
- Translation and text recognition. These use Google ML Kit on your device; the text you translate is not sent to a server.
None of this is sent to us. If you turn on Google Drive sync, it is copied to your own Google Drive, as described below.
Data that leaves your device
| Service | What is sent | Why |
|---|---|---|
| Firebase Analytics (Google) | Usage events such as screens opened and features used, an app-instance identifier, device model, OS version, country and language. For pages you open in the browser or Reader Mode, the website domain (for example example.com), not the full address. |
To learn which features people use and where the app needs work. |
| Firebase Crashlytics (Google) | Crash reports: stack trace, device model, OS version, app version and the app state at the time of the crash. When Reader Mode cannot extract a page, the website domain. When you report a problem with a page or comic, its page address and title. | To find and fix crashes and pages that do not display correctly. |
| Google AdMob | Advertising identifier, IP address, device information and ad interactions. | To show ads, measure them and limit fraud. Where the law requires it, the app asks for your consent first. |
| Google Sign-In and Google Drive | Only if you turn on sync or backup. Your Google account email, shown in the app so you can see which account is signed in. The app asks for two scopes: drive.appdata, a hidden folder only Readexa can read, used for sync; and drive.file, which covers only files Readexa creates, used for backups. |
To back up and sync your library and reading data to your own Drive. We never see this data; it goes from your device to your Google account. |
| Firebase Authentication and Cloud Firestore (Google) | Only if you redeem a code. An anonymous user ID is created and stored next to the code you claimed, with the time of the claim. | So each code can be used once. |
| Google Play Billing | Purchase details are handled by Google Play. We receive a purchase confirmation, not your payment details. | To unlock Readexa Pro. |
| dictionaryapi.dev | The word you look up. | To show its definition. |
| models.readexa.uk, Hugging Face and GitHub | A normal download request (IP address, app user agent). | To download the voices and language data you choose. The app also downloads a reader configuration file from GitHub that helps Reader Mode find article text. |
| Project Gutenberg, Standard Ebooks and catalogues you add | A normal web request when you browse those catalogues. | To list and download books you choose from those OPDS catalogues. |
| Web sites you open, and Google Search | A normal browser request, as from any web browser. Searches typed in the app go to Google Search. | To load the pages you ask for. Those sites' own privacy policies apply. |
To check whether you are online, the app may contact google.com. No personal data is sent with that check.
What we do not do
- We do not sell your data.
- We do not run our own servers that store your library, notes or reading history.
- We do not collect the content of your books or the text of the pages you open. Page addresses and titles reach us only in the cases listed above.
Your choices
- Sync and backup: turn off Google Drive sync in the app at any time. To delete what was synced, remove Readexa's app data in Google Drive under Settings → Manage apps.
- Ads: review or change your ad consent in the app under Profile → Ad privacy options, and reset or delete your advertising ID in your device settings.
- Everything on the device: uninstalling Readexa deletes its data from the device.
- Questions or deletion requests: email us at the address below.
Google's handling of this data is described in the Google Privacy Policy and Privacy and Security in Firebase.
Children
Readexa is not directed at children under 13, and we do not knowingly collect their personal data.
Changes
If this policy changes, the new version will be posted on this page with a new effective date.
Contact
Questions about privacy: marketingync@gmail.com