Privacy Policy

Last updated 10 November 2026

Buzzerify is run by TODO legal name (ABN TODO ABN) of TODO postal address, NSW, Australia. In this policy, "we", "us" and "our" mean TODO legal name. "You" means the person whose information we handle.

This policy explains what personal information we collect, why we collect it, how we look after it, and how you can ask us about it. It is written to follow the Australian Privacy Principles (APPs) in the Privacy Act 1988 (Cth).

If you are a customer of a venue

You scanned a QR code at a café, food court, bistro or takeaway counter, and a web page opened showing your order number. Here is what happens with your information, in plain English.

No name, no account, no app. We do not ask who you are. The page only knows your order number and a random code in the link.
The venue sees your order, not you. The venue's staff screen shows your order number and whether an alert is switched on. It does not show your mobile number.
Alerts on your phone. When alerts switch on (the page tries by itself, and otherwise your first tap on the page does it), the page plays a near-silent audio stream. That is what lets your phone keep the page running while it is locked, and show your order number in the lock screen media controls. It is a sound file we play. It does not use your microphone or camera, and nothing is recorded.
Android notifications. If your browser asks and you allow notifications, your browser gives us a push address (a "push subscription"). We use it to send one "ready" message. The message is encrypted before it leaves our server, and the push service run by your browser maker (Google, Apple or Mozilla) delivers it. We delete the push subscription when your order closes.
A text message, only if you ask for one. If you type your mobile number into the page, we send one text when your order is ready. Nobody else can enter your number for you. We delete the number when your order closes, normally within hours. We never use it for marketing.
A phone call, only if you ask for one. If you type your mobile number into the page for a call, we call it to say your order is ready, but only if the page can't ring you then (for example because another app or a phone call has taken its sound, or nobody has looked by the time the order would be called out). We call at most twice for one order. Nobody else can enter your number for you. We delete the number when your order closes. We never use it for marketing.
One small cookie, for posters. If you took a number from a poster, the page sets one essential cookie so that scanning the poster again gives you the same ticket. There are no advertising cookies and no third-party analytics on the order page.
Technical logs. Like most websites, our servers can log your IP address and browser type. We keep these logs for up to 30 days for troubleshooting and security, then delete them. To stop abuse we also count requests from each internet address for up to an hour, storing the address only in a scrambled (hashed) form. The ticket notes the kind of phone and browser (for example "iPhone, Safari") to help us fix problems.
When your order closes. When staff mark the order collected or cancel it, or it times out, the ticket closes. Your push subscription and phone number are deleted. What remains is an order number, timestamps and the kind of phone, with nothing that identifies you, and we delete that too, 90 days after the ticket closes.

If you have a question or a complaint, email hello@buzzerify.com. Because we hold no name, we may ask for the venue, the order number and the time so we can find the ticket.

Who this policy covers

We handle personal information about:

Venue account holders: the owner or manager who signs up a venue.
Staff users: people a venue invites to use its staff screen.
Venue customers: members of the public who use the order page.
Visitors and enquirers: people who visit buzzerify.com or email us.

We are a small business

Many Australian small businesses are not covered by the Privacy Act because their annual turnover is $3 million or less, and we may fall within that exemption. We have chosen to run Buzzerify as if the Privacy Act and the APPs apply to us in full, and this policy is written to meet them. If we opt in to the Act formally or grow past the threshold, the Act will apply to us directly and this policy will not need to change.

What we collect and why

Venue account holders

What we collect: your name, email address, password (stored only as a hash, never in plain text), business or trading name, business address, ABN, subscription status and payment history, and any support messages you send us.

Why: to create and secure your account, provide the service, bill you and issue tax invoices, answer support requests, send service notices, and meet our legal obligations (for example, keeping tax records).

Payments are processed by Stripe. Your card details go straight to Stripe. We never see or store your full card number.

Staff users

What we collect: your name, email address, password hash, role, and which orders you created on the staff screen.

Why: to let you log in, keep the queue accurate, and help the venue work out what happened if there is a question about an order.

The venue gives us your name and email address when it invites you.

Venue customers

What we collect: an order number, a random link token, the time the page was opened, which alert method is on, the kind of phone and browser, a push subscription if you allow notifications, your mobile number if you type it in for a text or a call, and server logs (IP address, browser and device type).

Why: to show your order status, alert you when your order is ready, keep the service running reliably, and prevent abuse.

We do not collect your name, contact details or location, and we do not build a profile of you. You can use the order page without ever identifying yourself.

Visitors and enquirers

What we collect: server logs for pages on buzzerify.com, counts of visits to our website (see "Visit counts on our website" below), and whatever you include when you email us.

Why: to keep the site running and secure, to see which pages help people and where our visitors come from, and to reply to you.

Marketing

We only send marketing email to people who have agreed to receive it, or to venue contacts we already do business with, and every marketing email has a working unsubscribe link. We never send marketing to venue customers. Emails about your account (such as verification emails, receipts and service notices) are not marketing.

How we collect information

Directly from you, when you sign up, use the service or email us.
Automatically, through server logs, and through the essential cookies and the visit counts on our website described below.
From Stripe, which tells us whether a payment succeeded and issues invoices.
From the venue, when it invites a staff member.

Cookies and similar technology

We use four cookies, and all of them are essential:

a session cookie that keeps account holders and staff logged in;
a cookie that remembers which venue a logged-in person is working in;
a cookie on a paired counter screen, so that it stays paired without anyone logging in; and
a small cookie from the poster's "take a number" page, so that scanning the poster again reopens your existing ticket.

We do not use advertising cookies, and the visit counts on our website (described next) set no cookies at all.

A browser push subscription is held by your browser and by us until your order closes. You can withdraw notification permission at any time in your browser or phone settings.

Visit counts on our website

We count visits to the pages of our website, including the sign-in and sign-up pages, with Vercel Web Analytics. For each page view it records the page, the page that sent you to it, any campaign tags in the link (such as utm_source), your approximate location (such as your country), and the kind of device, operating system and browser. It sets no cookies. It tells one visitor from another with a scrambled code worked out from the request, which it discards after 24 hours, and it does not tie the counts to you or to your IP address. We see only totals.

The counts never run on the order page, a counter screen or the staff app. A link that carries a one-time code, such as a password reset, an email confirmation or an invitation, is never counted. From any other link we keep only its campaign tags and the plan you picked on our pricing cards, and drop the rest before the visit is counted.

How we use and share information

We use personal information only for the purposes described above, and for closely related purposes you would reasonably expect.

We share personal information only:

with the service providers that help us run Buzzerify (listed in the next section), who may use it only to provide their service to us;
with the venue, limited to the order status shown on its staff screen;
when the law requires or permits it, for example to respond to a court order; and
with our professional advisers, under confidentiality.

We do not sell personal information, and we do not share it for other companies' marketing.

Overseas disclosure

Our application and database are hosted in Sydney, Australia. Some of the services we rely on are run from overseas, so some information leaves Australia or is held by an overseas company:

Vercel and Neon (United States): they host our application and our database in their Sydney regions, so all of the information described in this policy is stored with them. Vercel's network also delivers our web pages to visitors through servers in other countries, and Vercel keeps the visit counts on our website.
Stripe (United States): payment and billing details for venue account holders.
Resend (United States): the addresses and contents of the account and service emails we send, and the messages people send us through our contact form.
Browser push services run by Google, Apple and Mozilla: the push address of a customer who allows notifications, and the encrypted "ready" message. These services run wherever the customer's phone connects, which can include the United States and other countries.
Twilio (United States), if the venue offers texts or calls: the mobile number, and the words of the "ready" text or call, for customers who ask for one. It sends texts and places calls through its own network, which can include the United States.

Before we disclose personal information overseas we take reasonable steps to protect it, including choosing well-established providers, relying on their data protection commitments, and sending only the minimum needed. Privacy laws in these countries can differ from Australia's.

Security

We take reasonable steps to protect personal information from misuse, interference, loss, and unauthorised access, modification or disclosure. These steps include:

encryption in transit (HTTPS) for every page and connection;
passwords stored as salted hashes;
long random link tokens for customer tickets, so they cannot be guessed;
rate limits and other abuse controls;
access limited to the people who need it, with administrative access logged;
deleting customer phone numbers and push subscriptions as soon as an order closes; and
hosting with providers that maintain their own strong security controls.

No system is completely secure. If a data breach happens that is likely to result in serious harm, we will notify the people affected and the Office of the Australian Information Commissioner (OAIC) as the Notifiable Data Breaches scheme requires.

How long we keep information

Customer phone numbers and push subscriptions: deleted when the order closes, normally within hours of the order being collected, cancelled or timing out.
Customer tickets: the order number, link token, timestamps and the kind of phone are kept for 90 days after the ticket closes, for the venue's order counts and to help us fix problems, then deleted.
Server logs: up to 30 days.
Website visit counts: we can see them for 12 months. Vercel may keep them longer, and they hold nothing that identifies you.
Rate-limit counts: up to an hour, with addresses and emails stored only in hashed form.
Venue and staff accounts: for as long as the account is in use, and then for 90 days after the venue's trial or plan ends or the account is closed, so the venue can come back or download a copy (from the Settings page, or by asking us). We email the account holder a week before the 90 days are up. Then we delete the venue, its orders and its counter screens, and the logins of staff who belong to no other venue. Records we must keep by law, such as tax invoices and payment records, are kept for as long as Australian tax and business record-keeping laws require; Stripe holds those. If you ask us to delete your account sooner, we will.
Support emails: for as long as needed to resolve the matter, and for a reasonable period afterwards.
Backups: deleted information drops out of our backups as they are rotated.

Access and correction

You can ask for a copy of the personal information we hold about you, or ask us to correct it, by emailing hello@buzzerify.com. We will respond within 30 days, and we do not charge for this. Venue account holders and staff can also update most details in their account settings.

Because we hold no name or contact details for venue customers, we may not be able to link a request to a ticket. If we cannot, we will tell you why.

If we refuse a request, we will give you our reasons in writing and tell you how to complain.

Complaints

If you think we have mishandled your personal information, please contact us first at hello@buzzerify.com or by post at TODO postal address, NSW, Australia. We will acknowledge your complaint within 7 days, look into it, and aim to give you a written response within 30 days.

If you are not satisfied with our response, or you do not hear from us within 30 days, you can complain to the OAIC at www.oaic.gov.au.

Children

Buzzerify is used in public places, and anyone who orders food may open an order page, including children. The order page collects no name, age or contact details, and alerts work the same way for everyone. We do not knowingly collect any other personal information from children. Venue accounts must be held by people aged 18 or over. Staff users are invited by their venue, which is responsible for their use of the staff screen.

Changes to this policy

We may update this policy from time to time. We will post the new version on buzzerify.com with a new "last updated" date. If a change is significant, we will also email venue account holders before it takes effect.

Contact us

TODO legal name (ABN TODO ABN) TODO postal address, NSW, Australia hello@buzzerify.com buzzerify.com