Privacy Policy — epilogue
Last updated: 2026-05-15
epilogue ("the app", "we", "our") is a personal book-tracking app published by
oturk1. This policy explains what data the app handles, where it lives,
and what we do (and don't do) with it. It applies to the Android version of the app
distributed via Google Play.
TL;DR
- We don't run any servers. We don't collect, store, or transmit your data to ourselves or to anyone else.
- Your library, TBR, reading log, notes, reviews, and quotes live on your device.
- If you choose to enable sync, your data is uploaded to your own Google Drive in a private application folder we cannot read from our end.
- The only network calls the app makes are to public cover/genre lookup services (Google Books, Open Library) so it can fill in book details — and only for the books you choose to look up.
What data the app handles
The app stores the following on your device, locally:
- Books in your library (title, author, dates, ratings, reviews, notes, tags, cover URLs, page count, audiobook duration, playback speed, re-read count, source, quotes).
- Books on your TBR (to-be-read) list.
- Your daily reading log (which books you read, pages or minutes per session, notes).
- App preferences (theme, view mode, rating style, sort order, format filter, monthly/yearly reading goals, tutorial seen-flags, your name).
This data does not leave your device unless you explicitly:
- Enable Google Drive sync (see below), or
- Export a backup file (CSV or JSON) and share / save it via your device's share sheet.
Google Drive sync (optional)
If you sign in to Google Drive from the app's Sync settings, the app uploads a single
JSON snapshot of your data to a hidden application folder inside your
Google Drive (appDataFolder scope). This folder is private to the epilogue app
— it isn't visible in your normal Drive UI and other apps cannot read it.
- We do not have access to your Drive or your data.
- We do not store your OAuth tokens on our servers — they live in your device's secure keystore.
- You can disconnect at any time via Settings → Sync → Disconnect Drive. To delete the remote snapshot entirely, use the "Reset everything" option, or revoke the app from your Google account at drive.google.com → Settings → Manage apps.
The OAuth flow uses Google's standard authorization endpoints. We request only the drive.appdata scope.
What data we do not collect
- Email addresses, phone numbers, real names beyond what you type for display.
- Crash reports, analytics events, page-view tracking, advertising identifiers, location data.
- Anything from your camera, microphone, contacts, or photo gallery beyond what you explicitly pick (book cover photos, ISBN barcode scans). Permission prompts only fire when you tap the relevant feature.
Network requests
The app contacts these third-party services on your behalf, and only when you trigger an action that needs them:
- Google Books API and Open Library — to look up cover art, page counts, and genre metadata for books you add. Sends only the book's title, author, or ISBN.
- Google Drive API — only when sync is enabled.
We do not embed any analytics, ad networks, or tracking SDKs.
Children's privacy
The app is not directed at children under 13 and does not knowingly collect any data from them. Since the app collects no data at all, this is true by construction.
Your rights
Because all your data lives on your device (and optionally in your own Google Drive), you control it:
- Export: Settings → Backup & Restore → "Back up to a file"
- Delete locally: Settings → Danger Zone → "Delete ALL books" / "Clear Journal & streaks" / "Reset everything"
- Delete remote Drive copy: Settings → Danger Zone → "Reset everything" (or revoke via Google account settings)
Uninstalling the app removes all local data. The remote Drive snapshot (if any) is not automatically removed by uninstall — use "Reset everything" first if you want the remote copy gone.
Changes to this policy
If the app ever starts collecting data — it currently doesn't and there are no plans to — this policy will be updated and the app will request explicit consent before any change in data handling takes effect.
Contact
Questions about this policy or how the app handles data: open an issue at the app's repository, or contact the developer through the Play Store listing.