Privacy

The sentence you type, the titles and outline you approve, the book that gets written, and the cover you pick. An email address only if you make an account.

You can write a whole book without an account. In that case we hold a session identifier in a cookie and nothing that identifies you personally.

Google runs the models that write the chapters and draw the covers, so your sentence and the text produced from it pass through their API. Google Cloud also hosts the site and stores the books.

Inngest queues the generation job and therefore sees the identifiers attached to it, not the prose. Stripe handles payment — we never see your card.

Langfuse records model calls so we can see what a run cost and where it failed. Sentry records errors. Neither is used for advertising.

We do not sell your data, we do not use your books to train models, and we do not share them with anyone not listed here.

The cookie that keeps you signed in is required for the site to work and cannot be turned off.

Product analytics are not switched on at the time of writing. When they are, visitors in the EU and UK will be asked before anything loads, rather than being opted in by arriving.

Your books stay until you delete them or ask us to close your account. Error and model-call records are kept for a short operational window and are not tied to your identity beyond the account that produced them.

Ask, and we delete the account and every book in it. There is no retention period we hold you to and nothing to fill in.

A support address is published in the footer of every page once it is live. This draft predates it.