Cookies and storage
LMH Ticketing uses only what’s needed to make the site work, so there’s no cookie banner: no analytics, advertising or tracking cookies.
lmh_session: keeps you signed in if you have an organiser or staff account (ends when you sign out, or after 12 hours; 4 hours on the operator console).
lmh_csrf: a security token that stops other websites making requests as you. Same lifetime as your sign-in.
While you buy tickets, your browser keeps a private link to your order for that tab only, so you can see your tickets straight after paying. It’s cleared when you close the tab.
If you’re door staff, the scanner app keeps the event’s ticket list (ticket codes and whether each has been scanned, with no names or email addresses), a record of the scans made on that phone, and your PIN on the phone, so it works without signal. It’s cleared when you tap End shift, or automatically once the phone’s offline sign-in runs out (after a set number of hours, 18 by default, and never more than 6 hours after the event ends). Scans that haven’t reached the server yet are kept until they upload, then cleared too.
Cloudflare Turnstile may run a quick security check on sign-up, checkout and order help to tell people from bots. Cloudflare doesn’t use it for advertising.
Card payments happen on Stripe’s own checkout pages (checkout.stripe.com), which use their own cookies for fraud prevention under Stripe’s privacy policy.