RReadia

Privacy Policy

Last updated: 31 July 2026

Readia is made by Lumio Studio. This policy explains what the app does with your data, in plain language. It describes what we actually do — not what we might one day do.

The short version

1. Who we are

Readia is developed and operated by Lumio Studio. The app's identifier on the App Store is co.lumiostudio.readia. If you have a question about anything on this page, email contact@lumiostudio.co.

2. Anonymous by default, sign-in only if you need it

Readia has no sign-up screen and no password. When you first open the app it signs in anonymously using Firebase Authentication. That gives your device a random identifier (a "user ID") so our servers can tell one request from another and store your audio in the right place. On its own, that identifier is not linked to your name, your email, your phone number, or your Apple Account.

There is one situation where that is not enough. An anonymous identifier only exists inside a single app install — delete the app and it is gone for good. So if you buy a subscription on the web (see section 8) and want it to survive a reinstall or follow you to a new iPhone, you need something we can recognise you by. That is what Sign in with Apple is for.

What signing in with Apple stores

When you sign in, Apple gives us a stable identifier for you and — unless you choose Hide My Email — your Apple Account email address. If you do choose Hide My Email, we receive Apple's private relay address instead and never see your real one. Both are held in Firebase Authentication and used for exactly two things: to keep your account yours across reinstalls, and to match a web payment to the right person.

We never ask you to create a password, we do not read your Apple Account name or contacts, and your email is not added to any mailing list — we do not send marketing email at all. Signing in is optional. If you never buy on the web, you never need to do it.

3. What you send us, and what happens to it

Readia only sends something to our servers when you ask it to convert something into audio. Here is exactly what happens to each type:

A photo of a book cover

The photo is sent to our server and passed to Google Vertex AI (Gemini), which identifies the book from the cover. The identified title is then used to generate a spoken summary. We do not use your photos for anything else, and we do not use them to train any AI model.

A PDF you import

The file is sent to our server, where its text is extracted. The PDF file itself is not kept after the request finishes. The extracted text is used to produce the narration.

A web link you paste

Our server fetches that page and pulls out the readable text. The link and the extracted text are used to produce the narration.

Turning text into speech

The text is sent to a text-to-speech provider to be spoken aloud. Depending on availability, that provider is Fish Audio, ElevenLabs, or Google Cloud Text-to-Speech. All three act as processors on our behalf and receive only the text to be narrated — never your identity.

4. Where your audio is stored

The narration we generate is saved as an MP3 file in Firebase Storage, filed under your anonymous user ID, so playback is instant when you return to an item. Each file is reachable only through a long, unguessable link. The files are not listed publicly and are not indexed by search engines.

5. Your library stays on your device

The list of what you've saved — titles, items, and how far through each one you are — is stored only on your iPhone, in a file inside the app's own storage. It is not synced to our servers, it is not backed up to us, and we cannot see it.

6. Analytics and crash reports

To understand which features get used and to find bugs, Readia collects:

This matches the app's privacy manifest, which declares email address, user ID, photos, other user content and purchase history for app functionality, plus product interaction data for analytics and crash data for app functionality — and sets tracking to false across every one of them.

This website

The pages on readia-lumio.web.app use PostHog too, in the same project as the app, so we can see whether the site actually helps people find Readia. On the web we record page views, the language of the page you are on, and clicks on links and buttons — nothing you type, and nothing that identifies you. To count a repeat visit as the same visit rather than a new one, PostHog stores a random id in your browser (a first-party cookie and local storage). It is not used for advertising and it is not shared with anyone.

If your browser sends Do Not Track or Global Privacy Control, we load nothing at all — no analytics script, no cookie, no events. Session recording and automatic click capture are switched off for everybody.

7. Tracking: we don't

Readia's privacy manifest sets tracking to false, and the app lives up to it:

8. Subscriptions and payment

There are two ways to pay for Readia, and they involve different companies. In neither case does Readia ever see your card number. Adapty is the common piece: whichever route you take, it is what tells the app that an active subscription exists so the right content unlocks.

Buying inside the app

The purchase goes through Apple. Apple takes the payment and holds your billing details, and passes the transaction to Adapty, filed under your user ID.

Buying on the web (Russia)

Apple's in-app purchases are not available to everyone. For customers in Russia we offer a web checkout handled by lava.top, a payment provider operating in that market. If you use it:

9. Who processes data for us

ProviderWhat it does
Google FirebaseAnonymous sign-in, Sign in with Apple, audio file storage, crash reporting, analytics
AppleSign in with Apple — gives us a stable identifier and, unless you hide it, your Apple Account email
Google Vertex AI (Gemini)Identifies books from cover photos; generates summary text
Fish AudioText-to-speech narration
ElevenLabsText-to-speech narration
Google Cloud Text-to-SpeechText-to-speech narration
PostHogProduct analytics, in the app and on this website
AdaptySubscription management — receives your user ID and your subscription status
ApplePayment processing and billing for purchases made inside the app
lava.topPayment processing and billing for the web checkout offered in Russia — receives your email address and your card details, which we never see

Our servers run in Google Cloud in the United States (region us-central1). If you use Readia from outside the US, your requests are processed there.

10. How long we keep things

11. Deleting your data

One thing deletion does not do: it does not cancel a subscription. An Apple subscription is cancelled through Apple (see the Terms), and a lava.top subscription through lava.top. Delete the account first and you may keep being charged for a subscription you can no longer use, so cancel first.

12. Children

Readia is not directed at children under 13, and we do not knowingly collect personal information from them. If you believe a child has provided us with personal information, email contact@lumiostudio.co and we will delete it.

13. Your rights

Depending on where you live, you may have the right to access, correct, or delete your personal data, or to object to how it's processed. Email contact@lumiostudio.co and we will help. If you have never signed in, the practical scope of such a request is limited to what sits under your anonymous ID, because that is genuinely all we hold — we cannot look you up by name or email if we do not have one.

14. Security

Traffic between the app and our servers is encrypted in transit. Access to stored audio requires an unguessable link. Our API keys for the AI and speech providers live only on the server — they are never included in the app you download.

15. Changes to this policy

If we change how Readia handles data, we'll update this page and change the "last updated" date at the top. Material changes will be reflected here before they take effect in the app.

16. Contact

Lumio Studio — contact@lumiostudio.co