Privacy

UsherQR is used by venues — shops, salons, pharmacies — and by their customers, who scan a code to join a queue. What we hold about each is different, and so is who is responsible for it.

For customer data, the venue is the data controller and we are their processor. We hold it on their behalf and only do what the venue asks of us.

Depending on what the venue chose to ask, we may hold:

• Your first name, or the name you typed
• A mobile number, if the venue asked for one
• Whatever you entered on the venue’s form — an order, a registration number, an answer to their question
• Your ticket number and the times you joined and were served

We use it for one thing: running that queue. We do not sell it, share it with anyone else, use it for advertising, or build any profile of you across venues.

It is deleted automatically. 30 days after your ticket is finished, your name, number and answers are erased. What remains is an anonymous record that a ticket existed and how long it took, which the venue uses for its own wait-time estimates.

You can erase it sooner. Open your ticket and choose to be forgotten, or ask the venue.

If you ask to be notified, your browser gives us an address at its own notification service — Google’s for Chrome and Android, Apple’s for Safari, Mozilla’s for Firefox. Each alert passes through that service to reach you, carrying only your ticket number and the venue’s name — never your name, number or answers. That address is erased along with the rest of your details.

If you add your ticket to Apple Wallet, the card holds your ticket number, the venue and the queue — not your name, number or answers. So that it can update, your phone registers with us using an identifier Apple Wallet creates for that purpose, and when the queue moves we send Apple an empty signal telling your phone to fetch the new version from us. That registration is deleted within three days of your visit, and you can delete the card whenever you like.

Some venues run a club: a stamp card in your phone’s wallet. The venue runs it and is responsible for it, and we hold your membership on its behalf. We keep:

• Your first name, if you give one — so staff can greet you. It is never printed on the card
• An email address, if you give one and confirm it from your inbox
• Your stamps and rewards, and the dates you visited, were stamped or used a reward
• Which of your queue tickets at that venue belonged to your membership

Your card shows your stamps, rewards and a code for staff to scan. It does not carry your name, email or anything you told the venue.

Your email is used for one thing: getting your card back if you lose your phone or get a new one. We email you once to confirm it, and again only when you ask for your card back. These emails come from the venue “via UsherQR”, sent by Resend on servers in the European Union. Until you confirm the address it isn’t kept, and it is never used for marketing.

The venue can put a short message on the card — “10% off today” — which your phone shows the way it shows your stamps. At most one a day. It goes to the card itself, not to your email or your phone number, and the venue is never told who saw it. Your phone’s own settings can silence the card, and leaving the club stops it altogether.

A venue can also put its own address on the card, so that your phone shows the card when you are nearby — handy when you are at the counter. Your phone does that by itself, comparing where it is with the place written on the card. Nothing is sent anywhere, and neither we nor the venue is ever told where you are.

Joining leaves one small cookie on your phone for that venue, so that your next ticket there goes on your card. It does nothing else, and nobody else can read it.

Leaving is on the back of your card and on the venue’s club page. It deletes your membership, name, email, stamps and rewards straight away, and your card then says you have left. A membership with no visit for 24 months is deleted in the same way. What remains is an anonymous count — that a stamp or reward happened — which the venue uses for its own totals.

Some venues show first names on their in-venue screen. Where they do, you appear as a first name and an initial — “Sarah B.” — never in full, and never with your number or anything from the form. Venues handling anything medical or confidential have this switched off by default.

We hold your name, email address, the details of your venue and its settings, and billing records. Payment card details are handled entirely by Stripe — they never reach our servers.

Account email — confirming your address, resetting a password — is delivered for us by Resend, on servers in the European Union. It carries your email address and the link itself, nothing else. The only email your customers ever receive is a club member’s confirmation and card-recovery emails, described above.

Everything is stored and served in the United Kingdom — the database in London with Supabase, and the application from the same region by Vercel. There are two exceptions: phone alerts, which travel through your phone or browser maker’s notification service wherever that runs, and email — for venue staff’s accounts and club members’ cards — which is sent from within the EU. Both are described above.

We may combine anonymous totals from across UsherQR — for example, how many visits coffee shops get on a Saturday morning. They are counts, not records: they cannot identify you, and they do not name any venue.

You can ask for a copy of what we hold, ask us to correct it, or ask us to erase it. If you joined a queue, the quickest route is the venue itself, but you can come to us directly and we will help either way.

If you think we have handled your data badly, you can complain to the Information Commissioner’s Office.

UsherQR is run by Studio Dialect Ltd, the data controller for everything on this page about venue accounts. Write to support@usherqr.com for anything on this page — a copy of your data, a correction, an erasure, or a question about how any of it works. We answer within a few working days.

If you joined a queue and are not sure which venue holds your details, tell us the ticket number and roughly when, and we will find it.

Two kinds of cookie are needed for something you asked for: one keeps venue staff signed in, and one on a club member’s phone per venue makes their next ticket go on their card. Customers who only join a queue are not given a cookie at all.

On the pages that describe UsherQR — the home page, pricing, the pages for each kind of business and the like — we ask whether we may use Google Analytics, to see how people find the site and which pages help. It sets its cookies only if you say yes. It never runs on a queue ticket, a club card or the staff console, and it is set not to use what it sees for advertising. Google processes it for us, and may do so outside the UK.

You can change your mind at any time with “Cookie settings” at the bottom of any of those pages; saying no removes the analytics cookies. There is still no advertising, and we sell nothing about anyone.