Last updated 4 November 2026
Door Duty is run by Adam Scott Rowe. You can reach us at support@doorduty.app.
Door Duty is an app for Wix websites. An organiser (the owner of a Wix site) installs it to check guests in to their Wix Events with volunteers' phones.
For guests and volunteers, the organiser is in charge of the data (the "controller"). Door Duty handles guest and check-in data only to provide the service the organiser asked for (we're their "processor"). If you bought a ticket or volunteered at an event, contact the organiser first about your data; we'll help them with any request.
For organisers' own account details (which Wix site installed Door Duty, its plan and purchases), Door Duty is the controller.
| What | Why | How long we keep it |
|---|---|---|
| The Wix site's ID and name, and the logo and colour it chooses | To run the app for that site and brand the check-in screen | Until 30 days after the app is uninstalled |
| The Wix user ID of the person who opened the Door Duty dashboard | To sign them in to the dashboard | 12 hours |
| Event settings: which ticket questions to show at the door, warnings to flag, people per ticket type, walk-up sales | To show the door what the organiser asked for | Until 30 days after the app is uninstalled |
| Volunteer links: a name for each link (for example "Front door" or a volunteer's first name), and its PIN, which is stored encrypted and as a one-way hash | To let volunteers' phones check guests in without an account | 30 days after the link ends. A link ends 36 hours after its event starts, or sooner if the organiser switches it off. |
| Event templates: saved link names and settings | To set up repeat events quickly | Until the organiser deletes them, or 30 days after uninstall |
| A shared copy of an event's guest list: each ticket's number, guest name, ticket type, order status and the answers to the questions the organiser chose to show (which can include allergy or access needs) | So several phones can load the list quickly and work without signal | Up to one day. It's replaced whenever the list changes. |
| Check-in records: which ticket was checked in, when, by which link and which phone (a random ID, not the phone's number or identity) | To stop a ticket being used twice, allow undo, and sync phones that were offline | 30 days after the link ends |
| Door log: each check-in, undo and refused scan, with the time and the link | To show the organiser what happened at the door, and for the event report | 90 days |
| Event summaries: counts and times only (tickets sold and arrived, the busiest time). No names or ticket numbers. | For the organiser's year view of reports | Until 30 days after the app is uninstalled |
| Billing records: the site's ID, event IDs, which plan or pass was bought, the price and the dates | To give the organiser what they paid for, and for tax and accounting | As long as the law requires us to keep accounting records (in the UK, six years), including after uninstall |
| Emails to support@doorduty.app | To answer you | As long as needed to help you, then deleted |
Check-ins are also written back to Wix, so the organiser's Wix Events dashboard shows who has arrived. Data in Wix is covered by Wix's privacy policy.
The guest spreadsheet in the report is made when the organiser downloads it and isn't stored by us.
A volunteer's browser keeps the event's guest list and any check-ins it couldn't send yet, so the door keeps working without signal. This is stored in the browser on that phone only, not in a cookie. It's removed when the link ends or is switched off, when the link moves on to another event, or when the browser's site data is cleared.
The organiser's dashboard keeps its sign-in only for the browser tab it's open in.
For guest and check-in data, we act on the organiser's instructions; the organiser decides the legal basis for collecting it. For organisers' account and billing details, the basis is providing the service they installed (contract) and keeping accounts (legal obligation).
Answers about allergies or access needs can be health information. Door Duty shows them at the door only if the organiser chooses to, to keep guests safe, and deletes them with the rest of the guest list copy.
We don't sell data, show adverts, use analytics or tracking, or build any list of guests or organisers for our own use.
Everything is sent over HTTPS. Links and PINs are stored as one-way hashes, with encrypted copies only so the organiser can see them again. Wrong PINs are rate-limited. Organisers can switch off a link at any time, which stops every phone using it, or change its PIN and sign its phones out.
You can ask for a copy of your data, or for it to be corrected or deleted. Guests and volunteers should ask the event organiser, who controls that data; we'll help them. Organisers can delete everything Door Duty holds for their site by uninstalling the app (it's gone within 30 days, apart from billing records), or by asking us.
If you're unhappy with how we've handled your data, please tell us first. You can also complain to the data protection authority where you live; in the UK that's the Information Commissioner's Office.
Door Duty is used by adults: event organisers and their volunteers. Guest names on a school event's tickets may include children's names if the organiser sells tickets that way; they're handled as described above and deleted on the same schedule.
If we change this policy, we'll update the date at the top. If a change affects what we keep or why, we'll tell organisers in the Door Duty dashboard first.