How cookies and browser storage should be used.

Local Tickets should keep browser storage lean and explain it clearly. This policy foundation separates essential platform behaviour from optional analytics or marketing tools that need approval before use.

Launch approval needed Final cookie list, analytics tools, consent-banner rules and retention periods still need approval before launch.

Essential cookies

Creator and staff sessions use secure HTTP-only cookies so signed-in tools can work. These cookies should be limited to authentication and security needs.

Checkout and ticket flows

Buyer checkout and Find Tickets flows should avoid unnecessary browser storage. Failed-payment retry links may preserve event or ticket selections without putting personal details into the URL.

Analytics

Analytics or performance measurement tools should only be added after the provider, consent requirements and data-sharing implications are approved.

Marketing and embedded media

Future embedded videos, widgets, campaign tracking or affiliate links may involve third-party storage or tracking. Those features need clear labelling and consent rules before going live.

Managing cookies

Visitors can control cookies through their browser settings. A site-level consent control should be added if non-essential cookies or similar technologies are introduced.