Skip to content
bagevent.io

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 unless you answer yes we load nothing that sets cookies — no analytics and no chat.

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

One switch covers two things. Both are off unless you turn them on, and if you say no neither is loaded — not loaded in a limited mode, not loaded at all.

Analytics. 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.

Chat. The chat in the corner runs on HubSpot Conversations. HubSpot's script sets cookies such as hubspotutk, __hstc, and __hssc, which recognise a returning visitor, and messagesUtk, which keeps the conversation when you change page. HubSpot processes this data under its own terms. If you say no there is no chat on this site; the contact page works without it. If you switch it off later, the chat is removed and HubSpot is asked to delete its cookies.

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.

A count of sign-up button clicks. When you press a sign-up button we count the click — which page it was on and which button — without storing anything on your device and without an identifier.

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.

Forms

When you send a demo request or one of the download forms, what you typed is sent to HubSpot, where we read it. That happens only when you press send, and sets no cookie.

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, app.bagevent.io, and event sites keep you signed in with your browser's storage, not cookies. This is strictly necessary and is not part of the choice above, because without it you cannot sign in or complete a purchase.

  • Sign-in session — two tokens held in your browser's local storage keep you signed in. The session lasts 24 hours, or 30 days if you chose to stay signed in. Signing out removes them.
  • Working state — small items in your browser's session or local storage, such as which organization you are working in, an order you have started, the link you arrived through, and your answer to an organizer's analytics question on an event site. The application also records which set-up steps were reached — opening the sign-up page, creating an event, publishing it — and never what you typed: once you are signed in this is tied to your account, and before that to a random id kept in the tab's session storage, which is gone when you close the tab.
  • A cookie during Google sign-in only — if you choose Continue with Google, a cookie named bagevent_google_nonce ties that sign-in to your browser. Scripts cannot read it, and it expires after 15 minutes.
  • A cookie that remembers where you are signed in — a cookie named be_si lists which bagevent sites (for example app.bagevent.io) hold a sign-in in this browser, so the sign-in page can send you straight there instead of asking for your password again. It contains site names only, no token and nothing that identifies you, it is not sent to or read by any other company, and it lasts up to 30 days. Signing out of a site removes that site from it.

Support chat. In the organizer console the HubSpot chat is loaded only when you open it from the help menu. From then on HubSpot sets its own cookies, as described above.

Payments

When you pay for a ticket, the payment provider — Stripe — 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 run at a bagevent.io address, and an organizer can embed registration in their own website. What is described above still applies. If an organizer adds their own analytics to their event site, the page asks you first by default and loads nothing from those services unless you accept; that tracking is the organizer's responsibility and their policy governs it. A venue map or a video on an event site is loaded from Google Maps, YouTube, or Vimeo, which may set their own cookies.

Controlling cookies

Besides the choice on this site, you can clear or block cookies in your browser settings. Blocking the browser storage described above will prevent you from signing in and from completing a ticket purchase; nothing on this website depends on it.

Contact

Questions: milo@bagevent.io. See also our privacy policy.

Last updated: 6 October 2026