This page lists every cookie and similar technology (local and session storage) used when you browse The Change Experience 2026 or register — what each does, how long it lasts, and how to control it.
We use three kinds: essential storage that makes registration and sign-in work, measurement storage that tells us which campaigns bring attendees, and analytics storage that shows how the site is used. Blocking essential storage stops registration from completing; blocking the rest only stops measurement, and the site keeps working.
Essential — registration and sign-in
- change_session (up to 30 days, HttpOnly). An encrypted cookie that keeps your registration progress and sign-in on this device. It holds your sign-in token, an opaque registration session reference, and the phone number you are verifying while you wait for an SMS code. Without it registration cannot complete. It is never used for advertising and cannot be read by scripts on the page.
- convoy-registration draft (24 hours). Stored in your browser, not sent to us by itself. It remembers which registration session to resume if you close the tab and come back, and is deleted once it expires or you clear your browser storage.
- Campaign status cache. Short-lived cached copy of whether registration is open, full or on a waitlist, so the header does not reload it on every page view.
Marketing measurement — Meta
- _fbp (about 90 days) and _fbc (click ID). First-party cookies set by the Meta Pixel to recognise a browser across visits so we can measure which announcements lead to registrations. We read them, and forward them to Meta unchanged, so browser and server events match.
- Conversions API (server-side, not a cookie). When you complete key steps — registering, verifying your phone, completing your profile, receiving a ticket, or accepting an invite — our server sends Meta a matching event. It contains identifiers hashed with SHA-256 (email, phone, name, date of birth and similar), the browser click identifiers, your IP address and browser type, and a shared event ID so browser and server events are deduplicated rather than double-counted. Advanced matching on the registration form also passes your phone number to Meta directly in the browser.
- Campaign attribution (up to 12 months). A random identifier plus the first and last campaign touch you arrived with — ad click identifiers, UTM parameters, referral or invite code and the referring site. It is stored so that if you register today and finish next week, the registration is still credited to the announcement that brought you in. It contains no contact details of its own.
Analytics — Microsoft Clarity
- Clarity identifiers (up to 13 months). Pseudonymous session analytics that show how pages are used (taps, scrolls, rage clicks) so we can fix broken flows. Clarity does not run on ticket, pass, login or ticket-recovery screens. Invite and referral parameters are removed from the address before it loads. We do not combine Clarity recordings with anything you type into a form.
Maps & Places — Google
The area field on the registration form uses Google Places autocomplete, which loads Google’s components and may set Google’s own cookies under Google’s cookie policy. It is loaded only when that field is used. Venue directions are an ordinary link that opens Google Maps in a new tab — no map is embedded on this site.
Managing cookies and storage
You can clear or block cookies and site storage in your browser settings at any time. Blocking the essential session cookie will prevent registration from completing; blocking marketing and analytics storage only stops measurement. Ad and tracker blockers may also prevent the Pixel or Clarity from loading — the site keeps working either way. Use the in-product entry in your browser settings for a per-site reset.
You can also avoid marketing measurement cookies entirely by not clicking our ads, and you can control how Meta uses data about you in Meta’s Ads Preferences.
Contact
Questions — reach us at [email protected].
