Cookies

Lumind uses a small number of items stored on your device. Some are necessary for the site to work and are always on; everything else is optional and stays off until you say yes. This page explains both, and lets you change your choice at any time.

Always on — necessary

Not cookies, technically — this is stored in your browser’s local storage — but it’s the same category of “information on your device,” so we’re covering it here too. These aren’t optional: without them, basic features like staying signed in don’t work.

lumind_token — keeps you signed in. Set when you log in, removed when you log out.

lumind_onboarding — temporarily holds your answers while you’re completing sign-up, so you don’t lose progress if you navigate away mid-form. Cleared once sign-up finishes.

lumind_saved_events — a leftover from when events could be saved without an account. Saved events now live on your account; anything still stored here is moved across the next time you sign in, then deleted.

lumind_cookie_consent — remembers the choice you make below, so we don’t ask again on every visit.

None of this is used to track you across other sites, build an advertising profile, or shared with any third party. It’s the functional equivalent of a website remembering what’s in your shopping cart — necessary for the feature you asked for, nothing more.

Optional — only with your consent

We use Google Tag Manager to run analytics on Lumind, so we can see how the site is used and improve it. Nothing in this section is active until you choose — every tag starts denied (via Google’s Consent Mode) until you accept it, and you can change your mind at any time using the button below.

  • Analytics — helps us see how Lumind is used, so we can improve it.
  • Marketing — ad measurement and personalization, if we run campaigns.
  • Personalization — tailors event recommendations to your interests. This one doesn’t involve Google at all; it’s used on our side only.

Google Sign-In

If you sign in with Google, you’re briefly sent to Google’s own domain to complete that step. Google sets its own cookies there, governed by Google’s own policies — we don’t control or receive that data.

Last updated: July 2026