ScreeningHome

Legal · Everyone

Cookies

This Cookie Policy explains how Screening uses cookies and similar technologies when you visit usescreening.com from anywhere in the world.

Last updated: 25 September 2026 (version 2026-09-04).

In short

  • We use strictly necessary cookies and similar storage for sign-in, security, and ticket playback.
  • We do not use advertising cookies or sell cookie data.
  • Vercel Web Analytics is cookieless. Sentry only sends diagnostics when something fails.
  • The same rule applies worldwide. There is no consent banner while cookies stay strictly necessary.

1. What we use

1.1 We use strictly necessary cookies, local storage, and session storage to:

  • keep you signed in and protect sessions (Better Auth);
  • enforce security, rate limits, and abuse prevention;
  • grant ticket and catalog playback after checkout;
  • remember essential checkout or return state for a short time.

1.2 Vercel Web Analytics is cookieless. It records aggregate page paths, not advertising profiles.

1.3 Sentry sends diagnostics only when something goes wrong. Credentials and ticket codes are redacted.

1.4 Passkeys store credential metadata with our auth provider when you enable them. That is not an advertising cookie.

1.5 We do not use advertising cookies, cross-site tracking pixels, or sell cookie data. If that changes, we will update this policy and obtain consent where law requires it.

2. Law

2.1 In the UK and EEA, strictly necessary cookies may be set without consent under PECR and the ePrivacy Directive. Other cookies would need consent. We currently set only strictly necessary cookies ourselves.

2.2 The same practice applies worldwide: we do not run a consent banner while our own cookies remain strictly necessary. Local rules that grant you additional control still apply — use your browser settings.

2.3 Personal data stored in cookies is processed as described in Privacy.

3. Control

3.1 You can block cookies in your browser. Essential cookies are required for sign-in and ticket access; blocking them will break those features.

3.2 Questions: [email protected].

Questions: [email protected]