The small print, in plain words
Cookie policy
Last updated 4 October 2026
Ticket Folk uses only the cookies and browser storage the site needs to work. There are no advertising or analytics cookies, so there’s nothing to accept or reject.
1. Cookies
| Name | What it does | How long |
|---|---|---|
ticket_folk_session | Keeps you signed in, and remembers your basket while you check out. | 120 minutes after you were last active |
XSRF-TOKEN | Proves a form was sent from this site, protecting you against cross-site request forgery. | The same as the one above |
appearance | Remembers whether you chose light or dark mode. Only set if you change it. | One year |
2. Storage in your browser
| What | Why | Where |
|---|---|---|
| Your appearance choice | The same light or dark choice as the cookie, so the page doesn’t flash. | Local storage |
| An unfinished application | Saves what you’ve typed into an application form, so a lost signal doesn’t lose it. Cleared once you send it, or after a fortnight. | Local storage |
| An event you’re setting up | Saves your answers on /start and when you add a new event, so a refresh doesn’t lose them. Cleared once the event is made. | Local storage |
| The guest list for check-in | Only on the phones of gate crew who sign in to check people in, so entry keeps working when the signal drops. Removed 7 days after the event ends. | IndexedDB |
3. Why there’s no cookie banner
UK law (the Privacy and Electronic Communications Regulations) only asks for consent for cookies that aren’t strictly necessary for a service you’ve asked for. Everything above is needed for something you’ve chosen to do, so no consent is needed. We’d rather not track you than ask.
We also honour the Global Privacy Control signal sent by some browsers. Read why on our security and privacy page.
4. Payments and maps
When you pay, you move to Stripe’s checkout page, which sets its own cookies to process your payment and prevent fraud; see Stripe’s cookie policy. Event pages that show a venue map load it from Mapbox.
5. Questions
Email [email protected]. For how we handle personal details more widely, see our privacy notice.