Privacy
LivePass is operated from New Zealand. This page says what we hold, who else sees it, and what you can ask us to do about it. Where a detail is not settled, it says so rather than guessing.
Two sets of records
LivePass is white-label, so almost every record exists twice — once for the organiser whose site collected it, once for the platform that has to make it work.
- The organiser's records
- Ticket buyers, member-list applicants, campaign recipients and door check-ins belong to the organiser whose site collected them. They decide what to collect, what to say to those people, and how long to keep them on a list.
- Our records
- We hold the same data as the operator of the platform, plus the organiser's own account, so that checkout, payouts, scanning and support work at all. We do not sell personal information to anyone, and we do not use one organiser's buyer list to market to another organiser's audience.
- Where to ask
- If you bought a ticket, start with the organiser named on the site you bought from — the relationship is theirs. Write to us at help@livepass.nz if they cannot help.
What we hold
Everything below exists because a specific part of the product needs it. Nothing here is collected in case it turns out to be useful later.
- Organiser accounts
- Your name, email address, timezone and password — the password stored only as a salted hash — plus the sites and events you create, the team you give access to and the role each of them has.
- Purchases
- What was bought, for which event, at what price and when, with the buyer's name and email so that a ticket can be issued and the door can check it.
- Door records
- Which ticket was scanned, at what time, on which device. A duplicate scan records the device that scanned first, because that is the only thing that settles an argument at the door.
- Campaign sends, the list each one went to, and whether someone unsubscribed.
- The activity log
- Refunds, comps and edits, with the account that made them. It is kept after the record it describes is deleted. Refunded and voided tickets are kept the same way, as non-destructive records, so the financial history stays accurate.
- Support
- Whatever you send us at help@livepass.nz, and our reply.
Card payments
Card payments run through Stripe. Your card details go directly to Stripe and are never stored on our servers. We hold the outcome — paid, refunded, disputed — and the amount, not the instrument.
Stripe handles that payment data under its own terms as its own controller. Where a site settles into the organiser's own Stripe account, Stripe's relationship is with the organiser directly and their Stripe agreement governs it.
Tracking, and who switched it on
An organiser can connect a Meta, TikTok or Google Analytics pixel to their own site, and point a Discord webhook at their sales milestones. Those are the organiser's choice, configured by them, reporting to their accounts — not to ours. If you are the organiser turning one on, you are the one who owes your buyers notice of it.
The platform itself runs no advertising trackers, and nothing we run follows you to another site. What we put in your browser is your session token and your interface preferences, such as the theme you picked.
This marketing site counts visits, so we can tell which pages are worth keeping. It records the page you opened, the site you arrived from, and a coarse device and country. It sets no cookie, stores no advertising identifier, and never names you. It runs only after you accept the notice shown on your first visit — decline and nothing is loaded at all. Your answer is kept in your own browser, and the Privacy choices control at the foot of any page changes it later. How long the counts are kept is to be confirmed.
Who else processes it
Three of them, named.
- Stripe
- Payment processing, payouts, chargebacks and disputes.
- Amazon Web Services
- Hosting and email delivery. Both process data on our behalf under their own security and privacy commitments, and we share only what each one needs to do its job.
- Vercel
- Hosting and visit counting for this marketing site only. The counting is cookieless and runs only with your consent; it does not reach an organiser's ticketing site or the dashboard.
We do not sell personal information, and we do not share it for another company's advertising.
How long we keep it
Account and transaction records are kept for as long as your account is active, and for as long after that as financial record-keeping requires. Marketing lists last until the person unsubscribes or the organiser deletes them. Refunded and voided tickets are kept as non-destructive records rather than deleted.
Traffic is encrypted in transit with TLS, passwords are hashed, and access to production systems is restricted. Retention periods, stated in months: to be confirmed.
What you can ask for
The Privacy Act 2020 gives you these rights over what we hold about you. Ask at help@livepass.nz.
- Access
- A copy of what we hold about you.
- Correction
- Fix what is wrong. If we disagree that it is wrong, you can have your correction attached to the record so anyone reading it sees both.
- Deletion
- We delete what we are not required to keep, and tell you plainly what we are keeping and why.
- Complaint
- If we handle any of this badly, the Office of the Privacy Commissioner takes complaints at privacy.org.nz.
Contact
help@livepass.nz reaches us. Privacy officer: to be confirmed. Postal address: to be confirmed.
This page changes when the product changes. Material changes are emailed to organisers before they take effect.
Questions about your data
Ask a real question and get a real answer, not a form.