Face data — privacy by design
How EventKH handles biometric data for face check-in.
🏛️ On-premise only
Face templates (mathematical embeddings — not reversible images) and enrolment photos are stored solely in EventKH's own database, on your infrastructure. Nothing is sent to any third party or cloud.
🔒 Encrypted at rest
Every face embedding is encrypted with AES (Fernet) in the database. The key lives on the server and is never exposed to the browser.
✋ Consent & optional
Face enrolment is opt-in and consented. Face check-in is always optional — a QR ticket works for everyone, so no one is required to give biometric data.
🗑️ Right to erasure
You can remove your own face anytime (My dashboard → Remove). Administrators can purge all face data, and embeddings can be retained only for an event and deleted afterwards.
What is stored
| Data | Purpose | Protection |
|---|---|---|
| Face embedding | Match you at check-in | Encrypted (AES), on-prem |
| Enrolment photo | Confirm identity on the dashboard | Local file, purgeable |
| Liveness check | Reject photo/screen spoofing | Frames processed in-memory, not stored |
| Check-in record | Attendance | Name + time + method only |