See what we hold
Ask, and we will send you the personal data on your account.
Privacy policy
The short version, in plain words. Everything below it is the same thing said precisely.
Your phone number to sign you in, the addresses a parcel travels between, and — for drivers — the documents the law requires before someone may carry goods.
Five named companies process parts of it on our behalf, listed further down with exactly what each one receives. Nobody else gets it, and no one pays us for it.
Delete your account from the app and the personal data goes. There is a 30-day window first, because a mistaken tap should be recoverable and erasure is not.
Most of this list is not about you. Documents and bank details are what the law asks of someone carrying goods for hire — we never ask them of a customer.
We do not collect anything not on this list. If you find something we hold that is not here, it is an error — tell us and we will fix both the data and this page.
One piece of data, followed end to end. Every other field takes a shorter path than this one.
You type the number into the app.
Nothing has left the device yet.
Stored against your account, and a six-digit code is generated.
The code is stored as a hash, never in the clear.
Receives your number and the code, so it can send you the SMS.
They see the number because they are the ones sending the text. Nothing else goes with it.
You enter the code; we compare it and sign you in.
The code is deleted automatically ten minutes after it was issued.
The number is replaced with a placeholder and cannot be read back. We keep a one-way SHA-256 hash of it so that a deleted number can never be used to open a new account — which lets us answer “is this that number?” forever, and “what was the number?” never.
Two of these are deleted by a job on a clock. The rest are kept while your account is open — and we would rather say so than name a deadline nothing enforces.
A database TTL index, plus an hourly sweep. Not a policy — a mechanism.
Expire with the trip they belong to.
A daily job erases accounts past this mark. The window exists so a mistaken deletion can be undone by support — and not after.
Nothing deletes these on a schedule. They are your delivery history, and they go when the account is erased.
We are required to be able to show that a driver carrying goods was verified.
A tax invoice is not ours to delete. Indian law sets how long these are kept, and that outlives an account.
The axis is logarithmic — ten minutes and thirty days cannot share a straight line without one of them disappearing. Bars that run off the right have no end date because no job ends them; that data goes when your account is erased.
We do not sell your data and nobody pays us for it. These five companies process a part of it because a delivery cannot happen otherwise — each gets only its own slice, and none of them talk to each other.
Payment identifiers, amount, and the contact details a payment needs.
Your card and UPI credentials are entered on their side. They never reach us.
Your phone number and the six-digit code.
Only at the moment a code is sent.
Driver KYC documents and photographs.
Storage only. Nothing is read from them except by us.
Pickup and drop coordinates, and a driver's position while a trip is live.
Required for the map you watch a delivery on.
A device token, if your app registers one.
⚠️ Not currently in use. The integration exists and has never been switched on — no push notification has been sent to anyone.
This applies to drivers. A customer's location is never continuously read — only the addresses on a booking.
On a trip
Read continuously, and shown to the customer whose delivery it is.
These are not favours. Three of the five you can do yourself, right now, without contacting anybody.
Ask, and we will send you the personal data on your account.
Name, email and business billing details are editable in the app. Ask us for anything that is not.
In the app: Settings → Delete account. It closes immediately; the data is erased 30 days later.
In the app, per channel. It never affects a delivery you have already booked.
To us first — we would rather fix it. If that fails, to the authority in your jurisdiction.
Three stages, and the middle one is deliberate. We would rather be able to undo a mistake than be fast about it.
The account closes. You are signed out everywhere, the number stops working as a login, and nobody can book with it.
The data still exists, and support can restore the account if the tap was a mistake. Nothing new happens on it.
A job erases the personal data. The phone number is replaced with a placeholder that is not a phone number, and only a one-way hash of the original remains — enough to stop that number opening a new account, and not enough to ever read it back.
You can stop this at any point in the first 30 days by contacting support. After that there is nothing to restore — which is the point of erasing something.
Anything about your data — what we hold, correcting it, deleting it.
⚠️ A named officer has not yet been appointed. Until one is, this address reaches the company directly.