Privacy Policy

Last updated: June 2, 2026

Introduction

Welcome to ReadingKulture ("we," "our," or "us"). We are committed to protecting your privacy and ensuring you have a positive experience when using our mobile application ("App"). This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our App.

Please read this privacy policy carefully. If you do not agree with the terms of this privacy policy, please do not access the App.

Our Local-First Architecture

ReadingKulture is built to run without a backend of our own. We do not operate, rent, or maintain any servers or databases that store your account, your identity, or your library. There is no central system where we could look you up. Your books and reading data live on your device, and the only data that ever leaves your device goes directly from your device to services you control or can revoke; your own Google Drive, Google's Gemini AI (anonymously), and Google's analytics service. We never sit in the middle as a custodian of your data.

This means that where this policy says "we," it refers to the App running on your device and the limited, direct connections it makes to those third-party services — not to a server we operate.

Information the App Handles

Information You Provide

  • Google Account Information: When you choose to sign in with Google, the App on your device receives your name, email address, and profile picture from Google. This is used on your device to show who is signed in and to connect directly to your own Google Drive for cloud sync. Because we operate no server, this information is never sent to or stored by us — it stays on your device and is shared only between your device and Google.
  • User Content: The e-books you import, bookmarks you create, highlights and annotations you make, and reading preferences you set are stored locally on your device.

Information Collected Automatically by Third-Party Services

We run no analytics servers of our own. The following data is collected by Google's analytics service directly from your device, not by us:

  • Usage Data: Anonymous usage statistics are collected through Firebase Analytics (a Google service), including which features you use, how often you use the App, and general app performance data such as crashes. This is sent from your device to Google's servers, not to ours.
  • Device Information: Firebase may collect information about your device type, operating system version, and unique device identifiers, for general analytics purposes.

Information We Do NOT Collect

  • We do NOT operate user accounts, servers, or a central database that could store your data
  • We do NOT read the content of your e-books
  • We do NOT track which specific books you read, and analytics never include your book titles or library contents
  • We do NOT sell or share your personal information with third parties for marketing purposes

How Information Is Used

The information described above (most of which never leaves your device) is used for the following purposes:

  • To provide and maintain the App's functionality
  • To enable cloud sync of your library through Google Drive
  • To provide AI-powered book summaries (see AI Features section below)
  • To improve and optimize the App's performance
  • To analyze usage patterns and improve user experience
  • To respond to your inquiries and provide customer support

AI-Powered Features

AI Book Summariser

ReadingKulture offers an optional AI-powered book summarization feature. When you use this feature:

  • What is sent: Extracted text content from your book is sent to Google's Gemini AI API to generate a summary. Only the text needed for summarization is transmitted.
  • Anonymity: Requests are fully anonymous — no user ID, account information, or personal data is attached to AI requests.
  • No server storage: We do not store your book content on any server. The text is transmitted directly to Google's AI service and is not retained by us.
  • Local caching: Generated summaries and follow-up conversations are cached locally on your device in SQLite for offline access.
  • Rate limiting: The feature is limited to 1 book summary per 24 hours to keep the service free for all users.

Highlights & Annotations

Text highlights and annotations you create in the EPUB & PDF reader are stored exclusively on your device's local database. They are never transmitted to any external server unless you choose to back up your library via Google Drive sync.

Data Storage and Security

Local Storage

Your e-books, bookmarks, and reading progress are stored locally on your device using secure storage mechanisms. This data remains on your device unless you choose to sync with Google Drive.

Cloud Storage

If you enable Google Drive sync, your library data is stored in your own Google Drive account in a dedicated folder. We do not have access to your Google Drive; the sync happens directly between your device and your Google account.

Security Measures

We implement appropriate technical and organizational security measures to protect your information. However, no electronic transmission or storage system is 100% secure, and we cannot guarantee absolute security.

Book Sharing (Device-to-Device)

ReadingKulture lets you send books directly to another nearby ReadingKulture user. This feature is private by design:

  • Local transfers only: Books are transferred directly between the two devices over your local Wi-Fi network or a personal hotspot. The files never pass through, and are never stored on any servers; no cloud is involved.
  • Camera (QR scanning): When receiving books, the App uses your camera solely to scan the sender's QR code. The camera feed is processed on-device in real time; no images or video are recorded, saved, or transmitted.
  • Local network access: The App uses local-network access only to connect the two devices for the duration of a transfer. It is never used for tracking or any other purpose.
  • Protected & temporary: Each sharing session is guarded by a random, single-use code embedded in the QR code and is shut down as soon as you finish.
  • No new data collection: We do not collect, log, or receive any information about which books you share or receive.

Opening Files From Other Apps

You can open supported documents (PDF, EPUB, Word, and more) from other apps, such as your file manager, email, or a messaging app, directly into ReadingKulture. When you do, the file is copied into the App's private local storage on your device and, on Android, its original file name is read so your book keeps a meaningful title. This all happens on-device; the file is not sent to us.

Third-Party Services

Our App uses the following third-party services:

  • Google Sign-In: Used by your device to authenticate directly with Google, so the App can sync to your own Google Drive. We do not use it to verify your identity to us, and we receive no sign-in data on any server. Google Privacy Policy
  • Google Drive API: For cloud storage and sync functionality. Google Privacy Policy
  • Firebase Analytics: For anonymous usage analytics. Firebase Privacy Policy
  • Google Gemini AI: For AI-powered book summaries (optional feature). Requests are anonymous and content is not retained. Google AI Terms
  • Project Gutenberg, Open Library, Internet Archive: For free book discovery and downloads. Each service has its own privacy policy.

Your Rights and Choices

You have the following rights regarding your data:

  • Access: You can view all data stored in the App at any time.
  • Deletion: You can delete your local data by uninstalling the App or clearing app data from your device settings.
  • Google Data: You can revoke the App's access to your Google account through your Google Account settings.
  • Analytics Opt-Out: You can disable analytics by adjusting your device's privacy settings.

Children's Privacy

Our App is not intended for children under 13 years of age. We do not knowingly collect personal information from children under 13. If you are a parent or guardian and believe your child has provided us with personal information, please contact us so we can take appropriate action.

Changes to This Privacy Policy

We may update this Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page and updating the "Last updated" date. You are advised to review this Privacy Policy periodically for any changes.

Contact Us

If you have any questions about this Privacy Policy or our data practices, please contact us: