Privacy Policy

Last updated: 13 September 2026

Quillet ("we", "us") is a reading app for iPad and Android. This policy explains what information the app handles, how it's used, and the third parties it's shared with. We designed Quillet to collect as little as possible: there are no ads, no advertising identifiers, and no third-party analytics or cross-app tracking software in the app.

Information we handle

• Account information. If you choose to sign in, we receive your name and email address from Sign in with Apple or Google. Signing in is optional — Quillet works in an anonymous, device-only mode without an account.
• Content you create. Discussion posts, comments, and reactions you publish are stored on our servers so they can be shown to other readers.
• Identifiers. A random device identifier and, if you sign in, an account identifier, used to attribute your posts and apply usage limits.
• App usage and diagnostics. We record a small set of first-party events such as app and reader opens, chapter indexes, reading session duration, scene-image results, app/OS version, and crash details. These records may include a book's content hash, but never book text, selected text, highlights, notes, or chapter titles.
• Reading data. Your highlights, notes, bookmarks, and reading position. On iPad, this syncs through your own Apple iCloud account (CloudKit private database) — it lives in your iCloud, not on our servers, and we cannot read it. On Android, if you sign in, this data syncs through our backend (Google Firebase) so it carries across your devices; it is removed when you delete your account.
• Connected services. If you connect Hardcover, we store the access token you provide (server-side only) to fetch book metadata on your behalf.
• Independent-author submissions. If you ask us to add your book to the Indie catalog, we store the author name, book title, email address, optional message, and app version you submit so we can review the request and contact you.

How we use it

• To provide the reading, discussion, and AI features.
• To generate AI responses and discussion content (see below).
• To moderate content and enforce fair-use limits.
• To operate, maintain, and secure the service.
• To understand feature use and diagnose app and scene-image failures.
• To review Indie catalog submissions and reply to their authors.

AI features and the services that power them

Quillet's AI companion ("Sage") and its AI-generated discussion content are powered by Google's Gemini API. When you use Sage or trigger AI content, the text involved — your message, any passage you selected, and relevant context from the book you are reading — is sent to Google to generate a response. We do not send your name, email, highlights, or notes to the AI service. Google processes this data as our service provider; see Google's privacy terms for how they handle API data.

AI-generated content can be inaccurate and should not be relied on as professional advice. Some discussion posts are AI-generated and are labelled with an "AI" marker in the app.

Third parties we share data with

• Google Firebase / Google Cloud (Cloud Firestore, Cloud Storage, Cloud Functions) — hosts our backend and stores your posts, the parsed book index, and (on Android) your synced reading data.
• Google Gemini API — generates AI responses and AI discussion content, as described above.
• Apple and Google — provide sign-in; we receive your verified email and name when you choose to sign in.
• Apple iCloud (CloudKit) — on iPad, syncs your highlights, notes, and reading position through your own iCloud account.
• Hardcover — only if you connect it, to fetch book metadata and reviews.

We do not sell your personal information, and we do not use it for advertising or cross-app tracking.

Data retention and deletion

You can delete your account at any time from Account → Delete account in the app. Deleting your account removes your account record, sign-in details, sessions, and any connected-service tokens. Comments you have already published remain in discussions but are de-identified — they are no longer linked to you or your profile. Reading data stored in your iCloud is controlled by you through your Apple ID; reading data synced to our backend on Android and usage events attributed to your account or claimed devices are deleted when you delete your account.

Children

Quillet is not directed to children under 13, and we do not knowingly collect personal information from them.

Security

Data in transit is encrypted (HTTPS). Access tokens and credentials are stored securely server-side and never returned to the app. No method of transmission or storage is perfectly secure, but we take reasonable measures to protect your information.

Your choices

You can use Quillet without an account, delete your account in-app, block other users, and report content. For any privacy request, contact us at the address below.

Changes

We may update this policy from time to time. Material changes will be reflected by the "Last updated" date above.

Contact

Questions about this policy: yuvalheff@gmail.com.