How we handle data
Follow your information from booking to the entrance—and understand what happens when a device goes offline.
01 · A booking becomes a ticket
We save the attendee name, email and phone number with the event and create a signed QR ticket. The private ticket page shows the name, event and admission status. Email delivery, when enabled, uses a durable queue so a retry does not intentionally create another message.
02 · Access follows the job
Administrators manage their workspace, events and attendees. Scan-only accounts verify tickets on the platforms assigned to them. Offline preparation is a separate permission. Workspace data is separated through server-side authorisation checks.
03 · Devices prepare for the door
An authorised scanner can download event verification data, attendee ticket records and revocations. The browser uses IndexedDB and local storage so it can work without internet. Browser data is not separately encrypted at rest by AttendStack; use trusted, locked devices and avoid shared browser profiles.
04 · Scans sync securely
Offline scans keep their original identifiers. Web sync packages them into ZIP batches of at most 200 KB before encryption, encrypts the batches and signs them with an enrolled device key. The server checks the signature and reconciles records. Duplicate checks are strongest once devices share the latest records. Bluetooth peer exchange is still under development.
05 · An event ends; its history remains
Archived events keep their attendees and scan history. A data-deletion request starts a review—it does not silently cancel a ticket or erase an event. Pending scans should be uploaded before clearing a device. Disconnected devices cannot receive immediate revocations or deletion instructions, and backup copies require a separate retention process.
Questions or a data request?
Contact the AttendStack service team: send a privacy request. For event admission, cancellation, or booking questions, contact the organiser shown on your event page.