Cookie Notice

Last updated: October 19, 2026

A cookie is a small file a website keeps in your browser. Klasvo uses only the cookies a website needs to work and to remember your choices. We use no advertising cookies and no analytics on klasvo.com.

1. On klasvo.com

Cookie	What it does	How long
klasvo-currency	Remembers the currency you chose for our prices. Set only if you press the currency switch.	1 year
klasvo_demo	Only for someone who opens a private demo link from Klasvo: keeps you inside your own copy of the demo back office, and keeps others out of it. It ends when the demo ends, 14 days at the longest.	14 days

2. On studios’ websites and apps

A studio’s website and app run on Klasvo, and Klasvo sets these cookies for the studio. The studio decides how its own site is used; its own privacy policy explains it.

Cookie	What it does	How long
__Host-studio_session	Keeps a client signed in to the studio’s website and app. Renewed on each visit; ends when they sign out.	1 year
studio_login_pending	Remembers the email address a sign-in code was sent to, so the code box knows who is typing.	30 minutes
__Host-studio_staff	Keeps a studio’s team member signed in to the back office. Renewed on each visit; ends when they sign out or the owner removes them.	30 days
studio_staff_login_pending	Remembers the email address a team sign-in code was sent to.	30 minutes
studio_locale	Remembers the language chosen on the studio’s website.	1 year
studio_src	Remembers which ad or campaign link first brought a visitor (for example “facebook · paid”), so the studio can see which ads bring bookings. It keeps the label and the page only, never an ad click ID.	90 days
klasvo-demo-stay	On Klasvo’s demo studio only: remembers that you chose to see the demo in US dollars.	90 days
studio_connect_state	Only for a studio owner connecting Stripe: checks that the answer from Stripe belongs to the request they started.	30 minutes
kv_check_in	Only on the tablet a studio sets up at its own door for self check-in: marks that one device as the studio’s check-in tablet, so clients can check themselves in to a class they booked. Never set on a client’s own phone or computer; it stops working when the studio switches the tablet off, and ends after a year.	1 year
studio_consent	Only on a studio’s site that uses a Google tag or Meta Pixel: remembers the visitor’s cookie choice (measuring visits, advertising), so they are not asked on every page, with a random number the studio’s record of that choice is kept under (section 3). Asked again after six months.	183 days

3. Tags a studio can turn on

A studio can add its own Google tag (Google Analytics or Google Ads) or Meta Pixel to its website. They are off unless the studio turns them on. When on, Google or Meta set their own cookies (for example _ga, _gcl_au or _fbp) to measure visits and ads, under their own policies and the studio’s. They are never loaded in the studio’s back office.

Where the law asks for consent first (the European Union and EEA, the United Kingdom and Switzerland, for the visitor or the studio), they load only after the visitor accepts in the cookie bar, and the note of which ad link brought them is kept only then. In the United States they load unless the visitor opts out under “Your Privacy Choices” at the foot of every page, and a browser sending Global Privacy Control is opted out of advertising without asking. Elsewhere a short notice says they are used, with an opt-out. A choice can be changed at any time from the foot of the page.

Each choice is also recorded for the studio, as proof of what was chosen: a random number kept in the visitor’s choice cookie (the record holds only a hash of it), the rule applied, the choices, whether the browser sent Global Privacy Control, the version of the words shown, and the time. No name, IP address or browser is recorded. Records are deleted after 13 months.

Withdrawing a choice also deletes the Google and Meta cookies the studio’s site can reach (_ga, _ga_…, _gid, _gcl_au and the other _gcl_… cookies, _fbp, _fbc), on the site’s address and the domains above it. Cookies that Google or Meta keep on their own domains (for example google.com, doubleclick.net or facebook.com), and what the tags already sent them, are beyond the site’s reach: delete those in your browser’s settings, or ask Google or Meta.

4. Notifications

When a client turns on notifications in a studio’s app, their browser gives us an address for their device at its maker’s push service (Apple, Google, Mozilla or Microsoft), which we store so we can send them notifications. Each notification is encrypted so that only their device can read it. Turning notifications off in the browser stops them.

5. Your choices

You can delete or block cookies in your browser’s settings. If you block the sign-in cookies, you cannot stay signed in. Questions: hello@klasvo.com.