Cookies

It holds a signed token identifying your session and nothing else: no name, no email, no browsing history. It is marked HttpOnly and Secure, so no script on the page can read it. Signing out removes it.

Under the Privacy and Electronic Communications Regulations, consent is required for cookies except those strictly necessary to provide a service you asked for. A cookie that keeps you signed in, after you asked to be signed in, is exactly that exemption. A banner asking permission for it would be theatre.

No Google Analytics. No Tag Manager. No advertising or conversion pixels. No session-recording or heatmaps. No cross-site trackers of any kind, and nothing that follows a studio’s clients anywhere after they have booked their class.

If that ever changes, this page changes first, and anything that is not strictly necessary will be asked about properly rather than assumed.

When a studio takes a card payment, the payment step is handled by Stripe, who set their own cookies to detect fraud on that transaction. That is Stripe acting on their own account and is covered by Stripe’s cookie policy. It only happens when somebody actually pays.

Every browser lets you block or delete cookies. Blocking the sign-in cookie means you cannot stay signed in, so the console will not work, but a client can still browse a studio’s public booking page perfectly well without it.