ReadKeep — Privacy Policy
Last updated: 29 September 2026
ReadKeep has no accounts and never uploads your books, the files you import, the pages you scan or the text you translate. They stay on your device. The only data that leaves your device is anonymous usage and crash information, sent through Google Firebase and described below, and the searches you make for books.
Your books and reading data stay on your device
Your books, the files you import, scanned pages, reading sessions, notes, ratings, goals and streak are stored only on your device. We have no account system and we do not upload, sell or share this data. You can export your reading data at any time (JSON or CSV) from within the app, and you can delete everything by clearing the app's data or uninstalling it.
Files, photos and scans
When you import a PDF, EPUB or photos, the app copies the file into its own storage on your device. Text recognition of scanned pages runs on your device (Google ML Kit). Page photos are taken with Google's on-device document scanner, and the app itself has no camera permission. Nothing you import or scan is uploaded.
Translation and read-aloud
Translation runs on your device (Google ML Kit). The first time you translate into a language, the app downloads that language's translation pack from Google; your text is never sent. Read-aloud uses your phone's own voices, or natural voices that run on your device. A natural voice is downloaded once, from the public sherpa-onnx releases on GitHub; nothing you read is sent.
Book lookups and free books
When you search for a book or scan a barcode, the app sends your search text or ISBN to Google Books and Open Library to fetch titles, covers and details. When you search the free libraries, your search text is sent to Project Gutenberg (and its Gutendex index), Standard Ebooks, Wikisource (Wikimedia) and the Internet Archive, and a book you choose to download is fetched from that library. Cover images are loaded from these services. All requests use HTTPS and contain only what you searched for; each service's own privacy policy covers how it handles requests.
Analytics and crash reporting
We use Google Firebase Analytics and Firebase Crashlytics to understand which features are used and to find and fix crashes. These collect anonymous usage events, app performance and crash diagnostics, and device or app identifiers. This data is processed by Google on our behalf, is encrypted in transit, and is not sold or shared with third parties for their own purposes. We use it only to improve the app. ReadKeep does not use the advertising ID.
Payments
ReadKeep has no in-app purchases, tips or subscriptions, and collects no payment information.
What we do not do
- No ads and no advertising identifiers.
- No in-app purchases or payments of any kind.
- No accounts or logins.
- No selling or sharing of your personal data.
- No location, contacts, SMS, camera or microphone permission.
Permissions, and why each one exists
| Permission | Why ReadKeep asks |
|---|---|
| Internet and network state | Book lookups and downloads, cover images, translation packs and voices, and analytics and crash reporting. |
| Notifications | Progress while a large import or download runs, and the optional daily reading reminder. |
| Foreground service (data sync) | Keeps a large import or a download going when you leave the app, with a visible notification. |
Children
ReadKeep is not directed to children under 13 and does not knowingly collect personal information from them.
Deleting your data
Reading data: clear the app's data or uninstall the app. To ask us to delete analytics or crash data associated with your device, email us at the address below.
Changes
We may update this policy. Material changes will appear here with a new "Last updated" date.