Cookie Policy

FoM is operated by E-Events VZW, BE0871.628.142, Professor Scharpelaan 90, 3130 Betekom, Belgium. Contact [email protected] about privacy or [email protected] about the website.

You can accept optional tracking, reject it or choose analytics and marketing separately. Optional tracking starts only after the relevant choice. Browsing, buying a ticket or accepting our terms is not cookie consent. Rejecting optional tracking leaves the shop, accounts and competitions available.

Open Cookie settings in the footer to change your choices. Necessary storage supports services you ask for, such as sign-in and your cart. It is not used as a reason to turn on advertising.

Cookies are small values a website can store in your browser. We also use local storage, which can survive a browser restart, and session storage, which is normally cleared when the browser tab's session ends. The same choice about optional purposes applies to these technologies, not just to files called cookies.

First-party storage belongs to the FoM website you are visiting. A separate sign-in or payment provider can store information when you visit its service. That provider's notice explains its storage. Our Privacy Policy covers the associated personal data, recipients and your rights.

These entries support requested services and remembering your choices. They are scoped to the FoM origin in your browser. The consent cookie uses the root path, so the preference works throughout the site.

• fom.consent: a first-party cookie recording your necessary, analytics and marketing choices, policy version and choice time. Maximum lifetime: 180 days. Clearing it or changing the policy version can cause the banner to ask again.
• fom.storefront.auth-token: local storage used to keep you signed in. It is replaced at sign-in and removed at sign-out or when you clear this site's browser data. Local storage does not have its own automatic expiry; the server separately limits the token's validity and revokes it when your account is closed. Closing the account cannot erase local storage from every device. Removing this entry signs this browser out.
• fom.storefront.guest-cart: local storage containing selected product identifiers, quantities and cart information. It is cleared when the cart is cleared or successfully merged into your account. The current cart storage has no automatic time limit; you can remove it by clearing the cart or this site's browser data.
• fom.storefront.merge.*: local storage used to recover an interrupted cart merge without adding the same items twice. Entries are removed after a completed merge or cleanup. An interrupted entry can remain until that happens or you clear site data.
• fom.storefront.pending-auth-redirect: session storage remembering the page to return to after sign-in. It is removed when read, or ends with the browser session.
• fom.checkout.*: session storage used to recover an interrupted checkout and avoid duplicate orders. It contains a checkout retry key and, when available, an order reference. It is removed during the relevant completed checkout flow or ends with the session. A payment-return entry also holds an order reference and expiry so we can check the payment result on a clean page address. It is valid for five minutes; expired entries are removed when read or when the tab session ends. It does not store payment details or the payment status.
• fom_oauth_binding: a necessary cookie on the FoM API host, scoped to /api/v1/auth/social. It links a requested Google or Discord sign-in to the browser that started it and expires after 10 minutes.

Some API-hosted actions, such as confirming or cancelling a newsletter subscription, also use a server session and a request-security cookie to protect the form. These are separate from advertising cookies. Their names and expiry depend on the service configuration; the default server session is two hours. Social-login and payment providers use their own storage on their domains when you request those services.

Server-side cart, order and account records are different from browser storage. Deleting browser storage does not cancel a paid order or erase records that FoM needs to retain.

With analytics consent, measurement can record public page views and selected shop actions, including a verified purchase. Google Tag Manager delivers the configured tags; Google Analytics 4 processes analytics events. These tools are not needed to buy tickets. Analytics measurement is enabled only after you give analytics consent.

The FoM purchase-measurement entry fom.analytics.purchases is optional local storage. It remembers pseudonymous transaction references to avoid counting the same paid order repeatedly in this browser. Entries are considered for up to 30 days, with a maximum of 200 stored references. Entries are pruned when purchase measurement runs; withdrawing analytics consent or clearing this site's browser data removes the stored list sooner. This is not a copy of your ticket or invoice.

With analytics consent, fom.analytics.auth-outcomes is optional session storage used to count a successful sign-in or account creation after you return to a public page. It holds at most two short records containing the action, the sign-in method (email, Google, Discord or social sign-in) and a timestamp. It does not contain your name, email address, account ID or page address. Records are valid for five minutes and are removed when used; expired records are removed when read or when the tab session ends. Withdrawing analytics consent removes them immediately.

Campaign labels are used only after consent and held in page memory rather than a separate persistent campaign cookie. Private account details, form text, authentication secrets and ticket barcodes are not intended for analytics events. A transaction reference is pseudonymous, not anonymous.

GA4 can use first-party cookies such as _ga and _ga_* after analytics consent. The configured GA cookie lifetime is at most 180 days and is not refreshed on each visit. GA4 retains event-level data for 2 months and user-level data for 14 months; the user-level retention period resets on new activity. These settings do not describe the retention of aggregated reports. They are separate from the 30-day FoM purchase-measurement entry.

Marketing consent is separate from analytics consent. Advertising tags, when enabled, can measure ad-driven visits or purchases and support FoM remarketing audiences. Planned advertising services include Google Ads, Meta, X and TikTok. A service must be configured for its stated purpose and respect your marketing choice before its tag is activated.

Advertising tags are not currently enabled on the new site. Before enabling a provider, we will name its cookies, explain their purpose and lifetime, and ask for the relevant consent. Customer-list uploads, enhanced conversions and session replay are not enabled merely by accepting the site's terms or by making a purchase.

External providers describe their own technologies and processing in Google's privacy information, Meta's privacy policy, X's privacy policy and TikTok's privacy policy. Their websites can process information independently when you visit them.

The venue map loads automatically using OpenFreeMap. Loading the map shares connection information such as your IP address with the map provider. Google Maps embeds on other pages load only when you choose to load them. You can also use the written venue information and directions link to plan your journey.

Choosing Google or Discord sign-in, or proceeding to a Mollie payment page, takes you into the requested provider flow. Those providers may use storage necessary for that service under their own notices. A request to sign in or pay is not consent to FoM advertising cookies.

Use Cookie settings in the footer to withdraw analytics or marketing consent. The website updates the relevant signals, removes recognised first-party tracking cookies where possible and reloads when needed to stop an already loaded tag. Withdrawal prevents future optional use; it does not reverse information already processed lawfully.

You can also use your browser's site-data controls to delete cookies, local storage and session storage for the FoM site. This may sign you out or clear an unpaid guest cart. Storage on a provider's own domain must be managed there or through your browser; FoM cannot directly delete another website's cookies. Some browsers restore session data when restoring tabs.

Rejecting optional tracking is enough to keep using FoM. You do not need to lower your browser's privacy settings or disable tracking protection.

Optional tracking relies on consent. Necessary storage supports the services you request and our legitimate interest in operating them securely. For access, correction, deletion, objections, complaints and information about international processing, see our Privacy Policy or contact [email protected].

This version is dated 1 November 2026. We review the inventory when services or tracking purposes change. A new optional purpose that requires consent must be explained before it starts.