Guests and deletion
See who's enrolled, honour withdrawals and erasure requests, and how face data is deleted.
List enrolled guests#
GET /v1/events/{eventId}/enrolments →
Returns ticket numbers, when and how each guest enrolled (Widget, Dashboard or Api) and their consent version — never face data. Newest first, 100 per page; ?search= matches ticket numbers.
Remove a guest#
When a guest withdraws consent or asks for their data to be erased, remove their enrolment. It takes effect immediately; gate devices drop it at their next sync.
DELETE /v1/events/{eventId}/enrolments/{ticketId} →
Deletion is automatic#
| What | Deleted |
|---|---|
| The photo | Straight away — it is never stored |
| Face templates and consent records | When the event's retention ends: event end + retentionDays (0–30, default 7) |
| Copies on gate devices | At the same time — even offline — or when you revoke the device |
| Everything for an event | Immediately when you delete the event |
Every deletion is recorded in your deletion log (Dashboard): what was deleted, when and why — never who. Use it to show a regulator or a guest that retention is enforced.
Usage and billing#
Each guest's first enrolment on an event counts once towards your plan, even if they're later removed (billing records hold no face data). See Dashboard → Plan → Usage for this period's total and the per-event breakdown.