Facial Verification / Liveness Notice
Covers the selfie and liveness step used to confirm that the person opening the account is the person on the identity document, and that the capture is live rather than a photograph or recording.
- Dependency class
- B · Provider-dependent
- Needs final payment, KYC, maps, telecom or IoT provider details.
- Consent
- Required acceptance
- Face / liveness check
- Not revocable while the account is active
Version 0.1-draft · v1 Working Draft — frozen
Draft clauses
Facial Verification / Liveness Notice
- 01
Purpose: prevent identity substitution, account sharing, underage riding and stolen-document use.
- 02
Processing: a short capture is compared against the identity document by the verification provider.
- 03
SYIBE receives a match result, a liveness score and a provider reference; it does not use the capture for surveillance, tracking or advertising.
- 04
The check is performed once per verification cycle and repeated only on re-verification, suspicion of fraud or expiry.
- 05
Where a liveness check cannot be completed, a manual review route is offered instead of an automatic permanent rejection.
Open questions for legal review
- Whether local law classifies this as biometric processing requiring specific consent language.
- Provider retention of the raw capture and deletion guarantees.
These documents are professional working drafts prepared for the SYIBE operating model. They are not legal advice and are not approved production legal language. Before public launch, every jurisdiction-sensitive document must be reviewed by qualified local legal counsel once the corporate entity, regulatory classification, municipal permissions, insurance structure, payment provider, KYC provider and hardware structure are finalised.