Privacy Policy

1. Who is responsible for your data

The operator of the Raahi controlled pilot is responsible for deciding how personal data is used for the service. Public ride transactions are currently disabled except for authorized acceptance-testing accounts. Privacy questions and requests can be submitted through Contact Raahi. Before public ride transactions are enabled, Raahi will publish the operator’s formal legal identity, principal business address and designated privacy/grievance contact.

Raahi intends to follow the Digital Personal Data Protection Act, 2023 and applicable rules as their provisions become applicable, together with other privacy, consumer and transport-related obligations that apply to the service.

2. Data Raahi may collect or receive

• Google sign-in identity, account identifier, display name, email and authentication/session information.
• Mobile number, phone-verification status and related authentication events.
• Role information, account status, restrictions, preferences and service settings.
• Shared Ride routes, pickup stops, seat selections, booking states, fare snapshots and trip/service events.
• Outstation pickup area, exact pickup text, destination, dates, passenger count, notes, Driver quotes and accepted-booking details.
• Driver profile, vehicle details and verification material such as Driving Licence, RC and car photographs.
• GPS/location and time data where used for current stand, active-trip operations, live location, route progress or safety features.
• Support cases, complaints, contact messages, audit/security events and records needed to investigate misuse or service problems.

3. How Raahi obtains data

Data may come directly from you, from your device, from your Google authentication session, from Drivers/Passengers interacting with the same trip, from Raahi Admin review, or from service providers used for hosting, authentication, messaging, maps and related infrastructure.

Raahi does not ask users to upload Driver verification documents into public profile fields. Sensitive verification files are handled through restricted verification workflows.

4. Why Raahi uses personal data

• authenticate users and maintain one operational role per account;
• verify phone numbers and protect transactional actions from fake or abusive use;
• coordinate Shared Ride seats, routes, FIFO, trip progress and payment/booking state;
• match Outstation requests to eligible Drivers and show/accept quotes;
• review Driver and vehicle verification and display appropriate trust indicators;
• provide location-based trip features and safety/support functions;
• prevent fraud, abuse, queue manipulation, unauthorized access and other misuse;
• respond to support, complaints, disputes, legal requests and regulatory obligations; and
• measure aggregate service health and improve local mobility reliability.

5. Legal basis and consent

Where applicable law requires consent, Raahi will seek clear consent for the relevant processing and record it where appropriate. Some processing may instead be necessary to provide a service you requested, comply with law, protect users, prevent fraud, respond to emergencies, or rely on another basis permitted by applicable law.

Accepting the Terms does not mean you consent to every imaginable use of your data. Raahi should provide separate notice or consent where the law requires it for a materially different purpose.

6. Contact sharing and visibility

Raahi follows a stage-based privacy model. Contact details are not intended to be broadly visible before they are operationally needed.

• For Outstation, Driver and Passenger phone details are intended to become visible after a Driver quote is accepted.
• Passengers may see Driver name, vehicle details, verification status and approved car photographs as part of trust and booking decisions.
• Licence and RC scans are not shown to passengers merely because a Driver is verified.
• Drivers may see pickup/destination and other request information needed to decide whether to serve a lead, subject to the privacy boundaries built into the service.
• Shared-trip links may expose limited trip/location information to the person holding a valid link until the link expires or is revoked.

7. Location and GPS

Raahi may use location for current-stand selection, route eligibility, active-trip GPS, Passenger trip progress, shared-trip safety features and aggregate local-demand understanding. Location data may be approximate or delayed.

Raahi’s launch policy is not to build unrelated individualized advertising profiles from a person’s trip or location history. Aggregate, de-identified or privacy-aware mobility insights may be used to improve service planning, understand corridor demand and decide where Raahi should expand, subject to applicable law.

8. Service providers

Raahi may use service providers for cloud/database infrastructure, authentication, hosting, maps, communications/OTP transport, monitoring and other operational functions. Providers should receive only the access reasonably needed for their function and be subject to contractual/security controls appropriate to the data involved.

Where personal data is processed outside India or across jurisdictions, Raahi will comply with transfer restrictions and other requirements that apply at the relevant time.

9. When Raahi may disclose data

Raahi may disclose information to another Passenger or Driver where the service stage requires it; to service providers operating Raahi; to law-enforcement, courts, regulators or other authorities where legally required; or where reasonably necessary to investigate fraud, protect safety, respond to an emergency or establish/defend legal claims.

Raahi does not sell personal data to advertisers. Local Offers may be shown without giving the advertiser a Passenger’s individual trip history or contact details unless the user separately chooses to contact that business.

10. Retention

Raahi keeps personal data only for as long as reasonably needed for the purpose for which it was collected and for safety, dispute handling, fraud prevention, audit, legal, accounting or regulatory requirements. Different categories may have different retention periods.

Active-trip GPS should not be retained indefinitely merely because it was collected. Verification and transaction records may need longer retention where they support legal, safety or audit obligations. Counsel should confirm the final retention schedule before scale-up.

11. Security

Raahi uses technical and operational safeguards intended to limit unauthorized access, including authenticated role boundaries, restricted document access, server-side business rules, audit history and environment/secret controls. No internet service can guarantee absolute security.

If Raahi becomes aware of a personal-data breach, it will investigate and make notices or reports required by applicable law.

12. Your privacy choices and rights

Depending on applicable law and the stage of its commencement, you may have rights relating to access to information, correction, completion, erasure, withdrawal of consent, grievance redressal and nomination or other statutory rights.

Requests can be made through Contact Raahi until a dedicated privacy channel is published. Raahi may need to verify the requester’s identity. Some information may be retained despite a deletion request where lawfully necessary for safety, fraud prevention, legal claims, audit or another permitted purpose.

13. Children

Raahi is not designed for independent transactional use by a person who is not legally competent to make the relevant arrangement. Where a child travels, a responsible adult should make and supervise the arrangement as required by law.

If Raahi later introduces a feature specifically directed to children, schools or guardians, that feature should have its own privacy and consent controls rather than relying only on this general Policy.

14. Local Offers and analytics

Raahi may measure aggregate usage, route demand, service-area activity and feature performance to improve the service and support Raahi’s local economic model. Local Offers may be contextual to a place or service area without creating an individualized advertising profile from a user’s private trip history.

If Raahi later introduces materially different advertising, tracking or personalization, this Policy and any required consent controls should be updated before that use begins.

15. Changes to this Policy

Material changes will be identified by a new policy version. Raahi may require acknowledgement of the new version before the next protected Passenger or Driver transaction. Historic acceptance timestamps may be retained as audit evidence.

16. Privacy and grievance contact

During the controlled pilot, use Contact Raahi for privacy questions, correction or deletion requests, or complaints.

Before public ride transactions are enabled, Raahi will publish the operator’s formal legal identity, principal business address and designated privacy/grievance contact here and keep those details aligned with the Terms of Service.