Privacy policy
Last updated: 10 October 2026
Fleey is a transport management service: a web console, a customer portal, and the Fleey Driver and Fleey Owner apps. It is operated by Kvcodes ("we"), reachable at fleey@kvcodes.com. We do not sell data, do not use it for advertising, and do not build profiles of anyone.
Who decides what happens to the data
Transport companies use Fleey to run their business. Each company has its own workspace, and decides whose details go into it: its staff, its drivers, its customers and their consignees. For that data the transport company is responsible (under India's Digital Personal Data Protection Act, 2023, it is the data fiduciary), and we process it on its behalf and on its instructions.
For the details of the people who sign up for Fleey itself, we are responsible.
If you are a driver, a consignee or a customer of a transport company that uses Fleey, the quickest way to exercise your rights is to ask that company. You can also contact us (see Contact), and we will pass your request on and help them answer it.
What is collected, and why
People who sign in to the console or the Owner app. Name, email address, mobile number (optional), role, and a password, which is stored only as a one-way hash. If you sign in with Google, we receive your name, email address and Google account ID from Google; we never see your Google password. We email you only about your account: to confirm your address and, when you ask, to reset your password. These emails are sent through our email provider. Why: to let you sign in, to let you recover your account, and to show who did what.
Drivers. Name, mobile number, employee ID, driving licence number and expiry, and a sign-in PIN (stored only as a one-way hash). The Driver app is tied to one phone at a time, identified by an ID the app creates; we do not read the phone's IMEI, contacts or other apps. Why: to give each driver their trips, and to check a licence is valid before a trip is assigned.
Location (Driver app). While a trip is started, the Driver app records the phone's position as the vehicle moves (at most one point every 15 seconds, or every 100 metres when moving faster), including when the app is closed or the screen is off, and sends it to the transport company's workspace. A notification is shown on the phone for as long as this is happening. Location is not collected before a trip starts or after it is completed. When a driver arrives at a stop or confirms a delivery, the position at that moment is recorded with it. The app explains this and asks before Android's own permission prompt. Why: to show the vehicle on the company's map, tell customers when to expect their goods, and record where each delivery was made.
Proof of delivery. Photos of the goods, the receiver's signature, the receiver's name and (optionally) mobile number, quantities, cash collected, and remarks. Why: proof that goods were delivered, for the transport company and its customer.
Expenses and fuel. Amounts, categories, and photos of receipts and fuel bills. Why: so drivers are reimbursed and costs are accounted for.
Customers and consignees. Names, addresses, contact names and mobile numbers, as entered by the transport company. Why: to plan and deliver shipments and to invoice for them.
Technical records. For security, we record which account did what, when, from which IP address and with which browser or app version (an audit trail), and we count failed sign-ins to block password guessing.
The apps work without signal. What a driver records offline stays on that phone, inside the app, until it has been sent.
Who can see it
- The transport company's own users, according to the roles the company gives them.
- The transport company's customers, through tracking links and the customer portal: the status and position of their own shipments and the proof of their deliveries. The driver's name and phone are not shown to them.
- Systems the transport company connects, such as its accounting system (for example TamilAccounting), which receive shipment and delivery updates when the company sets up that connection.
- Service providers that make Fleey work:
- our hosting provider, GoDaddy (Host Europe GmbH), whose servers are in Strasbourg, France. Fleey's data, and its backups, are therefore stored outside India;
- Google, if you choose to sign in with Google; Google reCAPTCHA, which checks that sign-in and sign-up forms are used by a person and so sees your IP address and how the page is used (Google's privacy policy and terms apply); and Google Fonts, from which this website loads its typefaces;
- OpenStreetMap, whose map images the apps load, and which therefore sees the device's IP address and the area of the map being viewed.
- Authorities, when the law requires it.
How it is protected
All traffic is encrypted (HTTPS). Passwords and PINs are stored only as one-way hashes, and so are password-reset links. Each workspace's data is kept separate from every other's. Photos and signatures are never publicly addressable: they are shown only through links that expire after 15 minutes. A driver's session works only on the phone it was started on, and the apps exclude themselves from phone backups, so a session cannot be copied to another phone. Deactivating a user, or resetting their password, signs them out everywhere at once. The database and uploaded files are backed up every night; backups are kept for 14 days and are readable only by the server account.
How long it is kept
Data is kept while the workspace exists, except for the following, which are deleted automatically:
| What | Deleted after |
|---|---|
| Raw GPS points from the Driver app (each trip keeps its distance, and each delivery its location) | 180 days |
| The audit trail of who did what | 1 year |
| Proof-of-delivery photos and signatures | 3 years |
| Photos of expense receipts and fuel bills (accounting records) | 8 years |
| Photos uploaded but never attached to anything | 14 days |
| Password-reset and email-confirmation links | 1 day after they expire |
A transport company can close its workspace at any time from its settings. Everyone is signed out at once, and 30 days later the workspace and everything in it are deleted. Its GST invoices, and the customer details printed on them, are first moved to an archive and kept for 8 years, as tax law requires; nothing else is kept. Deleted data disappears from backups within a further 14 days.
Your rights
You can ask for a copy of your personal data, for it to be corrected, or for it to be deleted, and you can withdraw consent where consent is the basis. Drivers can stop location sharing at any time in Android's settings; the app then tells the driver, and the company, that the vehicle cannot be seen. Some records cannot be deleted while the transport company needs them to meet a legal obligation, such as tax records.
Deleting your account
A company's owner can close the whole workspace under Settings → Company → Close this workspace; everyone is signed out at once and everything is deleted 30 days later (GST invoices are archived as the law requires). Staff and drivers are added by their company: ask its owner or administrator to remove you, or write to fleey@kvcodes.com from the address on your account (or, for a driver, with your mobile number and company name) and we will arrange it with the company within 7 days. What the company must keep by law, such as tax records, stays until that period ends.
Children
Fleey is a business service and is not meant for anyone under 18.
Changes
If we change this policy in a way that matters, we will say so in the console and update the date at the top.
Contact and grievances
Write to the Grievance Officer, Kvcodes, at fleey@kvcodes.com, for any question about your data, any request under "Your rights", or any complaint. Say which workspace (company) your data is in, if you know.
We acknowledge every request within 7 days, and resolve grievances within the period the Digital Personal Data Protection Act and its rules require. If you are not satisfied with our answer, you may complain to the Data Protection Board of India.