Cookie Policy.

A cookie is a small file your browser stores on behalf of a website. Modern browsers also expose local storage and session storage, which are similar. Throughout this policy “cookie” means any of these.

These cookies are required for Jamrats to function and cannot be disabled without breaking core flows. You cannot opt out of them inside Jamrats; you can still block them in your browser, but signing in and checking out will stop working.

• __session — Sign-in session cookie, set when you log in.
• __client_uat — Anti-replay token used to invalidate stale sign-in sessions.
• cf_clearance — Cloudflare bot challenge token. Set when you pass the Turnstile verification at checkout.

Functional cookies remember non-essential preferences such as which dashboard view you last used.

• jamrats_pref — last-selected event filter in the dashboard. Local-storage only.

We use Vercel Web Analytics to count page views and understand which features are used. It is cookieless — no identifiers are written to your browser, no cross-site tracking, no sharing with ad networks. Visitor counts are deduplicated with a daily-rotating hash of the request IP and user-agent that is discarded after the count is taken.

When you load an event page, the embedded checkout form provided by our payment processor sets its own cookies on the processor’s domain to manage payment security. Those cookies are scoped to the payment processor and governed by their cookie policy.

Most browsers let you delete or block cookies in settings. Blocking the strictly-necessary cookies above will break sign-in and checkout.

If you want a record of what we have on file for you, file a data-subject request via hello@jamrats.com.