GPS Fleet Tracking in India: AIS-140 Rules, DPDP Act Duties, Costs and Rollout Timelines
In India, AIS-140 tracking is a permit requirement for covered vehicles, while most other telematics is optional, and the DPDP Act touches both. Here's what's mandatory, what it typically costs per vehicle and how long a rollout takes.
What the AIS-140 Mandate Requires, and What It Doesn't
If you run commercial vehicles in India, you're making two separate decisions. The first is how to meet the AIS-140 vehicle location tracking rule, which isn't optional for vehicles it covers. The second is how much telematics to add on top for fuel, safety and utilization. Many fleets merge the two and overpay, or buy a cheap compliance box and then find it can't run the analytics they wanted. A good plan for GPS fleet tracking India keeps the decisions apart, even if you end up buying both from one vendor.
AIS-140 is an Automotive Industry Standard. The Ministry of Road Transport and Highways (MoRTH) made it mandatory through the Central Motor Vehicles Rules for public service vehicles: buses, taxis, cabs and other permit-holding passenger vehicles. Many states have applied similar requirements to national-permit goods vehicles, and some to other categories. Two-wheelers, e-rickshaws and some three-wheelers are generally exempt. Coverage and enforcement dates vary by state, so your state transport department's notification is the document that counts.
A compliant setup usually has four parts:
- A certified AIS-140 tracking device. The model must be type-approved by a recognized testing agency such as ARAI or ICAT, with a valid conformity certificate. Many states also require the manufacturer to be on an empanelled list.
- Emergency (panic) buttons. When pressed, they send an alert with location to the state's command and control center. Several states also route alerts to the 112 emergency response system.
- Embedded connectivity. That means a cellular connection on an embedded or industrial SIM, often with fallback across networks. Newer specifications also expect NavIC satellite positioning alongside GPS.
- A state backend connection. The device must send location data to the state's tracking backend and be linked to the vehicle's record. In many states, fitness certificate or permit renewal can be held up until the device is registered.
The mandate doesn't require fuel monitoring, driver scoring, cameras, route optimization or ERP integration. Those are business choices, and they carry their own data-protection duties, covered below.
Separating Compliance Hardware From Optional Fleet Telematics
The cheapest compliant device and the most useful telematics platform are rarely the same product. Some AIS-140 vendors offer a basic portal with live location and trip history, and for a small passenger fleet that may be enough. Distributors, 3PLs and manufacturers running their own trucks usually need more: fuel sensors, cold-chain temperature logging, proof of delivery and an API into their TMS or ERP.
| Capability | Status | Who it mainly serves | Buyer note |
|---|---|---|---|
| Certified device, panic buttons, state backend feed | Mandatory for covered vehicles | Regulator, passenger safety | Buy on certification, state empanelment and service network, not features |
| Live tracking, geofences, trip history | Optional (often bundled) | Dispatch, customer service | Can run on the same AIS-140 device if the vendor exposes the data |
| Fuel level sensors and theft alerts | Optional | Finance, fleet operations | Often the fastest payback for long-haul diesel fleets |
| Driver behavior scoring (harsh braking, overspeed) | Optional | Safety, insurance | Counts as personal data processing, so plan notices |
| Video telematics and driver-facing cameras | Optional | Safety, claims defense | Highest privacy sensitivity; set a clear retention policy |
| Reefer temperature and door sensors | Optional | Cold chain, pharma, food | Customer contracts may effectively require it |
| TMS/ERP integration via API | Optional | Planning, billing, finance | Check API limits and data export rights before signing |
Most mixed fleets of 30 to 300 vehicles should buy an AIS-140 device whose data the vendor will also stream into a third-party fleet management software India platform, or into its own. That avoids a second GPS unit in every vehicle. Domestic names you'll meet include MapmyIndia (Mappls), LocoNav and Fleetx on the software side, and device makers such as iTriangle. Get written confirmation that the feed can go to your chosen platform and the state backend at the same time. Some low-cost compliance devices are configured to report only to the government.
How the DPDP Act Generally Applies to Driver Data
The Digital Personal Data Protection Act, 2023, and its implementing Rules apply to digital personal data processed in India. Driver location history, trip logs tied to a named driver, behavior scores, phone numbers and camera footage all generally count as personal data. Your company is usually the data fiduciary, the organization that decides why and how data is processed. Your telematics vendor is usually a data processor acting on your instructions. Many obligations phase in over a transition period after the Rules were notified, so confirm the current dates with counsel. A rollout you start now should be built for the final requirements.
The Act allows processing either with consent or under listed "legitimate uses." Two matter most for DPDP Act driver data:
- Compliance with law. Location data generated because AIS-140 requires it generally falls here. You don't need driver consent to switch on a device the law requires.
- Employment purposes. The Act allows processing for employment-related purposes, including protecting the employer from loss or liability. That may cover reasonable monitoring of employees. Whether it stretches to continuous driver-facing video is a question for counsel.
Indian fleets have a complication many other markets don't. A large share of trucks are run by attached owner-drivers or market vehicles hired per trip, not by employees. The employment basis may not cover them, so contractor drivers may need clear notice and consent for optional monitoring.
Duties that typically apply whatever the legal basis:
- Give drivers a plain-language notice of what is collected and why, in a language they read.
- Collect only what each purpose needs. Driver scoring doesn't require off-duty location.
- Sign a contract with the telematics vendor covering security safeguards, sub-processors and breach reporting.
- Report personal data breaches to the Data Protection Board and affected individuals.
- Erase data once its purpose is served, unless another law requires you to keep it.
- Offer a grievance channel so drivers can raise complaints.
Penalties for failing to maintain reasonable security safeguards can be very large, in the hundreds of crores of rupees. Treat vendor security as a procurement criterion, not an IT afterthought. This section describes how the framework generally works. Have a qualified Indian data-protection lawyer review your notices, legal bases and vendor contracts before you deploy cameras or driver scoring.
Indicative Per-Vehicle Costs and a Worked Budget
Prices below are typical 2026 market ranges in India. They vary with volume, contract length, state, installation geography and bundling. Confirm them with vendors in writing. USD figures are approximate conversions.
| Cost item | Typical range (INR) | Approx. USD | Frequency |
|---|---|---|---|
| Certified AIS-140 device, installed, with panic buttons | 7,000–15,000 | 85–180 | One-time |
| SIM, data and state backend/server charges | 1,500–3,500 | 18–42 | Per year |
| Fleet management software (tracking, reports, alerts) | 200–800 | 2.50–10 | Per vehicle per month |
| Fuel level sensor, installed and calibrated | 8,000–20,000 | 95–240 | One-time |
| Video telematics (dual-facing camera) hardware | 15,000–40,000 | 180–480 | One-time |
| Video platform and cellular data | 500–1,500 | 6–18 | Per vehicle per month |
| Field reinstallation or repair visit | 500–2,000 | 6–24 | Per event |
The biggest cost drivers are volume tiers, contract length (two to three years is common), whether renewal fees are capped, installation outside metro service hubs, and how much video you upload. Video is where budgets usually run over.
Worked example (hypothetical). Say a regional distributor runs 80 goods vehicles on national permits. All 80 need AIS-140 devices, it adds fuel sensors on 40 long-haul trucks, and it skips cameras for now. At mid-range pricing, the one-time cost is about INR 8.8 lakh for devices (80 × 11,000) plus INR 5.6 lakh for fuel sensors (40 × 14,000), roughly INR 14.4 lakh, or about USD 17,000. Recurring cost is about INR 2 lakh a year for SIM and backend charges plus about INR 4.3 lakh a year for software at INR 450 per vehicle per month. That's roughly INR 6.3 lakh, or about USD 7,500, a year. If fuel sensors cut theft or unexplained consumption even modestly, they can pay back within a year or two. Measure your own baseline before relying on that.
Rollout Timeline, Red Flags and a Decision Rule
Most fleets underestimate the steps outside their control: state backend activation, vehicle-record linkage and field installation across depots. A realistic plan for a fleet of 50 to 200 vehicles looks like this:
| Phase | Typical duration | Key output |
|---|---|---|
| Scope: map vehicles to permit categories and state rules | 1–2 weeks | List of vehicles that must comply, and by when |
| Vendor shortlist, certificate and empanelment checks, pilot | 3–5 weeks | Pilot on 5–10 vehicles with backend data confirmed |
| DPDP work: notices, vendor contract, retention policy | 2–4 weeks (run alongside the pilot) | Signed processing terms, driver notices translated |
| Installation and backend registration | 2–8 weeks, depending on how spread out the depots are | Devices live, vehicle linkage confirmed |
| Panic-button tests, integration, driver briefings | 2–3 weeks | Tested alerts, TMS/ERP feed, trained dispatchers |
Total: about 8 to 16 weeks. If a fitness renewal is coming up, start with the vehicles whose certificates expire first.
Red flags when choosing a vendor
- The device model's conformity certificate has expired, or the device isn't on your state's empanelled list.
- The vendor can't show a live connection to your specific state's backend.
- A locked SIM or proprietary firmware blocks data from reaching any software but the vendor's own.
- The contract has no data export clause, or charges exit fees for your historical trip data.
- Answers are vague about where data is hosted, who the sub-processors are, or how fast breaches are reported.
- Renewal pricing is uncapped after the first year.
- There's no service presence near your main depots or routes.
Decision rule: If more than about half your fleet needs AIS-140 and you also want fuel or utilization analytics, pick one vendor whose certified device feeds both the state backend and an open-API platform. Pilot ten vehicles across two states before signing a fleet-wide contract. If you only need compliance, buy the best-supported empanelled device in each state you operate in and decide on analytics later.
Quick answers
Does every commercial vehicle in India need an AIS-140 device?
No. The central mandate covers public service vehicles such as buses, taxis and cabs. Many states have extended similar requirements to national-permit goods vehicles. Two-wheelers, e-rickshaws and some three-wheelers are generally exempt, so check your state transport department's current notification for each vehicle category you run.
Can one device handle both AIS-140 compliance and our fleet management software?
Usually, yes. Many certified devices can send data to the state backend and a commercial platform at the same time. Get this confirmed in writing and tested during a pilot, because some low-cost compliance devices are configured to report only to the government.
Do we need driver consent under the DPDP Act to track vehicles?
For tracking the law requires, such as AIS-140, processing generally falls under the Act's legitimate use for complying with law, so consent isn't needed. Optional monitoring like driver scoring or cameras may rely on the employment legitimate use for employees. For owner-drivers and contractors, consent is often the safer basis. A data-protection lawyer should confirm the approach for your fleet.
What's a realistic all-in cost per vehicle for the first year?
For basic compliance plus standard tracking software, many fleets pay roughly INR 10,000 to 25,000 per vehicle in year one (about USD 120 to 300). Adding fuel sensors or video telematics can double or triple that. These are typical 2026 market ranges that vary by contract, so get written quotes that include renewal pricing.
Written by the Fleetmesh Tech editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.