UAE/GCC Compliance Guide: Asateel & SecurePath 2025 Checklist
Primary keyword: Asateel SecurePath compliance
Last updated: 29 Oct 2025
What fleets need in Abu Dhabi (Asateel, ITC) and Dubai (SecurePath, SIRA) — vehicle categories, onboarding steps, required documents, and audit prep. Download the CSV checklist to track your progress across regions.
Disclaimer: Regulations change. Use this guide as an orientation and confirm specifics with the issuing authorities and your approved supplier.
- Resource Type: Checklist / Guide
- Category: Compliance
- Audience: Fleet Owners & Managers; Compliance Officers; Ops Managers
- Tags: asateel, securepath, uae, gcc, permits, gps, device, onboarding, audit, data‑retention
- CTA assets: 2025 Asateel & SecurePath Checklist (CSV)
Overview
Asateel (Abu Dhabi) and SecurePath (Dubai) require approved GPS/telematics devices, data transmission to the authority platform, and adherence to data retention, driver/vehicle identification, and operational rules. Compliance is mandatory for specific vehicle classes and activities.
On‑time arrivals
SLA windows: alert early / late
Detention hours
Chargebacks or process fixes
After‑hours trips
Stop unauthorized use & theft
Vehicle categories (typical)
- Passenger transport (e.g., 9+ seats, school buses, staff buses)
- Goods and commercial vehicles (e.g., pickups, trucks, trailers)
- Special purpose vehicles (e.g., fuel tankers, waste, hazardous)
- Rental/leasing fleets (as specified by the authority)
Note: The exact list varies by emirate and activity license. Always confirm your category and exemptions.
Prerequisites
- Valid trade license with relevant activity.
- Vehicle registration cards (Mulkiya) and plate numbers.
- Authorized representative details (Emirates ID where required).
- Approved GPS device and installation by an approved supplier.
Onboarding — step by step
- Choose/verify an approved supplier and confirm device compatibility (CAN/OBD, camera, panic button if required).
- Register your company on the authority portal; create user accounts/roles.
- Submit documents (trade license, vehicle list, IDs) and request activation.
- Install devices to standard (power, ignition, GPS/GSM, tamper‑proofing).
- Verify data flow to Asateel/SecurePath (position, speed, VIN, driver ID, events).
- Link vehicles to permits or activity categories; complete test trips if asked.
- Receive approval; keep records (work orders, photos, configuration).
Data & retention
- Transmit required fields at mandated frequency (e.g., GNSS position, speed, time, device ID).
- Retain historical data for the minimum period (varies by emirate; keep at least 6–12 months internally).
- Use driver identification (e.g., iButton/Emirates ID integration) if required.
Device & installation standards
- Approved hardware/firmware versions and sealed installation.
- Hidden routing, protected power, backup battery, tamper alerts.
- Optional: AI dashcams, panic button, door sensors, temperature, PTO.
Audit readiness
- Evidence pack: installation photos, serials/IMEIs, wiring diagram, configuration sheet.
- Portal screenshots: vehicles active/online, last contact, driver links.
- Process docs: SOP for new vehicle onboarding and device replacement.
💬 FAQs
Do all vehicles require tracking?
No. Only categories mandated by the emirate/authority. Confirm with your activity license.
What happens if the device goes offline?
Investigate within policy (e.g., 24 hours). Keep a loaner/spare plan and document downtime causes.
How often do rules change?
Authorities update specifications periodically. Review supplier circulars and portal announcements.
Can we reuse existing devices?
Only if they are on the current approved list and can transmit in the required format.
Is driver consent required?
Follow local labor and privacy laws; communicate policy and purpose to drivers, and secure IDs appropriately.
Tip: keep a compliance register mapping each vehicle to its permit, device serial, and last data contact time.
Share
LinkedIn
X