Privacy Policy

How Turrant collects, uses, stores, and protects your personal data.

Effective: 26 May 2026 Version: 1.0 Governing law: India
Short version. Turrant collects only the personal data we need to operate an intercity ride-sharing platform safely. Your data stays in India by default. We don't sell it. You can read it, correct it, or delete it anytime by contacting our grievance officer below.

1. Who we are

"Turrant" refers to Turrant Mobility Pvt. Ltd. (the "Company", "we", "us"), the operator of the Turrant intercity ride-sharing platform at turrant.taxi. We are a Motor Vehicle Aggregator licensed under the Motor Vehicle Aggregator Guidelines, 2025 ("MVAG 2025") and process personal data as a Data Fiduciary under the Digital Personal Data Protection Act, 2023 ("DPDP 2023").

This policy applies to: passengers, drivers, fleet owners, and anyone who visits turrant.taxi or uses our apps.

2. What data we collect

For passengers

For drivers + fleet owners

What we don't collect

3. How we use your data

We use personal data only for these specific purposes:

We do not use your data for behavioural advertising, sell or rent it to third-party brokers, or share it with any party except the limited list in section 6 below.

4. Where your data lives

By default, all personal data is stored on servers physically located in India. We use AWS Mumbai (ap-south-1) as our primary infrastructure, in line with the spirit of DPDP 2023's localisation guidance.

AI-assisted services — limited cross-border processing

Some platform features use AI services that may process your data outside India. Here is the current, accurate picture of who processes what, and where:

ProviderUsed forWhere data goes
AWS Bedrock (Mumbai)Aadhaar, PAN and bank-proof document verificationIndia (ap-south-1) — these documents do not leave India. While this India service is being provisioned, Aadhaar / PAN / bank-proof OCR is done manually rather than routed abroad.
Anthropic (Claude)Driving-licence / RC / insurance field extraction, driver-identity face match and number-plate reading (safety check at pickup), customer-support drafts, reported-issue triage, marketing copy suggestionsUSA — opt-out of training; short retention; SOC 2. We are migrating the face-match and plate-reading steps to AWS Bedrock Mumbai (India).
Google AI StudioMarketing campaign image generation only — never your personal dataUSA / EU — opt-out of training; short retention

Your most sensitive documents (Aadhaar, PAN, bank account) are never processed outside India — they are handled exclusively through AWS Bedrock Mumbai once provisioned, and manually until then. Other verifications and the pickup safety check may currently use Anthropic's API (USA) while we complete the migration to India-based processing. You can disable AI-assisted verification on your account by writing to our grievance officer (section 8) — we will verify your documents manually instead.

5. How long we keep it

You can request earlier deletion of personal identifiers by writing to the grievance officer; we will comply unless a specific law requires us to retain the data longer.

6. Who we share data with

We share your personal data only with the following categories of third parties, and only as needed:

CategoryExample partnersWhat we share
Identity verificationUIDAI / DigiLocker, Parivahan, NSDL PAN, OnGrid (BGV), Karza / IdfyDriver/owner Aadhaar, PAN, driving licence, RC numbers — for verification only
MessagingMeta (WhatsApp Business), MSG91, Amazon SES, SendGrid, ResendYour phone / email + the message content (OTPs, trip updates, invoices)
PaymentsRazorpayTrip amount + your phone/email for invoice; never raw card data
Mapping + GPSGoogle Maps, Mappls (planned)Pickup + drop coordinates for route calculation
Cloud infrastructureAWS (ap-south-1, Mumbai)All platform data — processed under AWS's standard data-processing terms
One-tap login (passengers)WhatsApp (Meta), TruecallerYour phone number + display name, only at the moment you tap the login button
AI assistanceAnthropic (Claude), AWS Bedrock (Mumbai), Google AI StudioPer section 4 above — document text, pickup safety-check images, and (never personal data) marketing image prompts
Government + law-enforcementPolice, RTO, traffic authorities, GST authority, courtsOnly when served with a valid legal order, or to investigate a safety incident on the platform

Each of these parties processes your data under their own privacy obligations + a written contract with Turrant requiring them to use it only for the agreed purpose.

7. Your rights under DPDP 2023

You can, at any time, ask us to:

To exercise any of these rights, write to our grievance officer below. We respond within 30 days (often faster).

8. Grievance officer + contact

Grievance Officer

Per Rule 5 of the IT Rules 2021 + DPDP 2023, we maintain a named grievance officer who handles all privacy-related requests and complaints.

Email: grievance@turrant.taxi
Subject line: "DPDP request — <your phone number>"
Response time: within 30 calendar days (typically 3–7).

If you are not satisfied with our response, you may escalate to the Data Protection Board of India (once it is functional) or the Ministry of Electronics and IT.

9. Children's data

Turrant is not intended for children under 18. We do not knowingly collect personal data from anyone we believe to be a minor. If a parent or guardian becomes aware that a minor has created a Turrant account, please email grievance@turrant.taxi and we will delete the account within 7 days.

10. Cookies + tracking

Our website (turrant.taxi) uses only essential first-party cookies for session management and security. We do not use third-party advertising cookies, behavioural-targeting pixels, or cross-site trackers. The site also does not embed Google Analytics, Facebook Pixel, or similar trackers.

11. Changes to this policy

When we update this policy, the new "Effective" date at the top will change. Material changes will trigger an in-app + email notification asking you to re-consent before continuing to use Turrant. Minor wording changes (clarifications, typo fixes) will not trigger a re-consent.

Historical versions are archived; on request the grievance officer will share the version that was in effect on any specific date.