Legal

Privacy Policy

This explains what personal data SnappCab collects, why, who we share it with, how long we keep it, and what you can ask us to do about it. It is written to meet the Digital Personal Data Protection Act, 2023.

Version 1.2Effective 18 October 2026

Read the full policyYour rights

Why we collect it

Every purpose, and exactly what it uses.

Nothing is collected without a stated reason. This is the same table as § Why we collect it in the full policy below.

  • Signing you in and keeping your account secure

    What it usesMobile number, email, device and login history

  • Matching you with a nearby captain, and navigating the trip

    What it usesLocation, trip details

  • Calculating and collecting the fare

    What it usesTrip distance and duration, payment information

  • Safety — SOS response, trip sharing, and investigating incidents

    What it usesLocation, trip history, chat and call metadata

  • Confirming that a captain reached the pickup, each stop and the destination, and noticing when a trip leaves its route or stops for long — the basis for waiting charges, “rider didn’t come” and safety check-ins

    What it usesCaptain location during a trip, the planned route

  • Helping your captain find you, stopping a trip being ended as “rider didn’t come” while you are at the pickup, placing an SOS, and noticing if you and your captain are far apart

    What it usesYour location during a live trip — only if you share it; never for pricing or marketing

All 16 purposesFewer purposes
  • Telling the person you booked for, or your parcel’s receiver, about that trip or parcel

    What it usesThe name and mobile number you entered for them

  • Finding the place you said out loud

    What it usesThe text of your voice search (never the recording)

  • Confirming a rider’s gender for women-only rides

    What it usesGender, the ID photo you upload

  • Tracking a captain’s location while online without draining the battery

    What it usesMotion and activity detection on the captain’s phone

  • Verifying that a captain is who they say they are and is allowed to drive

    What it usesVerification documents, identity data, liveness video, date of birth

  • Paying captains

    What it usesEarnings and settlement data

  • Answering support requests and grievances

    What it usesCorrespondence, trip history

  • Detecting fraud and abuse

    What it usesDevice, login and trip patterns

  • Finding and fixing crashes, errors and slowness

    What it usesCrash, error and performance reports

  • Meeting legal, tax and regulatory obligations

    What it usesTrip and payment records

We do not sell your personal data. We do not use your trip history to build advertising profiles, and we do not share it with advertisers.

Contents
  1. Who we are
  2. What we collect
  3. Why we collect it
  4. Our lawful basis
  5. Who we share it with
  6. How long we keep it
  7. Your rights
  8. How we protect it
  9. Children's data
  10. Cookies
  11. Transfers outside India
  12. Changes to this policy
  13. Contact and grievances

Who we are

SnappCab is a ride-hailing service operated by Omnius Cloud Private Limited ("we", "us"). For the purposes of the Digital Personal Data Protection Act, 2023 (the "DPDP Act"), we are the Data Fiduciary for the personal data described below, and you are the Data Principal.

  • Registered office: S/O Ghulam Nabi Wali, B-4, Gali No. 18, Zakir Nagar, South Delhi, Delhi 110025, India
  • Head office: S/O Ghulam Nabi Wali, B-4, Gali No. 18, Zakir Nagar, South Delhi, Delhi 110025, India
  • CIN: U62099DL2024PTC435292
  • Data protection contact: privacy@snappcab.in

What we collect

We collect only what the service actually needs. What that is depends on whether you use SnappCab as a rider or drive with us as a captain.

From everyone

  • Identity and contact details — your name, mobile number, email address and profile photo if you add one.
  • Device and login history — the devices you sign in from, and the IP address and time of each sign-in, together with the approximate area that address points to — worked out from the address, not from your phone's location. We keep this so you can see where your account is being used and so we can detect someone else using it.
  • Crash, error and performance reports — when the app or website fails, the error, where in our code it happened, the app version, and your phone's model and operating-system version (on the website, your browser and its version). We also record how long screens, pages and requests take, which screen or page they belong to, and our servers' operational logs. Before any of this leaves your device or our servers we strip names, phone numbers, email addresses, account IDs, one-time codes, document numbers and sign-in tokens, and cut any location to about a kilometre. A report can carry an internal trip or request reference so we can follow a fault through our systems, but not who you are.
  • Support correspondence — what you write to us, and our replies.

From riders

  • Location — your pickup and destination. And, only if you turn it on, your phone's position during a live trip while the app is open: never before you book, never after the trip, never in the background. You can turn it off at any time in Settings › Privacy.
  • Trip history — where you went, when, in which vehicle, with which captain, and what you paid.
  • Gender and date of birth — only if you add them; both are optional for riders. Your gender lets you ask for a woman captain only.
  • Payment information — how you paid, and the transaction reference. Today you pay in cash, or by UPI straight to your captain; paying online in the app is coming soon. If you save a UPI ID we store the UPI address and the nickname you give it. We do not store card numbers. No card details are held by SnappCab at all.
  • Saved places — any addresses you choose to save.
  • Someone else's name and mobile number — when you book a ride for another person, or send a parcel, you can enter the name and number of the person riding or receiving it. We use them only to contact that person about that trip or parcel, by SMS, and keep them with the trip record. If you choose to save them for next time, they stay in your account until you remove them. Please enter someone's details only if they are happy for you to.
  • Voice search — only if you tap the microphone in the search box. What you say goes to your phone's own speech service (Google on Android, Apple on iOS), which turns it into text; if you have installed your phone's offline speech packs, that happens on the phone itself. The recording never reaches SnappCab. We receive only the text, and use it as a search, exactly as if you had typed it.
  • ID photo for women-only rides — only if you ask for a woman captain only. You can upload a photo of your government ID (and a selfie) so we can confirm it. Only our verification staff see it, and the photo is deleted automatically 90 days after it is reviewed; we keep the result of the check.
  • In-trip chat — messages exchanged with your captain, and the metadata of any calls made through the app (who called whom, and when — not the content of the call).
  • Ratings and reports — the ratings you give, and anything you report about a trip.

From captains

Everything above where it applies, and in addition — because a person carrying passengers for hire is subject to obligations a rider is not:

  • Verification documents — your driving licence, vehicle registration certificate and insurance certificate. These are checked, and their expiry dates tracked.
  • Identity verification data — including data obtained from an Aadhaar-based electronic verification where you choose that route, and a short liveness video confirming you are the person on the documents.
  • Background location while you are online — this is the significant one, and we want to be plain about it. While you are online and available for trips, the app reports your position even when it is in the background. We need this to offer you nearby trips and to keep a safety trail. It stops when you go offline. You can withhold the permission; you simply won't be able to go online without it.
  • Date of birth — required for captains, to check the minimum age to drive.
  • Motion while you are on duty — while you are online, the app uses your phone's motion and activity detection (the Physical activity permission) to tell whether you are moving or stopped, so it can track your location without draining your battery. We use it for nothing else, and we do not share it.
  • Whether your phone reports a fake location — the app checks for location spoofing, because arrival, waiting and safety all depend on your real position.
  • Earnings and settlement data — what you earned, what has been paid out, and the bank account it was paid to.

Why we collect it

PurposeWhat it uses
Signing you in and keeping your account secureMobile number, email, device and login history
Matching you with a nearby captain, and navigating the tripLocation, trip details
Calculating and collecting the fareTrip distance and duration, payment information
Safety — SOS response, trip sharing, and investigating incidentsLocation, trip history, chat and call metadata
Confirming that a captain reached the pickup, each stop and the destination, and noticing when a trip leaves its route or stops for long — the basis for waiting charges, “rider didn’t come” and safety check-insCaptain location during a trip, the planned route
Helping your captain find you, stopping a trip being ended as “rider didn’t come” while you are at the pickup, placing an SOS, and noticing if you and your captain are far apartYour location during a live trip — only if you share it; never for pricing or marketing
Telling the person you booked for, or your parcel’s receiver, about that trip or parcelThe name and mobile number you entered for them
Finding the place you said out loudThe text of your voice search (never the recording)
Confirming a rider’s gender for women-only ridesGender, the ID photo you upload
Tracking a captain’s location while online without draining the batteryMotion and activity detection on the captain’s phone
Verifying that a captain is who they say they are and is allowed to driveVerification documents, identity data, liveness video, date of birth
Paying captainsEarnings and settlement data
Answering support requests and grievancesCorrespondence, trip history
Detecting fraud and abuseDevice, login and trip patterns
Finding and fixing crashes, errors and slownessCrash, error and performance reports
Meeting legal, tax and regulatory obligationsTrip and payment records

We do not sell your personal data. We do not use your trip history to build advertising profiles, and we do not share it with advertisers.

Our lawful basis

We process personal data on the basis of the consent you give when you create an account and when you grant permissions such as location — and, where the DPDP Act allows, for certain legitimate uses, including complying with a legal obligation and responding to a medical emergency or a threat to safety.

Where we rely on consent, you can withdraw it at any time, and withdrawing it must be as easy as giving it. Some withdrawals stop us being able to provide the service — turning off location means we cannot match you with a captain — and we will tell you when that is the case rather than letting you discover it.

Who we share it with

  • The captain or rider on your trip — your first name, photo, and the pickup and destination. Captains see a rider's number only through a masked connection where masking is available.
  • Payment processors — once paying online in the app is offered (it is coming soon), to take payment and issue refunds. Until then no payment processor receives your data.
  • Google Maps Platform (Google) — our mapping and routing provider, acting for us: it shows the map, finds places you search for, and calculates routes and fare distances from the places and coordinates we send it.
  • MSG91 — our SMS provider, acting for us: it receives the mobile number and the text of each message, to send you one-time sign-in codes and trip updates, and to text the person you booked a ride or sent a parcel for.
  • Firebase Cloud Messaging (Google) — delivers the app's notifications, using a notification token for your device.
  • Identity verification providers — including DigiLocker / API Setu for Aadhaar-based verification where you use it.
  • Google Cloud Vision — captains' registration and insurance documents are passed through an optical-character-recognition service to read the details and expiry dates from them.
  • Sentry (Functional Software, Inc.) — receives the crash, error and performance reports described in section 2, stored in the European Union (Germany), so we can find and fix faults. It is set not to store your IP address.
  • Law enforcement and regulators — where we are legally required to, or where it is necessary to address a threat to someone's safety.
  • Professional advisers and, in the event of a corporate transaction, an acquirer — under confidentiality obligations.

How long we keep it

We keep personal data only as long as the purpose requires, or as long as the law requires us to. The periods below are the ones we apply.

DataRetention
Captain location history while online but not on a trip30 days
Location recorded during a trip (route replay)14 days
Your location during a trip, if you share it14 days
Safety alerts on a trip, and the evidence kept with them180 days
Identity verification media, including the liveness video90 days
The ID photo and selfie for women-only ridesDeleted 90 days after review
In-trip chat messages1 year after the trip ends
Support tickets and their messages1 year after the ticket is closed
In-app activity logs90 days
Trip and payment recordsAs required by tax and transport law, then anonymised
Account data after a deletion requestAnonymised 72 hours after the request, unless you sign back in first

Your rights

Under the DPDP Act you have the right to:

  • Access a summary of the personal data we hold about you and how we process it.
  • Correct data that is inaccurate, and complete data that is incomplete.
  • Erase your personal data where we no longer need it for the purpose it was collected for, or where you withdraw consent.
  • Grievance redressal — to complain to us, and to have that complaint answered.
  • Nominate another person to exercise these rights on your behalf in the event of your death or incapacity.

The fastest way to erase your data is in the app. Open your account settings and request deletion — it takes effect after 72 hours, and signing back in during that window cancels it. You do not need to contact us. If you cannot sign in, write to support@snappcab.in from the address on your account and we will handle it for you.

For access or correction, write to support@snappcab.in. We may need to verify your identity before we act, which is a protection for you rather than an obstacle: without it, anyone who knew your email address could ask for your data.

You also have a duty under the DPDP Act not to make a false or frivolous request, and not to impersonate someone else when making one.

How we protect it

  • Data is encrypted in transit. Access to production systems is restricted and logged.
  • Verification documents are never served from a public URL — reading one requires a short-lived, individually issued link.
  • Staff access to personal data is limited to those who need it, gated by role, and recorded in an audit trail that cannot be edited.
  • Console accounts require multi-factor authentication.

If a personal data breach occurs, we will notify the Data Protection Board of India and each affected Data Principal as the DPDP Act requires.

Children's data

SnappCab is not intended for anyone under 18, and we do not knowingly create accounts for children. We do not currently operate an age-verification gate, and we would rather say so than claim a control we do not have. If we learn that we hold the personal data of a child, we will delete it. If you believe a child has created an account, tell us at support@snappcab.in and we will act.

Cookies

When you sign in anywhere on this site — to be quoted a fare, or to reserve an intercity seat — we set snapp_session. It holds your login tokens, your phone number and whether the account is a rider or a captain. It is httpOnly, so page scripts cannot read it, and it expires 30 days after you last used the site. Signing out clears it.

One other cookie, snapp_view, is set only if you ask for it. Phones are sent to our app version of this site; choosing “desktop site” from the phone version records that choice in snapp_view so we do not send you back on the next visit. It holds one word, desktop, is httpOnly, identifies nobody, and lasts a year or until you ask for the phone version again, whichever comes first.

Your choice of the day or night theme is kept in your browser’s local storage so the site does not change appearance every time you return. It never reaches us. We do not use advertising or cross-site tracking cookies on this site, and apart from snapp_view nothing here is set before you sign in.

The SnappCab apps do not use cookies. They store an authentication token on your device so you stay signed in; signing out removes it.

Transfers outside India

Some of the service providers listed under Who we share it with process data outside India. Where that happens we transfer personal data only to countries not restricted by the Central Government for this purpose, and we require the provider to protect it to the standard this policy describes.

Changes to this policy

We will update this policy when what we do changes. If a change materially affects your rights we will tell you in the app or by email before it takes effect, not afterwards. The version number and effective date at the top of this page always tell you which version you are reading.

Contact and grievances

For anything about this policy or your data, write to our data protection contact at privacy@snappcab.in.

If you are not satisfied with our response, you can escalate to our Grievance Officer at privacy@snappcab.in and, if you remain dissatisfied, complain to the Data Protection Board of India.