Cookies and storage
familyeventsindex.co.uk — last updated 25 October 2026
This site uses one cookie, and only if you were sent a beta invitation.
The one cookie
swipe_session is set when you sign in with your link. It holds a random session token and nothing else — not your email, not your name, and nothing that means anything to anyone reading it. It is Secure, HttpOnly and SameSite=Lax.
It signs you in for 90 days from your last visit, and the cookie itself lasts 180. Opening the Hub restarts the 90 days, so if you use it at all you will not be signed out. Leave it alone for 90 days and the sign-in ends.
The second 90 days sign you into nothing. The cookie stays only so that, if you come back after your sign-in has run out, we can show you a page explaining what happened and how to get a new link — rather than the "page not found" that everyone else gets. Signing in again replaces it; signing out deletes it.
Signing out ends it at both ends: the cookie goes, and the session stops working on our side as well, so a copy of it is no use to anybody.
It does nothing but keep you signed in to something you asked to join, which makes it strictly necessary — and strictly necessary cookies do not require consent.
If you have never been sent a beta link, no cookie is ever set.
What your browser keeps
| Where | What |
|---|---|
| The index | Postcode locations already looked up, if you use the distance filter. Nothing else — not your searches, not your filters |
/swipe | Nothing. |
/swipe stores nothing in your browser. Your saved and binned events, the events you added yourself, your profile, your term dates, your filters and which view you were last on all live on your account, encrypted. They are fetched when you open the page and held only while it is open.
Your profile can include your children's first names and ages. Those are held the same way — encrypted, filed against an identifier that is not your name or email. The privacy notice says more.
This is why signing out takes nothing with it: there is nothing to take. It is also why a shared tablet cannot show the next person your list, and why the page needs a connection to work at all.
If you turn notifications on
Your browser holds a push subscription for this site: an address at Google (on Android and in Chrome) or Apple (on an iPhone or iPad) that points at this browser, and two keys. The keys encrypt each notification, so the company relaying it cannot read what it says.
We keep a copy of that address and those keys, encrypted, because it is the only way to send to you. It says nothing about you and nothing about what you have saved.
It is per device and off by default. The switch is under More, and the browser asks you as well — both have to say yes. Turning it off, signing out, deleting the app or clearing this site in your browser each remove it.
On an iPhone or iPad this only works from the copy you added to your home screen. Apple does not offer notifications to a website in a Safari tab, so in a tab there is no switch to find.
The app also caches two fonts and four small pictures so that it opens quickly. That cache holds nothing about you and is cleared when you sign out.
What opening a page asks of others
| Who | When | What they see |
|---|---|---|
| Cloudflare | Always — they deliver the site | Your IP address |
| postcodes.io | Only with the distance filter | The postcode you typed |
| OpenStreetMap, cdnjs | Only when you open the map | Your IP address |
Links out to Google Maps or an organiser's booking page are ordinary links — nothing is sent until you follow one.
Questions
jack@familyeventsindex.co.uk — or see the privacy notice for what we hold and why.