Privacy
Version 2026-11-02.1 · Beta: short and plain on purpose. Not yet reviewed by a lawyer.
We collect as little as we can, say what we collect, and delete it on a schedule.
What we collect
- Hosts: a username and a passkey public key. No email, no password, no phone number.
- Guests: a name and a phone number. The phone number is not checked or verified.
- Guest accounts: if you pull up with Face ID, your account keeps a passkey public key and the name and phone you last used, so next time is one tap and your tickets show up on any phone. They stay until you ask us to delete the account. Ticket copies of your name and phone still follow the 30-day schedule.
- Events: what the host enters, including the address and an optional flyer. Location data is removed from flyer images.
- Tickets and check-ins: which tickets exist, their status, and when each was scanned.
- Payments: for paid tickets, the amount, fees, refunds and Stripe's payment reference. Card details go to Stripe, never to us. Hosts who sell tickets give us their full name, an email and where to send their money (like a Venmo handle), so we can pay them and reach them about it. Hosts of free events still give none of these.
- Where visits come from: the app or website an event link was opened from (like Instagram), worked out automatically. Only the pullup team sees it, as totals. Hosts don't see it.
- Security log: IP address, browser type, a device cookie, and timestamps for sign ups, sign ins and ticket requests.
Why
To run the event: issue tickets, let hosts see their own guest list, and scan people in. The security log is for stopping abuse and for valid legal requests.
Who sees it
- A host and the co-hosts they choose see the guest list for that host's events only.
- Guests never see the guest list.
- The exact address is shown to ticket holders only, at the time the host picks.
- We don't sell your data, share it for targeted ads, or build profiles of you. No ad trackers, no cross-site tracking, no session recording. So there is nothing to opt out of; Global Privacy Control signals are respected by default.
- Data may be disclosed when the law requires it. See Law enforcement requests.
How long we keep it
- Guest names and phone numbers: deleted 30 days after the event ends. Only anonymous counts stay.
- Security log: deleted after 90 days.
- Payment records (amounts and references, no names or card details): kept as long as tax and accounting law requires.
- A valid legal preservation request can pause deletion for the data it names, until the hold ends.
- Deleted data can stay in encrypted backups for up to 7 days before the backups roll over.
Cookies and storage
A sign-in cookie for hosts, a device cookie for abuse prevention, and your browser's own storage to remember tickets you opened on this phone. No advertising cookies.
Your rights
Anyone can ask to see, correct or delete their data, wherever they live. This covers the rights in the Texas Data Privacy and Security Act, California's privacy laws and similar state laws. Email doorlist.help@gmail.com with the event or ticket link. We reply within 10 business days and finish within 45 days. If we say no, reply to appeal and we'll review it again within 60 days. Hosts can also cancel a guest's ticket at any time.
Children
pullup is for people 18 and older and is not meant for children. If we learn someone under 18 is using it, we delete their data.
Who stores it
- Fly.io runs the servers, in the United States.
- Tigris (part of Fly.io) stores encrypted database backups, kept for 7 days.
- Stripe processes payments for paid tickets, under its own privacy policy. It gets what you enter on its payment page, the event name, the guest name and the ticket link, which it prints on the receipt it emails you.
- No analytics, advertising or tracking companies get any data.
Law enforcement
How police and courts can request data, and what we need from them: Law enforcement requests.