Cookie Policy

How EventMatch uses browser storage

EventMatch uses cookies and similar browser storage for a small number of defined purposes. Essential storage supports account security and safe preferences. Optional analytics storage is used only after you allow it on the current browser.

EventMatch does not use advertising, behavioral targeting, or marketing cookies.

Essential

Django session and CSRF cookies authenticate your workspace session and protect state-changing requests. They use secure production settings and SameSite protections. EventMatch also keeps your theme and cookie choices in local browser storage. These items are required for security or to remember a choice you made, so they are always active while you use the relevant feature.

Analytics

If you accept optional analytics, Google Analytics may set its standard analytics cookies to distinguish aggregate visits and page categories. EventMatch sends explicit sanitized page views only. It removes query strings, replaces internal record identifiers with generic route templates, and reduces external referrers to their origin.

Google Signals, enhanced measurement, advertising storage, and ad personalization are disabled. Rejecting optional cookies does not limit EventMatch product features.

Luma registration content

When you choose Review & register on a recommended event, EventMatch loads the official Luma checkout in an embedded frame. It is not loaded while you browse recommendations. Luma may use its own essential session storage to show saved details and registration questions. EventMatch does not send checkout responses or purchase events to Google Analytics, and you can use the direct Luma link instead.

Manage your choices

You can accept, reject, or update optional analytics at any time on this browser. Withdrawing consent stops future analytics collection and removes the EventMatch GA cookie names available to the site. You can also clear site data using your browser controls.

Luma Session Companion

If your organization is included in the internal canary and you choose Use existing Chrome session, the Companion extension requests temporary access only to luma.com. After your separate confirmation on the Luma home page, it reads bounded Luma cookies and exact-origin local storage once, encrypts them locally, transfers the encrypted result to EventMatch, clears its in-memory copy, and revokes the temporary permission.

This is credential-equivalent session state, not an EventMatch analytics cookie. It is imported into your organization's protected server-browser profile until you disconnect or replace that connection. EventMatch does not use it for advertising or send it to Google Analytics.