Partner Privacy Notice

Who this is for

This notice applies to you if you drive for us, own a vehicle we run, or partner with us in any other capacity, whether you work with us directly or through an operator we have an arrangement with. That covers a driver on our own rolls, an owner who puts a vehicle on the road with us and drives it himself, an owner who puts a vehicle on the road with us and engages a driver of his own, and anyone who supplies a vehicle or a driver to us through a partner operator rather than directly.

Read this alongside our Driver Terms and our Vehicle Partner Terms, which set out what we expect of you on duty. This notice covers a narrower question: what personal data we collect about you, why we need it, who else sees it, and how long we hold it. If you are a customer booking a trip rather than someone who works with us, this notice is not the one you need; our Privacy Policy at /privacy-policy covers what we collect from a passenger, which is a different kind of data collected for a different reason.

What we collect and why

We collect only what we need to onboard you, keep you road legal, pay you correctly and run a safe duty. We do not ask for anything beyond that, and each category below exists for a specific, stated reason.

Name, photograph, address and contact details

To identify you, reach you, and put a face to a duty slip.

Driving licence

To confirm you are legally permitted to drive the class of vehicle allotted to you.

Police verification

A standard safety check before you are put on duty with a passenger.

Medical fitness certificate

Required for commercial driving under the Motor Vehicles Act.

Bank account details

To pay you for a completed duty.

PAN

For tax compliance on payments made to you.

Identity verification document

A masked Aadhaar, an Aadhaar Offline XML, or a document issued through DigiLocker. What we accept, and what we deliberately do not collect or store, is set out in full below.

Vehicle RC, permit, fitness certificate, insurance and PUC

To confirm the vehicle you bring us is road legal and properly documented.

Duty slips and odometer records

Our operational record of the duty: what was run, and the distance it covered.

Driving-behaviour data, where GPS or telematics is fitted

Collected only during duty hours. What this covers, and what it deliberately does not, is set out below.

A few of these are worth a fuller explanation than a one-line entry can give.

Police verification exists because a passenger gets into your vehicle without having met you first, and has no way of checking who is behind the wheel beyond what we have already checked on her behalf. It is not a comment on your character. It is a standard, upfront check that every driver we put on duty goes through, so that a corporate client sending its staff home late, a family booking a wedding car, or a woman travelling alone at night is dealing with someone whose background has actually been verified rather than taken on trust. We verify the certificate once at onboarding, keep it on file for as long as you are engaged with us, and ask for a fresh one if it lapses, in line with our Driver Terms and Vehicle Partner Terms.

Bank account details are collected for one purpose, to pay you for a completed duty, directly and without a middleman handling your money. We do not use your account details for anything beyond that payment, and we do not share them with anyone outside the limited circumstances set out in the next section. PAN is collected for a related but separate reason: so that tax is deducted and reported correctly on what we pay you, as the Income Tax Act requires of any business making a payment of this kind.

Vehicle documents, the RC, the permit, the fitness certificate, the insurance policy and the PUC certificate, exist to establish one thing: that the vehicle you bring us is legally entitled to be on the road with a paying passenger in it. A lapsed permit or an expired fitness certificate is not a paperwork formality, it is the difference between a duty that is lawful and one that is not, for you, for us, and for whoever is sitting in the back. We check these documents at onboarding and again whenever a renewal falls due, and a vehicle whose documents have lapsed is not put forward for a duty until a current copy has reached us.

Who it's shared with

We share your data with three kinds of recipient, and no one else. Each shares it for a stated reason rather than as a matter of routine, and each gets only what that reason actually needs.

A corporate client

Where a company has booked you for a duty carrying its own staff and asks us to confirm who is driving before the vehicle reaches its gate, we share what answers that: your name, your photograph, your licence details, and confirmation that your police verification is current. This is the same kind of clearance a corporate security desk runs on any visitor arriving on site, and it exists so the company can be satisfied about who is driving its people, not so that a stranger can look up your file.

Our insurer

Where a duty ends in an accident, a claim, or a dispute that touches a vehicle's insurance policy, we share the relevant duty slip, licence and vehicle documents with our insurer so the claim can actually be processed. Without this, a genuine claim, yours or the vehicle owner's, could not be settled.

A government authority

Where a court, the police, a transport authority or another government body has the legal power to require it, we hand over what the law obliges us to hand over, and nothing more than that.

We do not sell your data, we do not share it for anyone else’s marketing, and we do not share it with anyone outside this list.

GPS and telematics

Not every vehicle we run carries GPS or telematics equipment. Where one does, here is exactly what the record it keeps is used for, and just as importantly, what it is not used for.

GPS tracking operates only while a vehicle is on duty, where it is fitted. We do not track a driver or a vehicle outside allocated duty hours, and telematics data is used for safety, dispute resolution and customer service only.

In practice, this record helps us in three situations. If a passenger raises a concern about the route taken or the timing of a duty, the record lets us check what actually happened rather than relying on memory alone, on either side. If there is a dispute over the distance or the hours billed on a duty, it corroborates the duty slip you sign at the end of it, which protects you as much as it protects us. And if something goes wrong on the road, a breakdown, an accident or another emergency, it helps us locate the vehicle and respond without waiting for someone to describe where they are.

What it is not used for is watching you as a person. It does not run when the vehicle is off duty, it is not used to track where you go in your own time, and the record it keeps is not shared with anyone beyond the recipients named in the section above unless the law specifically requires it. When a duty ends, what we use that duty’s tracking data for ends with it.

How long we keep it

We keep your data for as long as you are engaged with us, and for 3 years after that engagement ends. Where the Motor Vehicles Act or a tax law requires a document to be held for longer, that document is kept for whichever period is longer.

The 3-year period after your engagement ends is not an arbitrary figure. It covers the ordinary window in which a question about a duty you drove can still surface: a passenger’s complaint reaching us months after the trip, an insurer reopening a claim, a tax authority asking about a payment made to you, or a corporate client running its own audit against a driver who worked its account before renewing the arrangement. Keeping the record for this period lets us answer a question like that with the actual document rather than with nothing, which is as much in your interest as ours if a claim is ever made against you unfairly.

Once the retention period for a document has run its course, and no statutory requirement extends it further, we delete it. We do not hold a driver’s or a vehicle owner’s data indefinitely once the engagement has ended, the statutory period has passed, and there is no live dispute left to answer for.

The Aadhaar rule

Identity verification is one of the more sensitive things we ask of a driver or a vehicle owner, because the documents involved can carry more about you than a driving licence or a bank account does on its own. Here is exactly what we accept for that purpose, and, just as importantly, what we deliberately do not.

We accept only masked Aadhaar, Aadhaar Offline XML or DigiLocker-issued documents for identity verification. We do not perform Aadhaar authentication and we do not store the full 12-digit Aadhaar number, in accordance with Section 8 of the Aadhaar Act, 2016.

In plain terms, this means we never ask you to hand over a photocopy of your full Aadhaar card, and we never run your Aadhaar number through an authentication check ourselves. A masked Aadhaar shows only the last four digits of the number. An Aadhaar Offline XML is a downloadable, digitally signed document that proves who you are without carrying the number in the clear. A DigiLocker-issued document is verified at source by the issuing authority itself, so we are relying on that verification rather than performing our own. Each of these confirms who you are without our ever holding the one number that, in the wrong hands, could be used to open other doors in your name.

This is not caution for its own sake, it is the law. Only entities specifically notified by the UIDAI may perform full Aadhaar authentication, we are not one of them, and we have built our onboarding around the formats that were designed for a business like ours to verify identity safely, without ever needing to hold your full Aadhaar number at all. The practical effect for you is that even if our records were ever compromised, your Aadhaar number itself would not be sitting in them to be exposed.

Your rights

You may ask us to let you access the data we hold about you, correct it where it is wrong, or erase it, subject to what we are legally required to retain under the Motor Vehicles Act or a tax law. In practice, for a driver or a vehicle owner, these three rights work like this.

Access

You may ask us for a copy of the personal data we hold about you: your onboarding documents, your duty and payment history, and any other record we hold that identifies you, so you can see for yourself exactly what is on file.

Correction

If something we hold about you is wrong, a licence number entered incorrectly, an address that has since changed, a document that has already been renewed but not updated on our side, tell us and we will correct it. This matters to you as much as it does to us: a wrong bank account detail delays your payment, and a document we still show as expired can keep you off a duty you are actually cleared for.

Erasure

You may ask us to delete your data. Where you are still engaged with us, or where the Motor Vehicles Act, a tax law or an open dispute requires us to keep a particular document, we will tell you plainly what we can delete now and what we are required to hold, and for how long, rather than simply refusing the request outright.

If you are not satisfied with how a request is handled, our Grievance Officer and the full escalation ladder are published at /grievance-redressal.

Our Data Protection Contact

For any question about this notice, or to make a request under it, write to our Data Protection Contact, Sachin Jaglan: sachin@om-travels.in · +91 99966 69190 · Grand Trunk Road, Panipat, Haryana.

We acknowledge every request within 24 hours and work to resolve it within 15 days. If a request needs more time because it touches a document we are checking against another record, we will tell you that rather than let it go quiet.