What we keep, and why

• Account details: your full name, email address and contact number, and a password we store only as a hash.
• Bookings: the seats you hold, your booking reference, payment method and status, and the times these change.
• Payment proof: the image or PDF you upload for an online payment.
• Ticket and attendance records: which physical tickets were printed, collected and checked in.

• Running the booking: holding seats, verifying payments and releasing tickets.
• Contacting you about your booking: confirmations, payment reminders and collection notices.
• Admission on the day: checking names and ticket numbers at the door.
• Accounting for the event, with ticket revenue reported separately from sponsorship.

We do not sell or share your details with sponsors or anyone outside the event team.

Only Student Council officers with an admin role, and only what their role needs. Finance officers see payment proofs; ticketing officers see bookings and tickets; event staff see the check-in list. Every admin action is logged. You can see only your own bookings.

On Supabase (database and private file storage) and Vercel (the website), with access rules enforced in the database so that attendees can read only their own records. Payment proofs are stored privately and served only to authorised admins.

Until the event is reconciled. The retention period after December 18, 2026, and when records are deleted, will be set by the school and stated here before booking opens.

• Correct your name or contact number from your account page.
• Ask the Student Council to delete your account once you have no active bookings.
• Cookies are used only to keep you signed in; there is no advertising or analytics tracking.