How We Use Cookies: Essential, Analytics & More
A plain-language explanation of the cookies that run on this site, why they exist, and how you stay in control.
Last updated: 12 June 2024
About Cookies
A cookie is a small text file a website asks your browser to store. The next time you visit, that file gets handed back, which lets the site remember things like whether you dismissed a banner or what you set in your preferences.
Most cookies do dull, useful work. They keep a page from forgetting who you are between clicks.
There are two lifetimes worth knowing about. A session cookie lives only as long as your browser tab is open and disappears the moment you close it. A persistent cookie stays on your device for a set period — days, months, sometimes longer — until it expires or you clear it yourself. The difference matters because it tells you how long a given piece of information sticks around.
Cookies We Use
We try to keep this short. The cookies on this site fall into three groups, and only one of them is running right now.
Essential cookies
These make the site function. They remember your cookie consent choice so the banner does not nag you on every page, and they handle the basic plumbing that keeps pages loading the way they should. You cannot switch these off and still use the site normally, because the site relies on them to work.
Analytics cookies
When enabled, these tell us how the site is performing in aggregate — which pages people read, where loading slows down, how visitors move between sections. We use that picture to fix rough edges and prioritize the content people actually want. The data is about patterns, not individuals.
Advertising cookies
We do not serve personalized advertising today. We are noting this category because we may use advertising cookies in the future to support the campaign and tailor content. If that changes, we will update this page and ask for your consent where required before any such cookie is set.
Third-Party Cookies
Some cookies come from services we rely on rather than from us directly. We want to be honest about which ones are active and which are planned.
Our content is delivered through a content delivery network (CDN), which speeds up loading by serving files from servers closer to you. A CDN may set cookies to balance traffic and protect against abuse. That is the main third-party presence on the site at the moment.
Analytics providers and advertising networks would also fall into this category. Both are future implementations, not current ones. Should we add an analytics provider or an advertising network, we will name it here and describe what its cookies do before they go live.
Controlling Cookies
You hold the final say. Every major browser lets you block cookies, delete the ones already stored, or set a warning before any new cookie is accepted. The controls live in the privacy or security settings of Chrome, Firefox, Safari, and Edge, and the wording differs slightly from one to the next.
Be aware of the trade-off. If you block essential cookies, parts of the site may stop behaving correctly — the consent banner, for one, will reappear on every visit because we have no way to remember that you answered it. Turning off analytics cookies costs you nothing on your end; it simply means your visit will not show up in our performance data.
A practical note: clearing cookies also signs you out of other sites and resets their preferences, not just ours. If you only want to adjust this site, most browsers let you manage cookies per domain.
You can read how we handle personal information more broadly in our Privacy Policy.
Policy Changes
This policy was last revised on 12 June 2024. We expect it to change as the site grows, particularly if we introduce analytics or advertising cookies that are not active today.
When we make a meaningful update, we will revise the date at the top of this page and, where the change affects how we collect or use cookie data, surface a fresh consent prompt so you can review your choices. This page describes our current practice and our stated intentions; it does not promise that every future tool we adopt will behave identically, which is why we commit to updating it rather than treating it as final.
Questions about any of this are welcome — reach us through the Contact page.
