KYC / Identity Verification Notice
Explains why identity verification is required before the first ride, what documents are processed, who performs the check, what SYIBE keeps, and what happens if verification fails.
- Dependency class
- B · Provider-dependent
- Needs final payment, KYC, maps, telecom or IoT provider details.
- Consent
- Required acceptance
- Identity verification
- Not revocable while the account is active
Version 0.1-draft · v1 Working Draft — frozen
Draft clauses
KYC / Identity Verification Notice
- 01
Purpose: age and eligibility confirmation, safety, fraud and theft prevention, and accountability for vehicle use.
- 02
Data processed: national ID or passport details, document images, and the verification decision.
- 03
SYIBE stores the verification status, provider reference, decision and expiry — not an unnecessary copy of the document where the provider retains it.
- 04
Outcome: verified, pending manual review, or rejected with a reason and an appeal route.
- 05
Refusal to verify prevents riding but does not prevent account deletion.
Open questions for legal review
- Selected KYC provider, its retention behaviour and data location.
- Whether local rules require a specific document type or registry check.
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.