Fleet Tracking in the UAE and Saudi Arabia: Transport Rules, PDPL, Costs and Timelines
A fleet running trucks in both Dubai and Riyadh answers to two transport regulators, two data protection laws and two sets of hosting expectations. Here's how that shapes your shortlist, budget and go-live date.
Why one tracking contract has to satisfy two regulatory systems
If you run commercial vehicles in both the UAE and Saudi Arabia, you're not buying one telematics product. You're buying something that must meet two transport regulators' reporting expectations, two personal data protection laws that work differently, and two sets of expectations about where data is stored. Many evaluations of fleet management software UAE vendors treat Saudi Arabia as a later add-on. That's usually the mistake that forces a second procurement a year or two down the line.
The decision comes down to five criteria, in this order:
- Regulatory integration. Can the platform and its hardware feed the tracking data that transport authorities require for your vehicle categories, and are the devices type-approved by each country's telecom regulator?
- Lawful handling of driver data. Does the vendor's data model support the lawful basis, notice and retention rules you'll need under each country's PDPL, including camera and biometric features?
- Hosting location and transfer terms. Where does the production instance run, where do backups and support staff sit, and what does the contract say about cross-border transfers?
- Arabic-language support. A translated menu isn't enough. You need right-to-left reports, Arabic driver-app prompts, Arabic driver notices, and local-hours support in Arabic and English. Driver-facing material often needs Urdu, Hindi or Bengali too.
- Local installation capacity. Installer coverage in Dubai, Abu Dhabi, Riyadh, Jeddah and Dammam, plus warranty swap stock held in-country.
Price matters, but it rarely separates serious bidders. For a mixed fleet of 50 to 500 vehicles, the gap between a well-integrated vendor and a cheap one shows up later: in failed authority audits, device re-installs, or a driver's privacy complaint the system can't answer.
Transport authority rules and device approvals that narrow the field
Both countries regulate commercial-vehicle tracking by activity and by emirate or region, not through one blanket rule. Treat what follows as a map of where to ask questions, not a compliance checklist. Requirements change often, so confirm current scope with the authority and your licensed transport consultant.
United Arab Emirates
Tracking obligations are set mostly at emirate level. In Dubai, the Roads and Transport Authority (RTA) has required tracking and, in some cases, cameras or data links for categories such as school buses, taxis, limousines, heavy vehicles and dangerous-goods transport. In Abu Dhabi, the Integrated Transport Centre sets comparable rules for licensed transport activities. Run only light commercial vans under a general freight licence and you may face no mandatory tracking at all. Run tankers or staff buses and you very likely do.
Separately, devices with a SIM or radio generally need type approval from the Telecommunications and Digital Government Regulatory Authority (TDRA). Mainstream hardware from makers such as Teltonika, Geotab or Powerfleet's MiX range is commonly approved, but ask for the certificate for the exact model quoted. Unbranded imported trackers often lack one.
Saudi Arabia
The Transport General Authority (TGA) has been widening requirements for licensed freight, passenger and rental activities to fit approved tracking devices and connect them to its platforms. Heavy trucks and buses are the core of that scope. Your vendor needs either a working integration with the relevant TGA systems or a credible plan and timeline to build one. Ask for a live customer reference in a similar vehicle class, not a slide.
Devices also need type approval from the Communications, Space and Technology Commission (CST). If your fleet does government or semi-government work, expect the National Cybersecurity Authority's controls to appear in your customer's contract terms, and those can affect hosting choices.
Our position: for any Saudi project involving trucks or buses, make "demonstrated TGA integration" a pass/fail gate on the shortlist, not a weighted score. A lower price can't rescue a vendor that fails it.
Two PDPLs, driver consent and where the data lives
The UAE and Saudi Arabia both have a law called the Personal Data Protection Law, and the shared name misleads people. They differ in scope, regulator, lawful bases and transfer rules, and the UAE has separate regimes inside some free zones.
| Issue | UAE | Saudi Arabia |
|---|---|---|
| Main law | Federal Decree-Law No. 45 of 2021 (onshore); separate regimes in the DIFC and ADGM free zones | PDPL, amended in 2023, now in force after its grace period |
| Regulator | UAE Data Office (onshore); DIFC and ADGM authorities in their zones | Saudi Data and AI Authority (SDAIA) |
| Lawful bases relevant to telematics | Consent, plus exceptions such as performing a contract and meeting legal obligations | Consent, contract, legal obligation and, in some cases, legitimate interest (generally not for sensitive data) |
| Higher-risk data | Biometric and other sensitive categories need extra care | Biometric data is likely to be treated as sensitive; confirm with counsel |
| Cross-border transfer | Allowed to adequate jurisdictions or with safeguards; detail depends on implementing rules | Allowed under the transfer regulations with adequacy or appropriate safeguards and a risk assessment |
What this means for driver monitoring
Basic location tracking of a company vehicle during working hours can often rest on contract or legal-obligation grounds, and a legally mandated tracker can rest on the legal obligation itself. The harder cases are the features buyers add for safety:
- Driver-facing cameras and fatigue detection. If the system uses facial geometry to identify the driver or score drowsiness, you may be processing biometric data. That puts you in sensitive-data territory, where you'll likely need explicit consent or another narrow basis.
- Audio recording in the cab. Many fleets simply switch it off. UAE criminal law separately protects people against being recorded without consent, so the PDPL isn't the only risk.
- Off-duty tracking. Vehicles taken home overnight create a location history of private life. Make a privacy mode or after-hours masking feature a requirement.
Employee consent is fragile in both countries, because the employment relationship makes it hard to show it was freely given. Don't build the program on a signed consent form. Pick the most appropriate lawful basis for each data stream, give drivers a clear notice in Arabic and in the languages they actually read, and set retention periods. Thirty to ninety days for raw GPS trails and shorter for routine video is a common starting point, with longer holds for incidents. Check whether your licensed entity sits onshore, in DIFC or in ADGM, because the applicable law changes.
Hosting
Neither law imposes blanket data localization on private fleets. Even so, many Saudi customers, government-linked contracts and cybersecurity controls push data into the Kingdom. Major cloud providers operate or have announced regions in the UAE and Saudi Arabia, but availability varies by provider and service. Ask each vendor which region your instance would run in, where backups are stored, and from which countries support staff can see live data. A vendor whose only instance is in Europe or North America can still be lawful, but it adds transfer paperwork and may disqualify you from some tenders.
Indicative costs for fleets of 50 to 500 vehicles
The prices below are typical 2026 market ranges for the GCC, in USD. They vary by contract length, hardware choice, reseller margin and volume, so confirm with vendors. Quotes in AED or SAR often bundle hardware into the monthly fee over 36 months.
| Cost item | Typical range per vehicle | Notes |
|---|---|---|
| GPS tracker hardware | $60 to $250 one-off | Higher end includes CAN-bus reading, driver ID and temperature sensor inputs |
| Video telematics (AI dashcam) | $250 to $800 one-off | Dual-facing units with fatigue detection at the top of the range |
| Installation | $25 to $90 | Heavy trucks, tankers and multi-site jobs cost more; ask about after-hours installs |
| Tracking subscription | $10 to $28 per month | Includes SIM data in most GCC bundles |
| Video subscription add-on | $15 to $40 per month | Depends on cloud video storage and event volume |
| Authority integration, ERP/TMS links | $8,000 to $60,000 per project | One-off; integration with SAP, Oracle or Microsoft Dynamics is the main variable |
Hypothetical worked example
Say a distributor runs 200 vehicles: 120 light vans in Dubai and Abu Dhabi and 80 heavy trucks in Riyadh and Dammam. It fits trackers to all 200 and dual-facing cameras to the 80 trucks.
- Hardware: 200 trackers at about $150 = $30,000; 80 cameras at about $500 = $40,000
- Installation: 200 at about $55 = $11,000
- Subscriptions: 200 at $18 plus 80 at $25 = $5,600 a month, or about $67,000 a year
- Integration (TGA link plus ERP and TMS): roughly $25,000
That's about $106,000 up front and $67,000 a year, or roughly $300,000 over three years before internal staff time. As rough bands, a 50-vehicle fleet with the same structure might land between $45,000 and $90,000 over three years, and a 500-vehicle fleet with substantial video between $600,000 and $1.1 million. Volume discounts on subscriptions are often negotiable above a few hundred units.
The biggest hidden cost is re-installation. If a cheap tracker lacks type approval or can't connect to the Saudi authority's systems, you pay for hardware and labor twice.
Rollout timelines, red flags and when to bring in lawyers
Rollouts in the region usually take longer than vendors quote. The usual causes are installer scheduling around vehicle availability, authority integration approvals, and internal work on driver notices.
| Phase | 50 vehicles | 200 vehicles | 500 vehicles |
|---|---|---|---|
| Requirements, legal review, vendor selection | 3 to 5 weeks | 5 to 8 weeks | 8 to 12 weeks |
| Pilot (10 to 20 vehicles per country) | 2 to 3 weeks | 3 to 4 weeks | 4 to 6 weeks |
| Installation waves | 1 to 2 weeks | 4 to 6 weeks | 8 to 14 weeks |
| Authority and ERP integration go-live | 2 to 4 weeks (parallel) | 4 to 8 weeks (parallel) | 6 to 12 weeks (parallel) |
| Typical total | 6 to 10 weeks | 3 to 4 months | 5 to 8 months |
Red flags in proposals
- No named, contactable reference customer running the Saudi authority integration in production.
- Device models without TDRA or CST type-approval evidence.
- A data processing agreement that names no hosting region, or lets the vendor move data "to affiliates" without notice.
- Arabic support limited to the dashboard, with an English-only driver app, alerts and notices.
- Biometric camera functions on by default, with no way to disable them per country or vehicle group.
- Contracts over 36 months with hardware locked to one platform and no data export clause.
The legal review step
Before you sign, have counsel licensed in each country review three documents: the driver privacy notice and lawful-basis assessment, the data processing agreement and transfer terms, and your transport-licence obligations for each vehicle category. For fleets in DIFC or ADGM, use advisers who know those regimes. This article explains how the rules generally work. It isn't legal advice, and fleet telematics rules in the GCC change often enough that last year's assessment may not hold.
Decision rule: shortlist only vendors that pass the authority-integration and type-approval gates in both countries. Run a paid pilot in Dubai and Riyadh at the same time, and sign once the pilot's data exports, Arabic driver notices and hosting terms have cleared legal review.
Quick answers
Is GPS tracking mandatory for all commercial vehicles in the UAE and Saudi Arabia?
No. In both countries the obligation depends on the vehicle category and the licensed activity, not simply on whether a vehicle is commercial. Heavy trucks, buses, school transport, taxis and dangerous-goods vehicles are the usual focus. Light vans under a general trading licence are often outside the mandatory scope. Confirm your categories with the RTA, Abu Dhabi's Integrated Transport Centre or Saudi Arabia's TGA.
Do I need driver consent to track company vehicles?
Not always. Tracking that the law requires, or that's needed to perform the employment contract, can often rely on those grounds instead. Saudi Arabia's PDPL also recognizes legitimate interest in some cases for non-sensitive data. Driver-facing cameras with biometric features, audio recording and off-duty tracking carry more risk and may need explicit consent, so have local counsel assess each data stream.
Does fleet data have to be hosted inside Saudi Arabia or the UAE?
Neither PDPL imposes blanket localization on private fleets, and both permit cross-border transfers under adequacy or safeguard conditions. In practice, government-linked contracts, cybersecurity controls and customer requirements often push Saudi data into the Kingdom. In-country or regional hosting avoids a lot of transfer paperwork.
Can one platform cover both countries, or do I need two vendors?
One platform usually works and is easier to manage, provided it has type-approved devices in both markets, a working Saudi authority integration and hosting terms that satisfy both laws. Some fleets run a single platform with separate tenants or data regions per country to keep data segregated. Two vendors only make sense if no single bidder passes the regulatory gates in both countries.
Written by the Trackmeshflow editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.