Cookies

Analytics runs on this site, and only for visitors who have accepted it. The question is asked in advance of the measurement it gates, because the answer has to be on record before anything runs.

Nothing on this site tracks you across other websites, and there is no advertising cookie anywhere in it. Saying no costs you nothing: every page works the same either way.

One cookie, and it exists only because you were asked a question. It records your answer so the banner does not ask again on every page. It carries no identifier, so it cannot be used to recognise you.

On anjin.media it is written for the whole domain, so one answer covers this site and the app you sign in to and you are not asked twice. Anywhere else - a preview host, a local build - it stays host-only, because those hosts have no shared domain to write to. It covers every path on the site, and it is not sent with background requests made from other websites.

This is the whole strictly-necessary list for the marketing site. Signing in to the service sets its own session cookies, which are necessary for the same reason a lock needs a key.

This site uses Google Analytics 4, provided by Google Ireland Limited. It loads only after you accept. It measures which pages people read, roughly where in the world they are, what sent them here and what kind of device they used. It does not read anything you type, and it is not connected to your account on the service.

Rejecting is not a preference we note down and honour later. It runs three things immediately:

• Your answer is written. The consent cookie is set to denied for the 6-month period above, and any older copy of it is cleared first so two cookies with the same name cannot disagree.
• The analytics cookies are deleted. Both names Google uses - _ga and its per-property twin - are cleared, in the domain-wide form and the host-only form, because we cannot read back which one was written and a cookie can only be deleted by matching how it was set.
• The page reloads if it has to. Google's tag cannot be cleanly unloaded once it is running, so if it was running when you rejected, the page reloads to stop it. If it was not, nothing visible happens.

There is also a sweep you would never guess at, so here it is. On every page load, for anyone who has not accepted - no answer yet, or a recorded no - this site clears any analytics cookies it finds. That exists for people who picked up a cookie before the banner was built, and for people who simply ignore the bar. It never runs for a visitor who has accepted: deleting a consenting visitor's cookies on every page would be its own kind of dishonesty.

Reopen the banner whenever you like and answer it again. The control is in the footer of every page, and here:

Cookie settings

Accepting later starts measurement from that moment; rejecting later runs the deletion in section 4. Whichever you choose, the answer is recorded in one place, and every control on the site reads it from there rather than keeping its own version of it - so nothing here can tell you one thing while the banner tells you another.

Nothing here overrides your browser. Every current browser can list the cookies a site has set, delete them, and refuse new ones - usually under Privacy, in Settings. Deleting ours has one visible consequence: the consent cookie goes with them, so the banner treats you as a new visitor and asks again.

Blocking cookies outright is fine too. The site is static pages and links; it does not need a cookie to render, and nothing on it is gated behind one.

If this site ever sets a cookie that is not described above, this page changes in the same deploy that sets it, and the date at the top moves with it. That is a standing rule in the repository, not an intention. The wider picture - what the service holds, who processes it and on what basis - is in the privacy notice, and the vendors are named on the sub-processors page.