Cookies and local storage

Strictly necessary

These are set regardless of your choice, because the site cannot work without them.

• __session and __client_uat — set by Clerk, our authentication provider. They keep you signed in. Without them you would have to enter a code on every page. Session cookie and one year respectively.
• pf_consent — remembers which button you pressed on the cookie banner, so we do not ask again. A first-party cookie, one year. It has to be a cookie rather than browser storage so our server knows whether to render the banner at all. Ironically, refusing this one would mean being asked forever.

Analytics — only if you accept

If you accept, we store two things and use them to understand which pages are worth writing more of. Both are first-party: they never leave our own systems, and they cannot be used to follow you to any other website.

• pf.sid — a random identifier in sessionStorage that groups your page views into one visit. Deleted the moment you close the tab. Not linked to your identity unless you are signed in.
• pf.attrib — remembers the page you first landed on and where you came from, for 30 days. This is how we find out whether anything we write brings people here.

We do not run Google Analytics, Meta pixels, advertising tags, heatmaps or session recording. There is nothing on this site that reports your behaviour to a third party.

Ours, not yours

• pf_internal — set only when we deliberately visit a special URL, so our own testing does not pollute the statistics. It will never be set on your browser by normal use.

Change your answer

You can also clear site data in your browser at any time, which removes everything above. Signing out clears the Clerk cookies.

More detail

The privacy policy covers what we store on our own servers, which processors are involved, and how long everything is kept.