Privacy Policy
What SYIBE collects, why, on what basis, who processes it, how long it is kept, and the rights available to the person it concerns. Written against the actual platform architecture, not a generic template.
- Dependency class
- C · Jurisdiction-dependent
- Needs Syrian/local legal review or country-specific adaptation.
- Consent
- Required acceptance
- Sign-up
- Not revocable while the account is active
Version 0.1-draft · v1 Working Draft — frozen
Draft clauses
Privacy Policy
- 01
Categories collected: account and phone data, identity documents, verification results, device information, precise location, ride routes, payment and wallet data, parking and incident photographs, support communications, fraud and security signals, vehicle telemetry and product analytics.
- 02
Purpose limitation: each category is tied to a stated purpose — eligibility, safety, ride delivery, billing, dispute handling, fraud prevention, service improvement or legal obligation.
- 03
Data minimisation: SYIBE stores verification references, status and results from providers rather than retaining unnecessary raw biometric material.
- 04
Processors: identity verification, payment, messaging, mapping, hosting, push and monitoring providers act under contract and only for defined purposes.
- 05
Retention: each category has a defined retention period; ride and financial records are kept as long as required for accounting, dispute and legal purposes.
- 06
Rights: access, correction, deletion, objection to marketing, withdrawal of optional consent, and complaint routes.
- 07
Security: encryption in transit, restricted internal access by role, audit logging of privileged actions.
Open questions for legal review
- Applicable Syrian data-protection obligations and any registration or notification duty.
- Final processor list, hosting locations and cross-border transfer basis once providers are selected.
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.