Cookies policy
Wavecast sets one cookie once you sign in, and one more for the few minutes a Google sign-in takes. There is no banner because there is nothing to ask about.
Last updated 27 September 2026
The session cookie
Signing in sets one cookie holding a session identifier, so the next page knows who you are. It is strictly necessary for an account to work at all, it is not readable by script, and it goes when you sign out or when the session lapses. There is no cookie at all for somebody who has not signed in.
While signing in with Google
Pressing Continue with Google sets a short-lived cookie holding a random value and the page to come back to, so that the answer Google sends back can be checked as the one this browser asked for. It is not readable by script, and it is cleared as soon as the sign-in finishes or lapses within minutes.
What there is not
No analytics, no advertising, no tracking pixels, no third-party cookies, and nothing that follows you to another site. Wavecast measures nothing about you.
What your browser keeps for itself
Some things are kept in your own browser’s storage rather than in a cookie: your preferences (the language, the clock, how dates read, the Studio switches, reduced motion, whether rooms start with sounds on, and that you have put away the alpha notice); the name you go by and, for each room you join, who you were in it and a token that lets a reload skip the PIN; the running orders you save, or that are kept for you, on the saved agendas shelf; and, for one tab only, whether sounds are on. None of it is sent anywhere except the preferences, which are kept on your account when you are signed in so they follow you to another machine. Clearing your browser’s site data clears all of it.
Questions about any of this, a request about your data, or a notice about something somebody uploaded can go to william@wo.dev.