Data categories, retention, controls

• Identity data: name, phone, email, DOB, profile photo, OTP records, and language preferences.
• Driver verification data: license/identity documents, vehicle RC/permit/insurance details, vehicle photos, payment settings, onboarding status, and admin decisions.
• Ride data: pickup, destination, route, fare, vehicle type, ride status, cancellation details, PINs, ratings, support reports, and notifications.
• Financial data: per-ride fee and insurance charges, outstanding dues and their clearance records, settlement workflow, and payment provider references.
• Technical data: logs, device metadata, crash reports, notification tokens, web form submissions, and admin audit records.

Account and ride records are retained for as long as the account is active and then for a reasonable period needed for support, safety, fraud prevention, dispute resolution, tax/accounting, and legal obligations. Driver verification records may be retained longer because they support platform safety and regulatory review.

Operational records are grouped by purpose: active service data while the account is live, support and dispute data while an issue is open, financial records while per-ride fee, insurance, dues, and settlement entries may be audited, and safety records while a complaint, incident, or policy review may be investigated.

• Per-ride charges include the flat fee and insurance amount, ride/account context, transaction status, and the resulting dues balance.
• Dues records track amounts charged after each completed ride and their clearance by the next day, including payment provider reference and status where applicable.
• Settlement records include account deactivation status, outstanding dues, pending disputes, saved payout details, admin decision, settlement status, and notification history.
• Rider-to-driver payment details may include the driver's configured payment identifiers, payment phone, or other payment instructions shown to the rider during an active ride.

Ride trace data may include driver coordinates, rider pickup and destination points, route/polyline context, timestamps, ride status transitions, cancellation actor, and distance estimates. This data supports live tracking, fare checks, safety review, cancellation review, and support resolution.

Admin and operations access should be role-based. Sensitive document, fee and dues, payment, support, and safety workflows should be visible only to authorized team members. Admin actions should be logged with actor, timestamp, decision, and relevant notes.

Data questions can be sent to narenderv7@gmail.com. Include your registered phone number and whether you are a rider, driver partner, website lead, or admin contact.