Privacy policy
Luz is a digital reading app published by Boris PADONOU. This page describes the data the app and its API actually handle.
Who is responsible
The publisher of Luz (Android package app.luz.reader) is Boris PADONOU. Questions about your data: hello@luzapp.site.
Google account
Sign-in uses Google through Firebase Authentication (profile and e-mail scopes). Luz receives the display name, the e-mail address, the Firebase uid, and the profile photo URL.
Only the uid is written into the Luz database, with the dates the account was created and last seen. The name, e-mail, and photo stay with Firebase Authentication and are shown in the app. They are not copied into that database.
On a web checkout, the e-mail claim of the ID token is sent to Stripe or FedaPay as the customer e-mail. It is not stored in the orders table.
Purchases and orders
Each purchase attempt stores the book, the amount, the currency, the status, the channel, the provider, and the provider’s payment references (checkout session, transaction id, or Google Play purchase token).
Builds installed from Google Play are charged only through Google Play Billing. Play receives an obfuscated account id (a hash of the internal user id), not your e-mail. Stripe (card) and FedaPay (mobile money) are used only for web distribution and builds distributed outside the stores.
A refund confirmed by the provider removes access to that book. The order row stays.
Reading
To keep your place across devices, Luz stores the current position and the furthest position (chapter and progress), bookmarks, highlights, and notes (the excerpt and the text you wrote), and reading sessions (duration, chapters, device id).
Devices and notifications
Up to five devices can be registered for offline reading (id, name, platform). Push tokens (Expo, FCM, or APNs), the platform, the language, and the time zone are stored so Luz can deliver the notifications you turn on.
Purchase and service notices may use push by default. Promotional pushes stay off until you opt in. That choice and its date are stored with the account, as is the in-app inbox.
Feedback
You can send a message (catalogue error, bug, or question). Luz stores the kind, the message (2,000 characters at most), a contact e-mail only if you type one, the book, and — from the reader — the chapter and the position, plus the app version, the platform, and the interface language. The Firebase uid is attached only when the token is valid. The IP address is not stored.
Searches with no result
A search that matches nothing stores the normalised terms (letters and digits), the catalogue language filter, a result count of zero, and the time. There is no uid and no IP address. Rows older than 90 days are deleted.
Web account-deletion requests
The form on the account-deletion page stores the account e-mail and an optional reason. The IP address is not stored. A hidden field that humans leave empty is used to drop spam; a filled field is not saved.
On the device
The phone keeps the Firebase session, the library, reading progress, bookmarks, notes, search history, and downloaded chapters (the chapter files are encrypted). Appearance and reader settings stay on the device and are not tied to the account on the server.
Deleting the account clears the local library and, when the session ends, the downloaded chapters.
What Luz does not do
Luz does not show advertising and does not sell, rent, or trade your data. There is no advertising SDK and no separate analytics SDK.
Processors
- Google Firebase Authentication, for the Google account.
- Google Play, for payments in the app installed from Google Play.
- Stripe and FedaPay, for payments on web distribution.
- Cloudflare, for the API, the D1 database, R2 files, and rate limiting. The IP address is a rate-limit key only and is not stored.
- Expo, to deliver push notifications to FCM and APNs.
How long data is kept
- Account, reading rights, progress, bookmarks, highlights, notes, sessions, devices, push tokens, notification preferences, and the inbox: for the life of the account. Deleting the account in the app removes them at once.
- Orders and payment events: kept after deletion, detached from the account, for accounting and legal duties. The code does not set a shorter period.
- Feedback already sent: kept so the message can be handled. It is not deleted automatically with the account.
- Searches with no result: 90 days.
- Web deletion requests: kept as a record of the request. The account data itself is deleted within 30 days of the request.
Your rights
Where the GDPR applies (readers in the European Economic Area), you can ask for access, rectification, erasure, restriction, and portability, and you can object to a processing. You can turn promotional notifications off in the app. You can lodge a complaint with the supervisory authority of your country.
To use these rights: delete the account in the app (Profile, then Delete my account), write to hello@luzapp.site, or use the account-deletion form.
Applicable law
Processing of data about readers in the European Economic Area is subject to Regulation (EU) 2016/679 (GDPR) and to the mandatory rules of the reader’s country. Otherwise, the applicable law is that of the publisher’s place of establishment, Boris PADONOU.