cookies.
The app itself uses only cookies it needs to work — no analytics, no advertising. The one exception is our pre-launch founders page, where a Meta pixel measures whether our ads brought you there; it loads only if you say yes to the banner.
| Cookie | Purpose | Lifetime |
|---|---|---|
authjs.session-token (and CSRF/callback cookies) | Keeps you signed in after the email link | 30 days |
siapp_ref | Remembers a friend's invite link until you finish signing up | 30 days |
siapp_scan | The door's scanner session for one event | Until 12 h after the event |
siapp_consent | Remembers your answer to the cookie banner on the founders page (yes or no) | 1 year |
_fbp, _fbc (Meta) | Meta pixel on /founders only, after consent: tells Meta a visit or pre-registration came from one of our ads. Meta is a joint controller for this measurement; see Meta's data policy. | 90 days |
Local storage
The scanner keeps a copy of the event's ticket list and any scans made offline in the browser's local storage so it keeps working without signal; it syncs and clears when the connection returns. The member app caches pages you have opened (your tickets) for offline use. A per-tab flag stops the device check from running twice.
Device fingerprint
When you use the member app we compute a device fingerprint (browser and hardware characteristics, no cookie). It exists only to spot accounts that share one device and is covered in the privacy notice under fraud prevention.