Cookies

Every cookie this site sets

This is the complete list — not the highlights. It is generated from the same list the application itself is held to, so a cookie that is not on this page is a cookie the site is not allowed to set.

Only the first is set on the live service. The second exists when a developer runs the app on their own machine with no mail server attached, so that the sign-in link can be shown on screen instead of emailed; you will never be given it.

Why you have not been asked to accept anything

UK law lets a site set a cookie without asking when the cookie is strictly necessary for a service the visitor has asked for — and requires it to ask for anything else. Everything above is in the first category: without the session cookie the site cannot tell your packs from somebody else’s, which is not a preference, it is the service.

So there is no banner, and that is not an oversight or a thing we have not got round to. A consent banner exists to collect permission for the cookies in the second category, and there are none. Putting one up anyway would ask you to click something that changes nothing, and train you to click the next one without reading it.

What is deliberately not here

No advertising cookies, no analytics cookies, and no cookie that follows you to another site. No Google Analytics, no Facebook pixel, no session recorder, no heatmap, no A/B testing tool, no chat widget, no embedded font service — no third-party script of any kind runs on any page of this site, which is a stronger statement than the cookie list, because a script that loads from somebody else’s server can see you whether or not it sets a cookie.

Nothing on any page writes a cookie from your browser either: every cookie above is set by the server, in response to something you did. That is why the list can be complete, and it is checked by a test rather than remembered by a person.

We do count some things, because a service nobody can see is a service nobody can fix — how many packs were built, how many failed, whether the tip link was followed. Those counts are written on our own server, they are not cookies, they carry no account, no address and no cookie, and they are described in the privacy notice.

Blocking or clearing them

Your browser can block or delete cookies for this site, and we do not try to detect it or work around it. It is worth knowing what happens if you do: without the session cookie there is no way to sign in, and no way to be shown the packs you built — the site will keep offering to sign you in and nothing will stick.

During the guest period, before you have given us an email address, that cookie is the only thing tying you to your work. Clearing it loses those packs permanently, and because we have no address for you we cannot give them back — we would have no way to tell it was you. Registering is what fixes that, and it is the only reason we suggest it.

Deleting the cookie does not delete the account behind it. If you want that gone too, use “Delete everything” on your children’s page first, which removes the rows and the files as well; a guest account nobody comes back to is deleted on its own in the end.

If this list ever changes

The date at the top is the date this page last changed. A new cookie means a new row here before it is set rather than after, and if one is ever added that is not strictly necessary, this page will say so and you will be asked first — which is the point at which a banner would stop being a thing we are glad to be without.

The privacy notice at /legal/privacy covers everything else that is held about you, how long it lives, and the two buttons that get you a copy of it or delete it.