What we set
| Cookie | Purpose | Duration |
|---|---|---|
sb-<project>-auth-tokenMyEventScape (Supabase Auth) | Keeps you signed in and carries your session between pages. Set when you log in, and split across numbered variants when the session is too large for one cookie. | Session, refreshed on use; cleared on sign-out |
pending_inviteMyEventScape | Holds an invitation token while you finish signing up, so the invite still applies once you have an account. | 30 minutes |
mes_sidebar_collapsedMyEventScape | Remembers whether you collapsed the workspace sidebar, so the server renders the width you chose instead of flashing the other one. | Persistent, until cleared |
The authentication and invitation cookies are set with HttpOnly, SameSite=Lax, and — outside local development — the Secure flag, so they cannot be read by scripts and are not sent along with cross-site requests.
Your controls
Every browser lets you view, block, and delete cookies for a site, and offers a private browsing mode that discards them on exit. Blocking cookies for MyEventScape will sign you out and prevent you from signing back in, because the session cookie is how the platform knows who you are. Blocking cookies does not limit any other part of the service, since nothing else depends on them.
We honor Global Privacy Control signals where they apply, though we have nothing to sell or share in the sense those laws use. Questions about this notice go to privacy@myeventscape.com; the privacy policy covers the wider picture.
Questions about this policy?
Email privacy@myeventscape.com or visit the contact page. Every policy is listed on the legal index.