Information buyers may provide
Ticket lookup and checkout flows may collect buyer names, email addresses, booking references, ticket-holder names, delivery details where posted tickets or merchandise are enabled, and any approved attendee answers.
Maintenance mode
Ticket search, checkout and creator tools are temporarily unavailable while maintenance is carried out.
Booking references and organiser accounts remain valid. Please try again once the maintenance message has cleared.
Privacy
This page sets out the privacy commitments and operational areas that need to be confirmed before Local Tickets goes live. It is written for buyers, organisers and staff support workflows, and should be reviewed against the final legal wording before launch.
Ticket lookup and checkout flows may collect buyer names, email addresses, booking references, ticket-holder names, delivery details where posted tickets or merchandise are enabled, and any approved attendee answers.
Creator accounts and event setup tools may store organiser account details, organisation records, venue information, event media, merchandise information, fulfilment settings and team-access records.
Local Tickets stores operational records needed to run the platform safely, such as order states, ticket references, audit logs, support notes, email delivery metadata, fulfilment status and backend request references.
Local Tickets is planned around hosted payment-provider flows. The platform must not store raw card details or sensitive authentication data, and payment records should keep provider references and payment state only.
Before launch, the privacy process should confirm how people can request access, correction, deletion or restriction of their data, how identity is checked and how support staff record the outcome.
Retention periods still need approval for orders, tickets, support notes, delivery addresses, audit logs, email metadata and organiser records. Once approved, those periods should be reflected in backend readiness settings and public wording.