DMDriveMe Privacy

PURPOSE LIMITATION

Privacy and data-use framework

Operational draft requiring approval against applicable data-protection law.

Data categories

Account, identity result, driver qualification, vehicle, assignment, passenger authorization, location, custody, payment reference, incident, support and audit data.

Purposes

Service execution, identity and authority verification, safety, matching, payment, support, fraud prevention, legal compliance and evidence-backed dispute handling.

Minimization

Drivers and providers receive only information required for their current role and active assignment. Raw identity documents and high-frequency telemetry should not be retained longer than justified.

Sharing

Data may be shared with authorized participants and bounded providers for identity, maps, notifications, payments, insurance or legal obligations. Provider-specific credentials must not enter application logs.

Security

Role boundaries, encryption, scoped credentials, private evidence storage, audit logs and session controls protect information according to sensitivity.

User rights

Access, correction, objection, deletion and portability requests are handled subject to applicable law and justified safety, financial, evidence and legal retention duties.

Policy approval gate

Retention periods, controller/processor roles, lawful bases, cross-border transfers, data-subject procedures and regulator contacts must be completed for the launch jurisdiction.