Privacy policy
Last updated 19 November 2026
Bottle & Booth is booking and ordering software for nightclubs and bars. This policy explains what we collect when you book a booth, order from a booth, work a shift or manage a venue, and what we do with it. We follow the Australian Privacy Principles in the Privacy Act 1988.
Who is responsible
Bottle & Booth is run by Rhythm Revolt Records, based in Brisbane, Australia. When you book or order at a venue, that venue decides what your details are used for (for example, contacting you about your booking). We run the software and store the details for them. Questions go to support@bottleandbooth.com.
What we collect
- Guests who book or order: your name, mobile number and/or email, the booth, the night, party size, what you ordered, how you paid (card or cash), your bottle sign message, and whether you said yes to hearing about the venue's events. Requests you send your booth host (like ice or a note) are kept with the booking.
- Guests who sign in to My bookings: your email address and a sign-in cookie on your device. We use it to show your own bookings, past nights and any perks the venue offers.
- Friends who join a booth: only what you type in to join, plus your orders and payments.
- Booth hosts and venue staff: name, profile photo if you add one, PIN (stored scrambled, never readable), shifts clocked, availability, sales you served, and team messages and alerts you send during the night.
- Venue managers and owners: email address, password (stored scrambled by our login provider) and what you change in the admin.
- Everyone: technical details needed to run and protect the service, such as the IP address of failed sign-in or join attempts, and browser notification settings if you turn alerts on.
We don't collect dates of birth or ID numbers. Card details are handled by our payment provider; we never see or store your full card number.
Why we use it
- To hold your booth, send your booking code and confirmation, and let staff serve the right booth.
- To keep a correct record of orders and cash for the venue's end-of-night report.
- To stop misuse: limiting repeated join codes, sign-ins and online bookings.
- To send you news about the venue's events, only if you ticked the box. Every message has an unsubscribe link, and staff never see your email or number.
We don't sell personal information and we don't use it for advertising.
Who we share it with
Only the venue you booked with, and the companies that run parts of the service for us:
- Supabase stores the database in Sydney, Australia.
- Netlify hosts the website and app (servers may be outside Australia).
- Resend sends booking emails (processed outside Australia, including Japan and the United States).
- Cloudflare runs our domain and the spam check on online booking (servers worldwide).
- Stripe processes card payments and tips when a venue takes card payments.
Some of these providers process information outside Australia. We choose providers with strong security and only give them what they need to do their job. We'll share information with police or regulators only when the law requires it.
How long we keep it
Booking and order records are kept while the venue uses Bottle & Booth so its sales records stay complete, and for up to 7 years after for tax purposes. A venue can delete its customer list at any time. Marketing consent ends as soon as you unsubscribe.
Your choices
- Ask to see, correct or delete your details: email support@bottleandbooth.com or contact the venue. We reply within 30 days.
- Stop marketing emails with the unsubscribe link in any message.
- Turn off staff notifications in your browser or phone settings.
- Sign out of My bookings at any time; the sign-in cookie is removed.
If you're unhappy with how we handled a privacy question, tell us first. If it isn't sorted, you can contact the Office of the Australian Information Commissioner at oaic.gov.au.
Security
Information is sent over HTTPS, access is locked to each venue's own staff and managers, and PINs and passwords are never stored in readable form. If a breach is likely to cause serious harm, we'll tell the people affected and the regulator as the law requires.
Changes
We'll update this page when our practices change and show the new date at the top.