Privacy

Your email address. To send your sign-in code and to know which books are yours.

Your Google name and photo. Only if you sign in with Google: we get your name, email and profile photo link. We don’t keep the sign-in tokens Google issues.

Passkeys. If you add one, we keep its public key. The private part never leaves your device.

Your quiz answers and your books. Languages, level, the hero’s name, gender, genre, goal and occupation, and the book written from them. We need them to write, show and continue your book. Your answers reach our server while you take the quiz, so we can read the sample page aloud.

Writing records. For each book we keep what we sent to the AI model and what it wrote back, including your quiz answers and the hero’s name. We use them to continue your book and to fix a broken one. We also note what writing each book cost.

A browser cookie. A random token that ties books you start before signing in to this browser. It lasts 1 year. We keep only a hash of it, not the token. Signing in adds a session cookie.

Your sign-in session. Keeps you signed in for up to 60 days after your last visit. Our session records don’t keep your IP address or browser.

Your IP address. To stop abuse. We count every sign-in request per IP address, and the counter holds the address as is. We also count audio requests per IP address for one minute; that counter isn’t stored with us. When you start a book, we keep only a keyed hash of your address, never the address itself.

Sign-in code records. When a code is requested or entered wrong, we note the email and the time. This limits how many codes one email can get.

An audio log. Each time we make audio, and some of the times audio is played: when, how many characters and which voice. The book is noted only when we pay to make new audio. We use it to keep audio costs in budget.

These stay in your browser’s storage: saved words, your practice history, reading progress, which words you tap and which paragraphs you read, how many words you know, your theme and audio speed. We don’t receive them. Clearing this site’s data in your browser removes them. When you listen, your browser asks our server for that sentence or word.

Sign-in sessions. Up to 60 days after your last visit, and signing out deletes it. An expired session is deleted within about 15 minutes.

Sign-in codes. Expire after 5 minutes. The code itself is stored only as a hash, next to your email. An expired code is deleted within about 15 minutes.

Sign-in code records. Deleted within about 15 minutes of turning 1 day old. Records for an email that never signed in follow the same rule.

IP address counters. Deleted within about 15 minutes once your last sign-in request is 10 minutes old.

Hashed addresses of book starts. Deleted within about 15 minutes of turning 1 day old. The book’s own record keeps its hash while the book exists.

Books in your account. Until you delete your account, with their quiz answers and writing records.

Books you start without signing in. Deleted 30 days after you last open them in the browser where you started them. Their quiz answers and writing records go with them. Signing in before then moves them to your account. A book that is still being written waits until it’s done.

The audio log. A record of audio being played is deleted within about 15 minutes of turning 90 days old. A record of audio we pay to make is kept with no end date. It names no account, and once you delete yours, the books it names are gone.

Backups. Our database keeps 30 days of restore history. Weekly backups are deleted after 84 days. Deleted data can remain in them until then. Weekly backups leave out sign-in sessions, sign-in codes, IP address counters and sign-in code records.

Hosting logs. Technical request logs are kept for 7 days. They include your IP address and the addresses of pages and audio you request, along with other request details such as the language of your sign-in email. The address of sample audio carries your quiz answers and the hero’s name.

Cloudflare. Hosts the site, the database and the files, and runs the bot check when you start a book or ask for a sign-in code.

Google. Only for Google sign-in. The Google button loads from Google when the sign-in form opens.

Cloudflare (Email Service). Sends your sign-in code, in your language if this browser knows it from your quiz or profile. It gets your email and the code. We don’t store the language. Like any detail of a request, it can reach the hosting logs for 7 days. Cloudflare keeps the recipient address in its sending log for up to 30 days.

Microsoft Azure AI Speech. Turns text into audio. It gets only the text being read aloud, which can include the hero’s name. It never gets your email.

The AI model provider. Anthropic (Claude), or OpenRouter when we send requests through it. It gets your quiz answers, including the hero’s name, to write the book. It never gets your email.

A server we rent to write books. When we use one. It gets your quiz answers and the book, like the AI model provider.

Open the menu, then Settings. At the bottom, choose Delete account and confirm by signing in again. Right away we delete your books and their writing records. We also delete your account with its sign-in methods, passkeys and sessions, and the sign-in code records for your email. If a book is still being written, wait until it’s done.

What stays: what writing each book cost, without any link to you; the audio log; backups, until they expire; hosting logs for 7 days. Audio made from your book’s text stays too. It is stored by the text itself and isn’t linked to you.

Books you started without signing in belong to this browser. To delete them now, sign in here first: they move to your account. Then delete the account. Or leave them: they’re deleted 30 days after you last open them.

Questions about your data, or a request to see or delete it: hello@novel.you. The rules for using novel.you are in the terms.