Cookie policy
We use cookies and similar storage technologies to run The Session website. Optional storage stays off until you agree. Rejecting optional storage does not prevent browsing, booking tickets, or applying to perform.
Your choices
Choose “Reject optional”, “Accept optional”, or select individual features in Cookie settings. You can withdraw consent using Cookie settings in the footer. Withdrawing consent deletes the remembered ticket email and removes our offline cache for any features you switch off. Previous processing is not undone.
Necessary storage
- Sign-in session: the first-party
__Host-thesession_sessioncookie keeps studio users signed in securely for up to 12 hours. It is set when signing in and removed when signing out. - Purchased tickets: after booking, a first-party
thesession_ticket_cookie verifies access to your latest order for that event in this browser for up to 30 days. It is HttpOnly and contains a signed checkout reference, not your name or email. Clearing it removes browser access; your emailed ticket remains available. - Consent choice: the first-party
thesession_cookie_consentcookie stores the chosen features, time of choice, and policy version for up to 180 days. It contains no advertising identifier. It is only saved after you make a choice. - Ordinary browser caching: your browser may cache images, fonts, and other static files to load the website. This is separate from the optional offline cache.
Optional features
- Remember ticket email: if enabled, the first-party local-storage item
ticket-checkout-emailholds the email entered at checkout so a ticket-support form can be prefilled. It is removed when you withdraw consent, when expired consent is detected on a subsequent visit, or when you clear site data. Consent is valid for at most 180 days. - Offline assets: if enabled, our service worker saves public site files in browser caches whose names begin
the-session-pwa-. This does not cache checkout, studio, or private ticket pages. Caches are replaced on site updates and removed when you switch the feature off, your consent expires on a subsequent visit, or you clear site data.
Visitor counting
To count how many people visit, our own server combines your IP address and browser type with a random key that changes every day and keeps only the resulting code. The key is deleted when the day ends, so the code cannot be traced back to you or linked with other days. We also count how often each page address is opened, as daily totals that are not linked to visitors. No cookies or other storage on your device are used, nothing is shared with analytics providers, and signed-in studio users are not counted.
We also keep separate aggregate counts for referring website domains, the site domain and language used, broad browser and device categories, and the hour and day of the week. Referring domains come from ordinary page requests; full referring addresses, their query strings, and raw browser headers are not saved in these counts. These totals are not linked to visitor codes, customer details, or individual browsing histories. Our server also records aggregate request outcomes and response times to help us maintain the service. This uses no additional cookies or device storage.
Third-party services
The website does not load advertising trackers or third-party analytics. Social links are ordinary links; opening one takes you to that provider’s website. If a paid booking uses Stripe, you are directed to Stripe’s checkout after choosing to buy tickets. Stripe then applies its own cookies and privacy practices on its service.
You can also clear or block cookies and site storage in your browser. Blocking necessary session cookies prevents studio sign-in. If your browser cannot save your preference, you may be asked again on your next visit.