Legal

Cookie notice

One essential sign-in cookie, one localStorage key for an unfinished brief, and Meta Pixel measurement on public pages while ads run. No analytics suite.

Updated September 15, 2026

Quick answer

The site sets one cookie of its own, and only after you sign in: an HttpOnly session cookie that tells the server which account is asking, so your books open without a password. It is not set on a visit, it is not shared with anyone, and it expires after thirty days or when you sign out. While we advertise on Facebook and Instagram, the public pages and the /start/ funnel also load the Meta Pixel, which sets Meta's own cookies to measure whether an ad led to a sign-up or a purchase; the studio where you write never loads it.

01

The session cookie

Name: `account`. Set when you open a sign-in link, HttpOnly (no script on the page can read it), SameSite=Lax, Secure on the live site, expires after thirty days. It holds a random session id, not your email address. Signing out deletes it; so does the browser when it expires. Without it the site works fully as a visitor — the free tools, the guides and the funnel need no cookie.

02

What is kept in the browser instead

The /start/ funnel keeps your answers in localStorage under one key (`ebookgen:start`) so a closed tab does not lose the brief; it is on this device only, never sent anywhere by itself, and cleared when the outline is made or when you choose "Start a new one". Your books themselves are not kept in the browser: they are saved to your account so they open on another device.

03

The Meta Pixel

Set by Meta Platforms, only on the public pages and the /start/ funnel, and only while an advertising campaign of ours is running. Cookies: `_fbp` (a browser id, 90 days) and, when you arrive from a Meta ad, `_fbc` (the click id, 90 days). What it reports to Meta: the page viewed, and three events from the funnel — an outline requested, a checkout opened, a payment completed, with the plan price. It does not receive your brief, your chapters or your books. Meta may match these events to a Facebook or Instagram account you are signed into; how Meta uses that is set out in its own data policy, and you can turn off ad measurement in your Meta ad settings. The studio itself (/app/) never loads the pixel. If you would rather not be measured at all, a content blocker that stops connect.facebook.net does exactly that and the site works unchanged.

04

What is not here

No analytics suite, no A/B testing cookies, no consent banner. We advertise only in the United States, where no banner is required; if we ever advertise where one is, the banner comes before the pixel does.

Common questions

Straight answers

Do I need to accept cookies?+

No, and the site does not ask. The one cookie of our own is strictly necessary for sign-in and is set only by the act of signing in; the Meta Pixel is measurement, not a condition of anything.

Can I use the site with cookies blocked?+

Everything except signing in. The tools, the guides and the funnel up to the email step need no cookie; opening a sign-in link needs the browser to accept the one session cookie. Blocking Meta's cookies changes nothing you can see.

Continue

The next useful question