Faceify

Faceify — On-Device Biometric

Face templates never leave the device. Only a UUID + boolean reaches the cloud.
✅ DPDP FULLY COMPLIANT — PRIVACY BY DESIGN
📷 Live Camera Feed — On-Device Processing Only
📷
Camera initializing…
Allow camera access when prompted
INITIALIZING…
⚠️ Not Enrolled — Run Enrollment First
📋 Activity Log
[SYSTEM] Faceify ready. On-device processing mode ACTIVE.
[SECURE] Biometric data stays on this device — zero cloud exposure.

🔒 PRIVACY PROTECTION STATUS

Consent — pending enrollment
Face template — not created
Anonymous UUID — not assigned
Local .dat file — not created
Cloud template backup — pending
☁️ S3: waiting for enrollment…
§4 Compliant §8 Compliant §6 Compliant §16 Compliant §22 Privacy by Design
☁️ S3 Template Backup — faceify-nexora-demo/
No templates uploaded yet — enrollment will upload a JSON template (not a photo)
What goes to the cloud during attendance:
Only { uuid: "a3f7b291…", present: true, ts: "2025-05-25T…" } — two anonymous values with no biometric data. Even if every network packet is intercepted, nothing about the person's face is exposed. The S3 backup above is a mathematical embedding — it cannot be used to reconstruct the original face.