Cookie and Storage Information

Last updated: October 5, 2026

EventScreen keeps the parts of the site that remember you to a minimum. This page lists what we store in your browser, why, and how to control it. It covers both the EventScreen web platform and the sign-in fallback our apps use in a browser.

1. Our only first-party cookie

We set one first-party cookie, named es_admin_session, but only when you sign in to the organizer backend at /admin. It is strictly necessary: it holds a signed, expiring token that proves your login so you can manage events. It lasts up to 7 days and is cleared when you sign out. Viewers never receive this cookie.

2. Browser storage we use instead of cookies

Viewer sign-in on the web uses your browser’s local storage rather than cookies. We store two small identifiers:

• eventscreen.deviceId identifies this browser install so the sign-in flow can pair it with your account.
• eventscreen.sessionId is the active viewer session, so the platform can recognize your purchases when you watch.

These never leave your browser except to our own servers as part of the sign-in flow, and we clear the session identifier when you sign out. The same job is done by the apps’ native storage on your phone or TV.

The player also keeps two small items for advertising on free events:

• ad-consent records whether you chose tailored or generic ads (see section 3).
• preroll-seen:<event> notes that you already saw the ad for an event, so it is not shown again for about 30 minutes.

3. Third-party cookies and advertising

Payments. When you pay for a ticket you are redirected to Stripe’s hosted checkout. Stripe sets its own cookies on its own domains to run that payment page, and Stripe’s cookie and privacy policies apply there.

Delivery. Our content delivery network (Cloudflare) may set technical cookies needed to deliver the site. These are essential to the service working.

Advertising. Free events can show an ad before the stream starts, and Google serves that ad (Google Ad Manager). On our public pages we also load Google’s AdSense script. Google may set or read cookies and use device identifiers, and collect your IP address and browser details, to deliver and measure ads, to prevent fraud and, only if you allow it, to tailor ads to you. These come from Google’s domains, such as googlesyndication.com, doubleclick.net and imasdk.googleapis.com. We do not currently show display ads on the pages themselves. How Google uses this information is described at policies.google.com/technologies/partner-sites. We do not load Google’s AdSense script on sign-in, account, payment or organizer backend screens. The player loads Google’s ad software only when a free event is about to show a Google ad.

Some free events show an organization’s own ad instead. That ad is served by us, from our own storage, and does not use Google’s advertising cookies.

4. What we do not use

Apart from Google’s advertising technology described above, we do not use advertising cookies or third-party analytics trackers on the platform, and we do not build advertising profiles of our own from your viewing.

5. Consent and your choices

Every cookie and storage item we set ourselves is strictly necessary to the service you asked for, so they need no consent. Advertising is different, and you choose.

• Until you choose, ads on free events are requested as non-personalized: they do not use your past activity to target you.
• A prompt over the player lets you pick Keep generic or Allow tailored ads. Your choice is saved in your browser (the ad-consent item above) and you can change it by clearing site data.
• You can also turn off ad personalization across Google at adssettings.google.com, or opt out of interest-based ads from many companies at aboutads.info/choices.

Our apps do not show Google ads. If we ever add other non-essential cookies, such as analytics, we will ask for your consent first.

6. Controlling cookies and storage

• Your browser’s settings let you block or delete cookies and local storage. Blocking es_admin_session will stop the organizer backend from keeping you signed in.
• Clearing local storage signs out the viewer side of the web platform on that browser. Your purchases are tied to your account, not to the browser, so you can sign in again.

7. Contact

Questions about cookies or storage: [email protected].