Cookie Policy
Draft — not yet reviewed
Draft. This describes how the site currently works, and is a starting point rather than a finished policy. Please have it reviewed by someone qualified before relying on it, particularly once ticketing and payments go live.
The short version
We ask you once, when you arrive, and we honour the answer. Only the things needed to make the site work are on by default; everything else waits for your permission.
We do not currently run any advertising or analytics at all. The marketing choice is recorded now so that nothing can start later without an answer already on file.
Signing in is the exception. If you sign in to a directory listing or to the organisers’ portal, one cookie is set so that the site knows it is still you on the next page. It is strictly necessary for signing in, so it does not need consent, and it is the only cookie this site sets.
Your choices
- Strictly necessary — always on. Keeping you signed in, and remembering the choice you make about this. The site cannot work without these, so the law does not require consent for them and we cannot switch them off.
- Marketing — off unless you turn it on. Measuring whether our posts and adverts bring people here, and showing you our adverts elsewhere. Nothing of this kind runs today.
Refusing is one button, exactly as prominent as accepting. You can change your mind at any time:
Your answer is kept in your own browser, not on our server, and is asked again if we ever add a new purpose.
The sign-in cookie
- What it holds — a signed session reference. Not your password, and nothing about what you do on the site.
- How long it lasts — 30 days for a directory listing, 14 days for the organisers’ portal, or until you sign out, whichever comes first. Signing out deletes it.
- Who can read it — this site only. It is marked HttpOnly, so scripts in your browser cannot read it, and SameSite, so other sites cannot trigger its use.
Payments
Card payments are handled by Stripe on Stripe’s own pages. Stripe sets its own cookies there, necessary to process the payment securely and to detect fraud. Those are covered by Stripe’s policies rather than this one.
Local storage
Your browser may remember which pages you have visited as part of normal browsing. That is handled by your browser, not by us, and we cannot read it.
What might change
If we ever add analytics, we will ask for your consent first and update this page.