Privacy and compliance
Who's responsible for what, the consent wording, and what FacePing enforces for you.
Face templates are biometric data. FacePing is built so the lawful way is the default way. But as the business running check-in (an event organiser, gym, club or venue), you are the controller and FacePing (Wiretouch Ltd) is your processor.
What FacePing enforces#
- 1:1 verification by default: the device checks the face against the person whose ID was scanned, and no one else.
- Every list must offer a way to check in without face matching.
- No consent, no processing: consent is checked before a photo is decoded. Photos are never stored.
- Face data is deleted on a fixed schedule, on the server and on every device, and each deletion is logged (see Retention).
- Data stays in your region. Check-in devices hold only their own list, encrypted, on a 24-hour lease.
- In the sandbox, faces enrolled with the SDK stay on the test device and never reach FacePing. Faces on your sandbox's practice check-in list (the server API with a sandbox key) are held by FacePing like a live list's, and deleted 24 hours after enrolment. The practice list is for testing with yourself and colleagues who agree to it, not real customers.
- FacePing staff can see your dashboard only in a read-only support view, for up to an hour, when helping you. Every view is listed for you under Support access in Data & compliance (in the sandbox, Settings shows it too).
Retention#
Everyone you enrol belongs to a check-in list. How long their face data is kept depends on the kind of list:
- A list with an end date (a show, a festival, a course): everyone's face data is deleted 0 to 30 days after the list ends (
retentionDays, default 7). For example, a festival ending on 9 August with 7 days' retention is deleted on 16 August. - An ongoing list (gym members, visitors): each person's face data is deleted at most 1 to 36 months after they enrolled (
maxAgeMonths, required in the API; the dashboard suggests 12), or sooner when you remove them. For example, a member who enrols on 3 March with 12 months is deleted on 3 March next year at the latest, and can enrol again. These deletions appear in your deletion log asMaxAgeReached.
FacePing never collects check-in logs (checks happen offline on the device), so an ongoing list's clock runs from enrolment, not from the last visit. Removing someone through the dashboard or API deletes their face data at once. Check-in devices drop faces at their next sync, and never keep a face past its deletion date. Our own biometric data retention schedule is public, so you can link to it from your privacy notice.
What you do#
- Complete a DPIA before you go live, using our template: it's in your sandbox dashboard now, under Data & compliance.
- Publish a face check-in privacy notice and link it in Dashboard → Settings once you're live (or per list, if a list needs its own).
- Offer, and staff, a standard (non-face) way to check in, every time.
- Honour withdrawals and erasure requests (remove someone).
- Read our data processing agreement. It's part of the sandbox terms you accept at sign-up (for your practice list), and of the customer agreement you sign when we approve your application to go live.
Download the compliance pack from Dashboard → Data & compliance, in the sandbox or once you're live: the data processing agreement, sub-processor list, DPIA template, privacy notice template and consent wording. The data processing agreement and sub-processor list are also public.
Workplace use#
Our standard terms and consent wording cover checking in ticket holders, members and visitors. They don't cover using FacePing with your own employees or contractors, for attendance, timekeeping, shift records or workplace access. Employment brings extra legal duties, and people at work may not feel free to say no.
If you're considering workplace use, talk to us before you build. We review it separately, and it needs its own terms and consent wording. As a minimum we'd expect:
- a non-face way to clock in or get in that staff can choose at any time, with no penalty and no extra effort;
- a data protection impact assessment before anyone enrols;
- a staff notice, retention that matches your HR policy, and deletion when someone leaves;
- consultation with staff representatives or a works council where the law requires it;
- in the US, each person's written release under the state laws that apply.
We don't currently accept workplace use for employees or contractors in Illinois.
Consent wording#
The widget shows this wording, filled in with your organisation name, the list name and when the face data is deleted. The list is whatever you check people in to: a show, a gym, a venue. Use the same words, and the same version id, if you collect consent yourself.
To show the wording yourself (on your own sign-up page or at a front desk), GET /v1/lists/{listId}/consent returns it filled in for the list, with its consentVersion.
UK (uk-v1) and EU (eu-v1): two separate, unticked boxes:
I agree to [organisation name] using my face data to confirm it's me at entry. My photo will be turned into a face template, used only for entry to [list name], and deleted [when]. I can withdraw at any time and use the standard entrance instead.
I have read the face check-in privacy notice.
[when] is "7 days after it ends" for a list with an end date (or "1 day after it ends", or "as soon as it ends" with 0 days' retention), and "12 months after today at the latest, or sooner if I leave" for an ongoing list (with your number of months).
US (us-v1): two separate, unticked boxes, the written biometric release and the privacy notice confirmation:
Biometric data release. I authorise [organisation name] and its service provider Wiretouch Ltd (FacePing) to create and store a face template (biometric identifier) from the photo I provide, for the sole purpose of verifying my identity when I enter [list name]. It will be permanently destroyed [when], under the published retention schedule. It will not be sold, leased, traded or shared, and I can withdraw at any time. Using face check-in is optional.
I have read the face check-in privacy notice.
[when] is "7 days after [list name] ends, and in any case no later than 30 days after it ends" for a list with an end date (or "1 day after", or "as soon as [list name] ends"), and "12 months after today at the latest, or sooner if I leave" for an ongoing list.
Under 16s: a parent or guardian agrees on their behalf: "I am the parent or guardian of the person checking in. I agree to the statements above on their behalf, where 'me' and 'my' mean them."
There is one wording per region: uk-v1, eu-v1 and us-v1. On a sandbox practice list, [when] is "24 hours after I enrol (this is a sandbox test)".
What each consent field records#
When you enrol someone from your server, send what they agreed to in consent (the widget does this for you):
| Field | What it records | UK and EU (uk-v1, eu-v1) |
US (us-v1) |
|---|---|---|---|
consentVersion |
The wording they were shown | The list's consentVersion |
The list's consentVersion |
givenAt |
When they agreed (missing gets 400) |
Required | Required |
explicitBiometricConsent |
They ticked the consent statement (the "I agree…" box, or for the US the release) | Required, true |
Required, true |
writtenRelease |
They signed the US written biometric release (the same tick as the release statement) | Not used (send false or leave it out) |
Required, true |
under16 |
The person is under 16 | Optional, true or false (default false) |
Optional, true or false (default false) |
guardianConsent |
A parent or guardian ticked the guardian statement | Required, true, when under16 is true; otherwise leave it out |
Required, true, when under16 is true; otherwise leave it out |
How the ticks map to the fields, for every version: the first tick (the "I agree…" statement, or for the US the release) sets explicitBiometricConsent; for us-v1 the same tick is the written release, so it sets writtenRelease too. If you collect consent yourself for a US list, send both true when the person ticks the release.
The privacy notice box ("I have read the face check-in privacy notice") is the second tick on the enrolment page, which won't go on until both boxes are ticked. When you collect consent yourself, show your privacy notice and record that the person read it in your own records; it isn't a field in the request.
Which wording people see#
The wording follows the list's country (set when you create the list, in the dashboard or with country in the API):
| List country | Version | Wording |
|---|---|---|
United States (US) |
us-v1 |
US biometric data release (a BIPA style written release) |
| EU and EEA countries (the 27 EU members plus Iceland, Liechtenstein and Norway) | eu-v1 |
EU wording |
| Anywhere else, the UK included | uk-v1 |
UK wording |
A list with no country follows your account's country (from your application to go live), and an account with no country on record follows its billing currency (pounds uk-v1, euros eu-v1, dollars us-v1). Each list's consentVersion in the API shows the version in use. The country can't change once people have enrolled, so everyone on a list agrees to the same wording. Setting each list's country correctly is your responsibility under the data processing agreement (clause 6.1.7).
Your privacy notice#
Your notice should cover: who you are and how to contact you; that face check-in is optional and how to check in without it; that the photo becomes a face template and isn't kept; that it's used only for check-in; the lawful basis (explicit consent); that FacePing processes it for you, in which region; when it's deleted; and how to withdraw or exercise rights. The compliance pack includes a ready-to-edit template.