Privacy

What we store when you browse without a session

An anonymous cookie (vte_anon) that is an opaque identifier. It exists so that your reflections and saved items from before activating your code are not lost: when you activate, that identifier is linked to your account. We don't read this cookie for anything else.

What we store when you activate your code

• Your email, linked to an internal identifier.
• The type of access you have (physical book, premium, etc.).
• A session cookie (vte_user) with your internal identifier. It's HttpOnly: your browser sends it but no script can read it.

What we store when you read

• Your reading progress per chapter (percentage and last position).
• What you mark as saved.
• Your reflections on the book's questions. They are private and only you see them.
• Anonymised events about product usage (which pages are visited, how many times the mentor is opened, etc.). They don't include the content of your reflections or any text you write.

What we do with your email

We use it to identify you on future visits and, with your permission, to send you occasional editorial notes (no spam, no feed). During the beta, we may also use it to contact you if you find an important issue.

What we DON'T do

We don't sell data. We don't share it with advertising networks. We don't load third-party tracking pixels. We don't analyse the content of your reflections.

How to delete your data

Email us at the feedback address shown in My space and we'll delete your account and all associated data. We do this manually during the beta because the cohort is small; when it grows, we'll enable a delete button in My space.

Provisional text · this policy will be reviewed and legally signed before public launch. The practice described reflects the actual behaviour of the code.