Privacy
Covers the JaldiGO website and the JaldiGO Android app. Last updated 17 September 2026.
The website
This website has two forms and nothing else that collects anything. There is no login, no account, and no advertising cookie or third-party tracker anywhere on it.
The launch list is closed and the form that fed it has been removed from this website. If you joined it before that, we still hold the phone number and area you gave us, and we still use them for the one thing we said: a single message about JaldiGO in your area. We do not sell them and we do not pass them to anyone else.
If you apply to be a driver, we store your name, phone number, CNIC number, driving licence number, vehicle registration number and area, along with the photographs you upload of yourself, your documents and your vehicle, so that a person here can check them and call you. Applications are reviewed by hand, and the photographs are kept in private storage that only a JaldiGO reviewer can open.
If you message us on WhatsApp instead, that conversation is covered by WhatsApp's own privacy terms, and by ours: we use your number to reply to you. Nothing else.
If you ask us to delete your account through the form on this website, we store the email address you sign in to JaldiGO with and, if you give one, your phone number, so that a person here can find the account and confirm the request is really yours before anything is deleted. That request record is deleted along with the account.
The JaldiGO app
The Android app is where rides actually happen, so it collects more than this website does. Everything the app collects is listed below. If something is not on this list, the app does not collect it.
Signing in. The app signs you in with your Google account, and from Google we receive your name, email address and profile photo. We never see your Google password. You type your phone number in yourself. That number matters for two reasons: it is how a driver and a passenger call each other about a ride, and it is what matches a driver application made on this website to the same person’s app account, so nobody has to send their documents twice.
Becoming a driver. If you apply to drive for JaldiGO in the app, we store the type of vehicle you will drive (for example bike, rickshaw, car or van), its registration number, make, model, colour and model year, your CNIC number, driving licence number and the area you drive in, and the photographs you take or choose: your face, your CNIC front and back, your driving licence, your vehicle registration, and the front and side of your vehicle. A person here reviews them together before you can take a ride. The photographs are kept in private storage that only a JaldiGO reviewer can open.
Location, drivers. While a driver is Online, and while a ride is under way, the app reads the phone’s location and sends it to us, including when the app is minimised or the screen is off. A JaldiGO notification stays in the status bar for the whole time that is happening, so it is never running silently, and it stops the moment the driver goes Offline. We store only the driver’s latest position: a single row, overwritten each time. There is no record of where a driver has been, and that is deliberate rather than an omission.
Location, passengers. The app reads a passenger’s location to suggest a pickup point, and only while they are using the app. Passengers are never tracked in the background. The pickup and drop points you confirm are stored with the ride, and the pickup point is shown to the driver who accepts it, because that is how they find you.
What the app asks your phone for. Location, for the two reasons above. Notifications, so that Android will show the status-bar notice while a driver is online and so a ride offer makes a sound. We ask for this before any tracking starts, never after. The camera and your photo gallery, only at the moment a driver taps to photograph a document or their vehicle, or to choose a profile picture. That is the whole list: the app does not ask for your contacts, your microphone or your files, and it does not hold Android’s “allow all the time” location permission. You will never be shown that option, because the app cannot read your location with it fully closed.
What the two of you see about each other. Once a ride is accepted, the passenger sees the driver’s name, photo, rating and phone number, the vehicle type, and the vehicle’s registration number, make, model and colour, and the driver’s live position on the map until the ride ends. The driver sees the passenger’s name, photo, rating and phone number, and the pickup and drop points. Neither of you is shown to anyone else using the app.
Rides, fares and the wallet. We store each ride: the two points and the names they were given, the route, the distance, the fare, the times and how it ended. For drivers we also store a wallet balance and one line for every top-up and every commission deduction, because that is money you have actually handed over and you are entitled to watch it add up. The fare is paid directly to the driver. The app never processes a payment, and we never see a card or a bank account.
Ratings and SOS. A rating you give is stored against that ride. If you press SOS during a ride, we log the ride, the time and the last position the app had, so that a person here can look at what happened.
Who else sees any of this. The database and the photographs are held by Supabase. Google provides the map you look at, the sign-in, and the navigation app the driver taps through to. OpenRouteService is sent the two ends of a ride, and nothing else about you, not your name, not your phone number, not your account, so that we can work out the real road distance and price the ride honestly. That is the entire list. We do not sell your data, we do not share it for advertising, and the app contains no advertising or analytics SDK.
How it is kept safe. Everything the app and this website send us travels over an encrypted connection; nothing goes out in the clear. In the database, each row carries its own rule about who may read it: a driver cannot open another driver’s documents, and a passenger cannot open anyone’s. Driver photographs sit in private storage that is not reachable by a link. Your sign-in stays in your phone’s own encrypted store, and we never see your Google password.
How long we keep it, and how to have it deleted. Ride, wallet and rating records are kept while your account exists. A driver’s documents, vehicle details and vehicle photographs are kept while they drive for JaldiGO. You can ask us to delete your account at any time and we will delete it, together with your rides, ratings, documents and vehicle details. There are three ways to ask, and all three reach the same person here: open Account and tap “Delete my account” in the app; fill in the form at jaldigo.com/en/delete-account/, which needs neither the app nor an account and works if your phone is gone; or message the same WhatsApp number, +92 339 9999338. We confirm the request is really yours before anything is deleted, and if you are a driver with money in your wallet we hand that back to you in cash first. Deletion is done within 30 days of the request and usually within a few days. Where we are required by law to keep a record of money handed over, we will keep that record and nothing else, and we will tell you if it applies to you.
Children. JaldiGO is not for anyone under 18, and we do not knowingly collect anything from a child.
Changes, and who we are
JaldiGO is operated from Kharian, Punjab, Pakistan. If this policy changes, we will update this page and the date at the top of it. Anything you want to ask about it: WhatsApp +92 339 9999338.
