Cookie policy
This page explains what is stored in your browser when you use BagEvent, and separates two different things: this website, and the application you sign in to.
This website
Nothing here is stored on your device until you choose it. When you first arrive we ask one question, and until you answer it we load no analytics that set cookies.
You can change your answer at any time — the "Cookie settings" link at the bottom of every page reopens the same choice. Withdrawing is as easy as giving.
What you can switch on or off
Analytics — off unless you turn it on. Google Analytics (G-BDV5FCKZVC) sets first-party cookies such as _ga so we can see page views, traffic sources, and device types in aggregate. Google processes this data under its own terms. If you say no, it is never loaded — not loaded in a limited mode, not loaded at all.
What runs either way
A page-view counter that sets no cookie. We use Plausible to count page views. It stores no cookie and no identifier that follows you between visits or between sites: it records the page, the referrer, and a coarse device type, in aggregate. There is nothing to switch off because nothing is stored on your device.
Nothing else. No advertising cookies, no advertising identifier, and no tracking across other companies' sites. Typefaces are served from our own domain, so loading a page here does not contact a font provider.
If you open the chat
The chat in the corner of every page runs on our own support system. Nothing from it loads until you choose Chat here, so it stores nothing on your device if you never open it, whatever you chose above. Once you open it, it stores cw_conversation and cw_user_… so the conversation is still there when you move to another page, and cw_snooze_campaigns_till if you dismiss a pop-up message. These are strictly necessary to provide the chat you asked for, which is why they do not depend on the choice above. Choosing WhatsApp instead stores nothing on this site: it hands you over to WhatsApp.
Where your choice is stored
In your browser's local storage, under bagevent.consent, together with the date you made it — that record is how we can show what was agreed and when. It never leaves your device. Clearing your browser data clears it, and we will ask again.
The application
account.bagevent.io and app.bagevent.io need cookies to work at all. These are strictly necessary and are not part of the choice above, because without them you cannot sign in or complete a purchase.
- Session cookie — keeps you signed in. Expires after 24 hours, or after 30 days if you chose to stay signed in.
- Security token — protects forms against cross-site request forgery. Expires with the session.
- Preferences — remembers choices such as your selected currency during checkout.
Payments
When you pay for a ticket, your payment provider — for example Stripe or PayPal — may set its own cookies to process the transaction and detect fraud. Those cookies are governed by that provider's own policy, not this one.
Event organizer sites
Events published on BagEvent may run under an organizer's own domain. What is described above still applies. If an organizer adds their own tracking to their event site, that is their responsibility and their policy governs it.
Controlling cookies
Besides the choice on this site, you can clear or block cookies in your browser settings. Blocking the strictly necessary cookies described above will prevent you from signing in and from completing a ticket purchase; nothing on this website depends on them.
Contact
Questions: [email protected]. See also our privacy policy.
Last updated: 1 September 2026