Your reading is personal.

Updated 28 September 2026. Aivoy LTD provides Leaflect and is responsible for the personal information described here. Contact matt@aivoy.io with privacy questions.

Your journal and account

Without signing in, books, saved passages, reading progress, favourites and reflections stay in the app’s local storage. If you sign in, Firebase Authentication processes your account identifier and the name and email supplied by Apple or Google. Your journal is then saved in Cloud Firestore through our Render backend and cached on your device. Importing an existing local journal into an account is an explicit choice. We do not provide end-to-end encryption. Google’s sign-in component may also process Google account details (including a phone number where present), country information, device identifiers and sign-in usage data under Google’s policies.

Photographs and book lookup

Page and cover text recognition runs on your iPhone with Apple Vision. We do not upload photographs for recognition. Images may remain in temporary device storage until removed by the app or operating system. To find a book, a title, author or ISBN query is sent through Render to Open Library. Catalogue results may be cached. Cover images load from catalogue providers, which receive network information such as your IP address. Save only passages you have the right to use.

Optional AI and OpenAI

Ask Leaflect uses OpenAI GPT-5.6 Terra. Before using it, you choose your age band and country and explicitly agree to sharing text. We send your question, the selected saved passages and associated book metadata, and a limited recent conversation context to OpenAI. We do not send photographs, your full journal, your account email or your name as AI input. Questions and answers are checked using OpenAI’s moderation service.

OpenAI API data is not used to train its models by default. We request no persistent Responses API storage, but this is not zero data retention: OpenAI may retain abuse-monitoring information under its policies, normally for up to 30 days unless longer retention is required. See OpenAI’s data controls. Do not include sensitive information about yourself or another person in AI requests.

Our backend stores generated answers, cited passage identifiers, request hashes and usage counters to deliver answers, prevent duplicate charges and enforce limits. AI responses can be incorrect and are based on the selected passages, not the full book. You can report an answer from the app. Sending a report opens your email app so you choose what to send.

Subscriptions and diagnostics

Apple processes payments. RevenueCat processes an anonymous or signed-in app account identifier, purchase and transaction details, subscription status, and device/app information to provide and restore access. Purchase and paywall interaction metrics also help us understand subscription performance. We do not receive your full payment-card details. Firebase Crashlytics processes crash traces, installation identifiers and device/app diagnostic information. Firebase, RevenueCat, Render and our catalogue providers may also process IP addresses and operational logs. We avoid including journal text, credentials and request bodies in our service logs.

We do not sell your personal information or use advertising tracking SDKs. We do not use your private writing to target advertising.

Why we process information

We use information to provide the features you request, sync your journal, validate subscriptions, secure the service and answer support requests. Where data-protection laws require a legal basis, these purposes rely on performing our agreement with you, legitimate interests in security and service reliability, legal obligations, and consent for optional AI sharing where required.

Retention and deletion

Local writing remains until you clear it or remove the app. Cloud journal data, cached AI responses and usage records are retained while your account is active. In Settings you can export your journal, turn off future AI sharing, or delete your account. Turning off AI sharing stops future requests; it does not undo processing already performed. Account deletion removes your cloud journal, AI request records and Firebase sign-in account and sends a deletion request to RevenueCat. If a provider is temporarily unavailable, the deletion is queued and retried automatically. Minimal deletion status and security records may remain to prevent data from reappearing. Apple and providers may retain records they must keep for legal, financial or security reasons. Device backups are controlled by your device and backup settings.

Deleting an account or the app does not cancel an Apple subscription. Cancel it separately in Apple subscription settings. Export writing you wish to keep before deletion.

Age and regional eligibility

The on-device journal is available to all ages. Account sync requires you to meet the applicable local age for consent to this service, with parental permission where required. AI requires age 13 or older and the applicable local minimum age for digital consent, parental permission for users under 18, and a supported country or region. AI is unavailable for younger users and in regions OpenAI does not support. The App Store age rating describes content and does not replace these eligibility requirements. Please contact us about a child’s information so we can investigate and remove it where appropriate.

International processing and your rights

Our service providers operate internationally, including in the United States and Europe. Processing may occur outside your country. Applicable provider contracts include data-protection safeguards for relevant transfers. Depending on your location, you can request access, correction, deletion or a copy of your data, object to or restrict processing, and withdraw consent without affecting earlier lawful processing. Contact matt@aivoy.io. You may also complain to your local data-protection authority; in the UK this is the Information Commissioner’s Office.

Changes

We will update the date above when this notice changes and provide an in-app notice or renewed consent when a material change requires it.