Cookie Policy

The one cookie we set

cityfolk_session

• What it does. It is your sign-in. Without it the site cannot tell one person from another, and every page would treat you as a stranger.
• What is inside it. A signed token carrying your user id and nothing else. Not your name, not your email, not your plan, not your role. Everything else about you is read from the database on each request.
• Category. Strictly necessary. It is not optional, because without it there is no signed-in site to use.
• How long it lasts. Seven days, then it expires and you sign in again.
• Its settings. httpOnly — scripts on the page cannot read it. sameSite=lax — it is not sent along with requests started by other sites. secure in production — it only travels over HTTPS. path=/ — it applies across the site.
• Who can read it. Us. It is set by our own domain, it is signed with a key only our server holds, and it is sent to nobody else.

You can delete it in your browser at any time. Doing so signs you out. Blocking it entirely means you cannot sign in at all.

What we do not run

This is the whole list, and it is a list of absences.

• No analytics of any kind — no Google Analytics, no Plausible, no product analytics, no session recording, no heatmaps.
• No advertising or conversion pixels — no Meta pixel, no Google tag, no remarketing, no attribution scripts.
• No third-party embeds pulling scripts, fonts or images from somebody else's server.
• No localStorage or sessionStorage used to identify or follow you.
• No cross-site tracking, no advertising identifiers, no data brokers.
• No IP address logging. Sign-in throttling counts failed attempts against the account in the server's memory, not against your network address — so there is nothing to store.

There is nothing here to opt out of, because there is nothing running.

If we ever add a cookie banner

A banner is only honest when there is a choice behind it. Today there is not: a cookie that is strictly necessary to deliver a service you asked for needs no consent — not under the UK rules (PECR), not under the EU ePrivacy rules, and not under Swiss law. So what you get is a notice, not a consent gate.

If we later add anything optional, we will ask first, nothing optional will load before you answer, and remembering your answer will itself need a cookie:

cityfolk_cookie_consent

• What it does. Remembers what you chose, so we do not ask again on every page.
• What is inside it. Your choice and the date you made it. No identifier, nothing that ties back to you if you are not signed in.
• Category. Strictly necessary / preference. Storing a refusal is not tracking, and it is the only way to honour the refusal.

We will update this page and the effective date at the top before any such cookie is set.

Controlling cookies yourself

Every browser lets you see the cookies a site has set, delete them, and refuse new ones. It is under Privacy or Site settings in Chrome, Safari, Firefox and Edge.

Deleting or blocking cityfolk_session signs you out and keeps you out. Nothing else we set will ever be worth blocking, because there will not be anything else unless you have said yes to it.

Changes

We update this page when what we set changes. The effective date at the top tells you which version you are reading. If we ever add a cookie beyond the two named here, it will be listed here before it is set, and we will email you.