Privacy Policy
This document is a draft. The items marked like [COMPANY-NAME] must be filled in, and the whole policy must be reviewed by a qualified person before it is published.
1. Who we are
[COMPANY-NAME] ("we", "us") operates the Ridehail customer app, the Ridehail Driver app, and the services behind them (together, the "Service"). This policy explains what personal data the Service collects, why, and what happens to it. For anything not answered here, write to [SUPPORT-EMAIL].
2. Information we collect
- Phone number. Sign-in is by one-time password (OTP) sent to your phone number. The number identifies your account; there are no passwords for rider or driver accounts.
- Profile details. Name, email address, and an optional avatar photo, if you choose to add them.
- Rider location (foreground only). The customer app uses your precise location while you are booking a ride and while a ride is in progress, to set your pickup point and show the trip on the map. It does not track riders in the background.
- Driver location (background, while online). The driver app reports the driver's precise location roughly every 4 seconds while the driver is online and available for rides, including when the app is in the background. This runs through a visible foreground service (a persistent notification on the phone) and stops when the driver goes offline. It powers dispatch, live trip tracking, and fare calculation.
- Driver identity documents. Drivers upload identity and vehicle documents — driving licence and vehicle registration certificate (RC), including document photos — for verification before they can accept rides.
- Emergency contacts. Names and phone numbers of trusted contacts you add. This is information about other people, so add only contacts who agree to receive alerts from us. It is used for one purpose: when you trigger SOS, we alert those contacts by SMS with your location and a live trip-tracking link.
- Ride records. Ride history, pickup and drop locations and addresses, fares, ratings you give and receive, and tips.
- In-ride chat. Messages exchanged between rider and driver about an ongoing ride.
- SOS events. When you trigger SOS we record the time, your location, and the ride it relates to, and share it with our safety/operations team.
- Push notification tokens. A device token (Firebase Cloud Messaging) so we can send ride updates and alerts to your phone.
3. What we do not collect
- No payment instruments. Rides are paid in cash, directly to the driver. We do not collect card numbers, UPI handles, or bank details from riders.
- No advertising. The apps contain no ads and no advertising identifiers.
- No analytics or tracking SDKs. The apps do not embed third-party analytics, profiling, or tracking libraries.
- We do not sell personal data to anyone.
4. How we use it
We use the data above to operate the Service: signing you in, matching riders to nearby drivers, navigating and tracking trips, calculating fares, verifying drivers, handling SOS alerts, sending ride notifications, keeping ride history and receipts, resolving support requests, and preventing fraud and abuse.
5. Who it is shared with
- Between rider and driver. A driver sees the rider's name, pickup/drop points, and chat messages for the assigned ride; a rider sees the driver's name, photo, vehicle details, ratings, and live location during the trip.
- Your emergency contacts. Only when you trigger SOS: an SMS with your name, approximate location, and a live-tracking link. Anyone you share a trip-tracking link with (directly or through SOS) can see that trip's live location while the link is active.
- Service providers. An SMS gateway (MSG91) delivers OTPs and SOS alerts; Google Firebase Cloud Messaging delivers push notifications. They process the minimum data needed to deliver those messages.
- Legal requirements. We may disclose data where the law requires it, or to protect the safety of riders, drivers, or the public.
6. Retention and deletion
You can delete your account from inside the app (Profile → Delete account). Deletion is immediate for access: the account is marked deleted and can no longer be used to sign in. Underlying records are then retained for a limited period — because ride, fare, and safety records may be needed for legal compliance, dispute resolution, and fraud prevention — after which they are removed or anonymised. If you want a deletion request handled manually, or want data corrected, contact [SUPPORT-EMAIL].
7. Security
Data is transmitted to our servers over authenticated sessions and stored on access-controlled infrastructure. Driver documents are accessible only to our verification staff. No system is perfectly secure; if we learn of a breach affecting your data we will notify you as required by law.
8. Your rights
Subject to applicable law — including India's Digital Personal Data Protection Act, 2023 — you may request access to, correction of, or deletion of your personal data, and you may withdraw consent for processing that is based on consent (which may mean parts of the Service stop working, e.g. location-based dispatch). Requests go to [SUPPORT-EMAIL].
9. Children
The Service is not directed at children and requires users to be at least 18 years old.
10. Changes to this policy
If this policy changes materially we will update this page and change the effective date above, and notify you in the app where the change is significant.
11. Contact
[COMPANY-NAME] — [SUPPORT-EMAIL]