Privacy policy
Last updated: 6 October 2026
KeenRead helps you learn and practise book ideas. This policy describes the iPhone app and this website. For privacy questions or requests, contact the KeenRead team at keenread.app@gmail.com.
Your account and progress
The app creates an anonymous account with a random identifier when it can reach the KeenRead server. You can use the local app before that connection succeeds. Your profile, reading progress, answers, notes, practice history, settings and a previous local backup are saved on your device. Account records are synchronised with our server to preserve progress and support connected devices. An anonymous account is still an account; it is associated with identifiers rather than a required email or password.
If you choose Sign in with Apple, we use the verified Apple account identifier to link or recover your KeenRead account. The current sign-in flow does not request your name or email from Apple. A name you enter in the KeenRead profile is saved with your account. We do not receive your Apple password. Linking to an existing account may merge your saved records.
Notifications
If you enable reminders and grant notification permission, the app registers an Apple push token, the installation identifier, notification environment and interface language with our server. We use these to deliver notifications to the right device through Apple Push Notification service. Push tokens are excluded from analytics events and diary sync. Disabling reminders removes the server registration when the app can connect; account deletion also removes its push registrations and delivery attempts. You can manage notification permission in iOS Settings.
Optional AI features
With your permission, AI coaching or assessment sends the text you choose to submit, the necessary lesson or selected-book context, and language information through the KeenRead server to OpenAI. Your name and entire journal are not automatically included. Text you enter can itself contain personal information. Do not submit information you do not want the model provider to process.
KeenRead does not keep a server history of raw AI requests or responses. A practice step or answer you choose to save becomes your account data. OpenAI processes requests under its applicable API data policies; see OpenAI’s privacy policy and API data controls. AI features may be unavailable while the service is being prepared or disabled.
Subscriptions
Apple processes purchases and payment details. RevenueCat receives purchase receipts, subscription status, product and transaction information, and a KeenRead billing identifier to manage access and restoration. We use server-verified subscription information to confirm premium access. We do not receive your card details.
RevenueCat can send subscription lifecycle events to our Amplitude and PostHog projects using the corresponding account identifier. These events help us reconcile the purchase journey with app usage. See RevenueCat’s privacy policy.
Analytics and diagnostics
We use Firebase Analytics and Crashlytics, Amplitude, and PostHog to understand app usage, reliability and subscription flows. Data can include a random user or device identifier, app version, device and operating-system information, language, lesson identifiers, event times, completion or error codes, purchase status, and technical diagnostic data. Providers may process network metadata, such as an IP address, when receiving requests.
Our app events exclude names, journal text, submitted AI text, raw responses, passwords and server credentials. We do not enable session replay or automatic screen/text capture. Technical AI metrics include feature, duration, status and token-use metadata, rather than prompts or generated text. Advertising storage and personalisation consent are disabled in the app’s Firebase configuration; we do not access the advertising identifier or use these events to track you across other companies’ apps and websites.
Provider policies: Google, Amplitude, PostHog. This public website uses no analytics scripts, advertising trackers, account forms or cookies. Our hosting service processes ordinary network requests and operational logs to deliver and protect the site and API.
Retention and deletion
Account records stay in the active KeenRead database until you delete the account or request their removal. In Profile, you can delete the account and remove local records and backups from this device. Other connected devices lose access to the deleted account and offer to remove their local records. We keep an irreversible hash of the deleted installation’s random identifier to prevent old records returning to the cloud.
Encrypted or access-controlled server backup copies are rotated and normally expire within 14 days. Copies you export, or device backups managed by Apple, remain under your control. Operational and third-party analytics records follow their configured retention periods; contact us to request access, correction or deletion of identifiable records. Apple and RevenueCat may retain purchase records under their own policies. Deleting a KeenRead account does not cancel an App Store subscription.
Security and your choices
Connections to the KeenRead API use HTTPS. Server credentials are kept outside the app and source repository. Account access and administrative actions require authentication. No system guarantees absolute security. You can export a backup in Profile, decline optional AI processing, manage reminder permission in iOS Settings, and manage subscriptions through Apple.
Service providers may process information outside your country. Depending on where you live, you may have rights to access, correct, delete or restrict use of personal data. Contact us with your request; do not send passwords, payment credentials or your private journal by email. We do not sell personal data.
Updates
We may update this policy as the service changes. The date above identifies the current version. Material changes will also be explained in the app where appropriate.