Privacy policy
[REVIEW] are open questions). The Spanish version is the reference one.Last updated: [REVIEW: publication date]
1. Summary
- Without an account, ReadersNook does not send your data to any server of ours: your library lives on your phone.
- An account is optional (Google or Apple only) and is used for reading circles, notifications and the cloud copy.
- There are no ads, no third-party analytics and no sale of data.
- You can export your data and delete your account from the app.
2. Controller
MandarinaStudio, Spain (individual developer) [REVIEW: full name or company name, tax ID and address for notices]. Contact: privacy@readersnook.app (privacy and rights) and support@readersnook.app (help).
3. What data we process and why
3.1. Without an account (data stays on your phone)
Books, shelves, notes, reading sessions, goals and settings are stored on your device. We do not receive them. When you search for a book, the query (the search text or ISBN) goes through our own intermediary server to Google Books to return results; it carries no identity or identifier of yours.
3.2. With an account (optional)
| Data | Purpose | Legal basis (GDPR) |
|---|---|---|
| Account identifier and email provided by Google or Apple at sign-in | Authenticate you and keep your session | Performance of the service you request (Art. 6(1)(b)) |
| Profile: alias, avatar and year of birth (self-declared age, 16 or over) | Show you in reading circles and check the age requirement | Performance of the service (6(1)(b)) and duty to restrict access by minors [REVIEW] |
| Reading circles: membership and role, reading progress you choose to share, threads, comments, proposals, votes, blocks and invitations | Provide the reading circles | Performance of the service (6(1)(b)) |
| Reports and moderation log | Keep the community safe and handle abuse | Legitimate interest (6(1)(f)) |
| Library copies (a compressed file with your books and reading data) and an identifier for each device | Restore your library on another phone | Performance of the service (6(1)(b)) |
| Device notification token and per-circle notification preferences | Send you notifications from your circles (new book, poll, replies, daily digest) | Your consent when you grant the notification permission (6(1)(a)); you can withdraw it at any time |
| Plus subscription status (app user identifier, no payment data) | Recognise your purchase across your devices | Performance of the contract (6(1)(b)) |
Push notifications contain only identifiers, the notification type and, for replies, the alias of the person replying. They never include comment text or titles; your phone composes the notification text in your language.
3.3. What we do not do
We use no cookies or third-party analytics in the app or on this website. We show no ads. We do not build profiles or make automated decisions. We never ask for a password (sign-in is handled by Google or Apple).
4. Processors and third parties
| Who | What it does | Data |
|---|---|---|
| Supabase (database and storage; EU region, Frankfurt) | Account, reading circles and library copies | Those in section 3.2 |
| Google and Apple | Sign-in (the only methods) | What you authorise on their sign-in screen; we receive identifier and email |
| Expo (Expo Push service) with Apple and Google (FCM/APNs) as carriers | Notification delivery | Device token, identifiers and, for replies, the replier’s alias |
| RevenueCat | Plus subscription management | App user identifier and purchase status |
| Google Books (through our intermediary server) | Book search | Only the search text or ISBN; no personal data |
| Google Play / App Store | Distribution and payment | Governed by their own policies |
Each provider acts under its own data processing agreement or terms [REVIEW: confirm the DPAs with Supabase, Expo and RevenueCat].
5. International transfers
Our database and files are in the EU. Expo, RevenueCat, Google and Apple may process data outside the European Economic Area, notably in the USA; in those cases we rely on the safeguards they offer (adequacy decisions such as the EU-US Data Privacy Framework, and standard contractual clauses) [REVIEW: check each provider’s current certification or clauses].
6. How long we keep data
- Account and reading circles: as long as you have the account. Deleting it removes your profile, memberships, progress, votes, blocks, notification tokens, invitations and cloud copies. Your comments remain as “[eliminado]” with no author, so conversations are not broken.
- Reports: the copy of the reported text is deleted 90 days after the report is resolved; the whole report, 12 months after it is resolved (or created, if never resolved).
- Moderation log: 12 months, with no alias or comment text after the account is deleted.
- Inactive circles: a circle with no activity for 24 months is warned and deleted [REVIEW: confirm this applies in the published version].
- Provider technical backups: may keep deleted data for a limited time [REVIEW: Supabase period].
7. Your rights
You may exercise your rights of access, rectification, erasure, objection, restriction and portability, and withdraw consent.
- Access and portability: in the app, Settings → Account → “Export my data” (a JSON file with your data).
- Rectification: you can edit your alias (once every 30 days) and avatar in the app.
- Erasure: Settings → Account → “Delete account” (see how to delete your account).
- Notifications: turn them off in the app settings or in your system settings.
- Any other request: write to privacy@readersnook.app. We will reply within one month at most.
If you think we have mishandled your data, you can complain to the Spanish Data Protection Agency (aepd.es) or to your local authority.
8. Minors
Account features (reading circles, notifications and cloud copy) are only for people aged 16 or over, based on the age you declare at the start (we store only the year of birth). This is not a document check. Without an account, the app works on your phone without sending us anything. If we find an account belonging to someone under 16, we will delete it. If you are a parent or guardian and think this has happened, write to us.
9. Security
Access to data is restricted by per-user rules in the database; connections are encrypted; library copies are kept in private storage reachable only from your account. No system is infallible: if a breach affected you, we would tell you as the law requires.
10. Changes
If we change this policy in a significant way, we will tell you in the app and update the date above.