Privacy policy

What we collect

A booking carries the name, email address and phone number you type in, the tables and times you booked, and its payment state. If you create an account, it holds your email and your bookings; walk-in guests can book with no account at all.

Confirming a transfer deposit means looking at the evidence of that transfer: a receipt screenshot you choose to upload, and the notification our own account receives, which carries the sender name, amount and reference your bank attaches. We never see or store card numbers or banking passwords.

If you enable notifications in the iOS app, we store the device token Apple issues so we can send you your booking updates. It identifies a device, not a person.

What it is used for

Running your booking: holding the table, confirming the deposit, emailing your confirmation and door code, settling the bill, and issuing any cancellation credit. Contact details are shown to venue staff on a need-to-see basis — the floor console redacts them; only management sees them in full.

If the venue enables it and you have the app, you may receive an occasional “come back” notification after a visit. Turning off notifications in iOS settings ends that.

Who processes it

The site runs on Supabase (database and sign-in), Cloudflare (hosting), Resend (email) and Apple (push notifications). Each processes data only to provide its service. We do not sell or share your details for marketing.

Retention and your choices

Bookings and payment records are kept as business records of real transactions. Manage links, sessions and push tokens expire or are deleted when stale.

To correct or delete your details, or to ask what we hold about you, contact us through the details in the footer. Deleting payment records that document a real transaction may be limited by law; everything else is yours to remove.