Privacy

What this document covers

Read for Me is a mobile app made by Great Lair. This privacy policy describes what data the app handles, what we send to which third parties, what we keep, and what we don't.

Identity and accounts

There are no user accounts in Read for Me. We don't ask for your name, email, phone number, age, or any other identifying information. We don't issue you a customer ID. We don't sign you in to anything. The first screen of the app is "what would you like to read" — not "create an account."

For paid subscriptions (when launched), purchase identity is managed by Apple's App Store or Google Play, not by us. We receive a receipt from the store to verify entitlement; that receipt does not contain your personal details.

What's stored on your phone

The following lives in your phone's local app storage and never leaves the device unless YOU choose to share a book with someone:

• Your reading preferences: voice, speed, language, theme.
• Your library of books and pages — including the recognized text, any translations, and the synthesized voice audio.
• Your recent reads (the "Read anything" history list).
• Your monthly credit usage counter.

Photos of pages are not persisted. When you take a photo of a page for a book, the image is sent for text recognition and then discarded. For one-off "Read anything" captures, the photo is kept locally as a visual cue in the recents list so you can identify the entry — and is removed when you delete that entry. Either way, the image never reaches our servers in a way we keep.

What we send to third parties — and what they keep

Google Cloud (text recognition + translation)

When you photograph a page, the image is sent to Google's Gemini API to extract the printed text. When you ask for a translation, the extracted text is sent again to Gemini for translation. Google processes these requests under its standard API terms and — per Google's published policy for paid API tier — does not use your inputs to train their models. Google may retain the request in their logs for a short period for abuse prevention; we do not control that retention window.

OpenAI (voice synthesis)

When you tap play on a page, the text to be read aloud is sent to OpenAI's text-to-speech API. OpenAI generates the spoken audio and returns it to us. OpenAI's published policy for API customers states that API inputs and outputs are not used to train their models and are retained for a maximum of 30 days for abuse monitoring, after which they're deleted.

Cloudflare (network edge + audio chunk hosting)

The bridge between your phone and the AI services above is a small server (a Cloudflare Worker) that lives at our edge. Generated audio chunks are temporarily stored in Cloudflare R2 storage and served back to your phone via signed URLs that expire after one hour. We don't index those audio files by user — they're stored under random keys and are unreachable once the signed URL expires. Cloudflare retains operational logs (request timing, response codes, byte counts) for diagnostics; those logs do not contain the text you photographed or the audio that was spoken.

Apple / Google (in-app purchases)

If you subscribe to a paid tier, the payment is handled entirely by Apple's App Store or Google Play, under their own terms and privacy policies. We receive a purchase receipt to verify your subscription status. We don't see your payment method, your billing address, or your name as it appears on your card.

What we don't do

• We don't have analytics tracking that follows you across apps or websites.
• We don't share your data with advertisers.
• We don't sell your data, ever.
• We don't build a profile of what you read. We literally couldn't — your library is stored on your phone and we never see its contents in a form we keep.

Sharing books with other people

When you choose to share a book with someone via the secret-code flow, the book's encrypted contents (text + audio) are uploaded to our server for the recipient to download. The encryption key is part of the share code itself — we never see the unencrypted book on our end. Shared books expire and are deleted from our server after 7 days regardless of whether they were claimed.

Children

Read for Me is not directed at children under 13. We don't knowingly collect any data from children. The app has no accounts, comments, social features, or messaging that could expose a child to other users.

Your rights and choices

Because your data lives on your phone and not on our servers, you control it directly:

• To delete a book, page, or recent read: delete it inside the app — it's gone immediately.
• To delete everything: uninstall the app. iOS and Android wipe all app data when you do.
• To opt out of all third-party processing: don't capture pages. The app cannot read text without the text recognition service, and cannot generate speech without the speech service. There is an offline reading mode using your phone's built-in capabilities (no network calls), available when you're out of monthly credits or when you choose it.

Changes to this policy

If we change how the app handles data, we'll update this page and change the "last updated" date at the top. If a change is material — for example, if we ever decided to add accounts or server-side history (we don't plan to) — we'd surface it in the app itself before it took effect.

How to reach us

Questions about this policy, or about how Read for Me handles anything not covered here: write to [email protected]. A real person will reply.