Book a look

Privacy policy

What Riderly Guest List stores, why, where it lives and how long it’s kept. Written in plain English.

Draft, last updated 11 October 2026. This policy is being reviewed and may change. We’ll tell venues about any changes that matter.

Who we are

Riderly Guest List (“Riderly”, “we”) is a guest list and door tool for live music venues, run from Melbourne, Victoria. We aim to handle personal information in line with the Australian Privacy Principles in the Privacy Act 1988 (Cth).

If you’re a guest: the venue decides who goes on its list and what’s written about them. Riderly stores that list on the venue’s behalf. For questions about your details, contact the venue first. They can see, correct and delete them. You can also contact us (see the end of this page).

What we store

WhoWhat
GuestsName, number of +1s, list type (e.g. Guest, Artist, Media), VIP flag, any note the venue or contributor adds, who added them, and door check-in and check-out times.
ContributorsThe name the venue gives them (e.g. an artist or promoter), their allocation and any note.
Venue staffThe name typed on each phone or laptop, and a log of what was done under that name (added a guest, checked someone in, used a manager code).
Refused entryOnly if a venue uses its banned list: the person’s name (or “name unknown”) and the venue’s short reason. Only the venue admin can see the list, and every look and change is logged. Door staff see a warning on a matching guest, never the list. Each entry is reviewed every 12 months and removed a month later unless the venue renews it.
Refused entry: photosOnly if a venue turns on banned-list photos. A photo of the person, taken at the door (staff should tell the person they’re taking it) or added by the venue admin. A door photo isn’t added until the venue admin approves it; if they don’t within 24 hours, it’s deleted, and photos waiting for approval are never copied into backups. Door staff can see a photo when a guest’s name matches, and can open a gallery of the venue’s banned-list photos; every look is logged with the staff member’s name. Staff compare faces by eye: Riderly does no automatic face matching or face recognition. A photo is deleted with its entry, or earlier by the venue admin or with a manager’s code.
VenuesVenue name, username, contact name, email, phone (optional) and the message sent with the sign-up. Passwords and manager codes are stored only as one-way hashes. We can’t read them.

We don’t ask guests for email addresses, phone numbers, dates of birth or ID. Please don’t put sensitive information (health, ID numbers and so on) in notes.

Why we use it

  • To run the venue’s guest list and door: who’s on the list, who has arrived, how many people are inside.
  • To show the venue who did what, so mistakes can be traced and fixed.
  • To run venue accounts: logins, password resets and service emails (for example “your venue is live” or a night report the venue asks for).
  • To keep the service secure: stopping password guessing and keeping backups.

We don’t sell personal information or use it for advertising. It’s used only to run the service.

Cookies and storage on your device

We use only what’s needed to make the app work. There’s no analytics, advertising or tracking from third parties.

  • Login cookies keep a venue, venue admin or Riderly admin signed in. They are signed, can’t be read by scripts on the page, and expire after 30 days.
  • On the phone itself (browser storage): the name typed on that device, a random device ID used to limit wrong password attempts, and door taps waiting to sync while offline. The door app also keeps a copy of the current show on the phone so it keeps working if the venue Wi-Fi drops. Logging out deletes that copy.
  • VIP alerts (only if someone turns them on): the phone’s push address, kept so we can wake it. The alert itself is fetched from us over the phone’s own login, so no names pass through Apple’s or Google’s push services.
  • Contributor links need no login or cookie. The private link itself is the key, so treat it like a password.

Where it’s stored

  • Private and secure: guest lists are only reachable with your venue’s login, or by a contributor through their own private link. Nothing is published or listed publicly, and everything is sent over an encrypted connection.
  • Backups: encrypted backups are made every night.
  • Email: service emails, like “your venue is live” or a night report you ask for, go to venue contacts only.

We use trusted providers for hosting and email (DigitalOcean and Google), so some information may be handled on their systems outside Australia.

How long we keep it

  • Guest details stay until the venue deletes them, deletes the show, or its automatic clean-up runs. A venue can set “keep guest details for X days” in its venue admin page. After that, names and notes are removed and only totals remain (how many were on the list, how many came).
  • Removed guests: when a venue removes a guest, their name is also removed from the show’s activity log. If the venue uses “Oops / Undo”, a copy is held in the server’s memory only (never saved to disk or backups) for up to 12 hours so a mistake can be undone, then it’s gone.
  • Banned-list photos: see “Refused entry: photos” above. Photos waiting for approval are deleted after 24 hours.
  • Backups roll over automatically, and every copy is deleted within 12 months.
  • Venue accounts are kept while the venue uses the service. When a venue is deleted, its shows, guests and activity are deleted with it, apart from the rolling backups above.

Security

Everything is encrypted in transit, passwords are stored securely, and logins are protected against guessing. Important actions, like going over capacity, need a manager’s code, and every use is logged. If a security incident ever affected your information, we’d let you know promptly, as Australian privacy law requires.

Your choices

  • Guests can ask the venue to correct or remove their details at any time, or ask us and we will pass the request on or act on it.
  • Venues can export a show’s list as a spreadsheet, edit or delete any guest, set a retention period, and ask us to delete their whole account.
  • If you’re unhappy with how we’ve handled your information, contact us first. If it isn’t resolved, you can complain to the OAIC.

Contact

Contact Riderly through the form on the home page, or ask your venue to pass your request on.

Terms of use · Guide · Home