Privacy Policy

How your reading, your library, and your identity are stored, used, and protected.

Effective April 23, 2026

The short version: we store what you bring us — your books, your answers, your portrait — and we use it only to draw your Reading Portrait and to connect you with readers you choose. We never sell it. You can export your library or delete everything at any time from your Account page — and email us anytime for a full copy of what we hold.

1. Who we are

Reading Portrait is a reading app that composes a private literary portrait from the books on your shelves. For the purposes of the UK GDPR and EU GDPR, the data controller is the Reading Portrait team. You can reach us at [email protected].

2. What we collect

Information you give us

Information we generate about you

Information we collect automatically

3. Why we use your data (legal basis)

Under GDPR, we process your data on these grounds:

4. Who we share it with

We share your data with the following service providers, each contractually bound to process it only on our instructions:

We do not sell your data. We do not share your library with other readers unless you explicitly share it (Reading Lists, shared shelves, public reader page, friend-to-friend recommendations).

5. Where your data lives

Your data is stored primarily in the United States (Supabase and Cloudflare regions). When data moves out of the UK / EEA, we rely on Standard Contractual Clauses and supplementary measures approved by the European Commission.

6. Your rights

If you are in the UK, EU, or another jurisdiction with similar rights (California's CCPA, Brazil's LGPD, etc.), you have the right to:

To exercise any of these rights outside the in-app controls, email [email protected].

7. Cookies

We use a single first-party session cookie to keep you signed in. That's it — no analytics or advertising cookies, so there's no cookie banner to click through.

8. Retention

9. Children

Reading Portrait is intended for readers 16 and over. If you believe someone under 16 has signed up, email us and we will delete the account.

10. Security

Passwords are hashed by Supabase using bcrypt. All traffic is TLS-encrypted. Row-level security in our database enforces that only you can read your own books, answers, and portrait.

We're a small beta team. We don't yet hold SOC 2 or ISO 27001 certification; if your organisation requires formal attestation, please reach out.

11. Changes to this policy

If we make material changes, we'll notify you by email and inside the app before they take effect. Non-material changes (typos, clarifications) will be reflected by updating the date at the top.

12. Contact

Questions, requests, or complaints: [email protected].