Khalid has lived in Dubai for eleven years. He knows the city well enough to know that trusting someone with his daughter's daily commute — school in the morning, Quran class in the afternoon, back home by six — is not something he does lightly.
For two years, the family had a driver they knew well. A steady, familiar presence. When that driver returned to his home country in early 2024, Khalid found himself in a situation many Dubai families navigate: a new driver, good references on paper, and a daughter who needed to be somewhere at 7:15 AM regardless of how comfortable her father felt about the arrangement.
“I didn't distrust him,” Khalid says. “I just didn't know him yet. There's a difference.”
The problem with just asking
Khalid considered his options. He could call his daughter between drop-offs to confirm she'd arrived. He could ask the driver to send a WhatsApp message at each location. He could track her phone.
None of these felt right. Calling his daughter mid-morning interrupted her class. Asking the driver to send updates felt like surveillance that would make the working relationship awkward from day one. Tracking his daughter's phone gave him her location, not the car's — and told him nothing about how the car was being driven.
What he wanted was simple: to know where his car was, in real time, and to know whether it was being driven the way he would drive it. Without making it a conversation.
A colleague mentioned ViaLoop. Khalid ordered the OBD device the same evening.
The first week
The device took less than three minutes to set up. OBD port under the dashboard, app on his phone, done. No technician, no wiring, no telling the driver anything had changed.
The first morning, Khalid watched the live location from his office as the car left home at 7:08 AM, took the route through Al Barsha he would have taken himself, arrived at the school at 7:23 AM — right on time — and then continued to the driver's waiting spot nearby. At 1:45 PM, the car moved to collect his daughter from her afternoon class. Home by 5:50 PM.
He didn't intervene. He didn't need to. He just watched.
By the end of the first week, a pattern had formed in the data: consistent routes, no significant detours, departure and arrival times that matched what the driver reported, speed that stayed within reasonable bounds through the city. The driving behaviour score that ViaLoop generates was sitting comfortably above 80 — smooth acceleration, no harsh braking events worth noting, no overspeed alerts on the Sheikh Zayed corridor.
On the privacy question: Khalid chose not to tell the driver about the device initially. This is a decision each owner makes differently — some prefer transparency from day one, others want an unobserved baseline before any conversation. In Khalid's case, the data gave him confidence he would not otherwise have had, and the driver's behaviour on and off camera turned out to be identical.
The moment that mattered most
Three weeks in, something small happened that Khalid still brings up when he talks about the device.
His daughter's class finished early one afternoon — a last-minute change the school sent by SMS. The driver rerouted immediately, taking a road Khalid didn't immediately recognise. For about four minutes, Khalid watched the live map with the low-level alertness of a parent who notices something unfamiliar.
Then the route resolved. There was construction on the usual road — visible on the map, marked clearly. The driver had taken the logical alternative and arrived at the class two minutes later than the standard route would have. Nothing had happened. But for Khalid, something important had: he had seen an unexpected situation, watched it unfold in real time, and the outcome was completely ordinary.
“Before ViaLoop, that four minutes would have been a phone call to my daughter, then a call to the driver, then me sitting anxious until she messaged. With the app, I watched it happen and went back to my meeting.”
Six weeks in: the conversation
By the sixth week, Khalid felt the driver had more than earned his trust. Clean driving data, reliable schedules, zero incidents. He told him about the device.
The driver's response surprised him. “He wasn't upset. He said he wished more families used it — that it would make misunderstandings about routes and timings impossible. He actually asked to see his own driving score.”
They looked at it together. The score was 84. The driver pointed out the two harsh braking events in the log — both on the same junction near the school, where a pedestrian crossing activates unexpectedly. He knew exactly what they were. After that, he started braking a hundred metres earlier at that junction. The events stopped appearing.
Why he still hasn't unplugged it
The driver is fully trusted now. Khalid's daughter is comfortable with the arrangement, the schedule runs smoothly, and there has been no safety incident in six months of the device being in the car. By the logic of the original problem — monitoring an unknown driver — the job is done.
The device is still plugged in.
What changed is what Khalid uses it for. The safety monitoring function has receded into the background. What he pays attention to now is different:
- Engine health alerts. Three months in, ViaLoop flagged a check engine code — a minor oxygen sensor issue that hadn't triggered the dashboard warning yet. Khalid booked the car in for service the following weekend. The mechanic confirmed the fault and fixed it before it became a larger problem. “I found out about my car's health before my car told me,” Khalid says.
- Fuel efficiency tracking. Khalid noticed the car's fuel consumption had increased slightly over a six-week period — not dramatically, but enough to show up in the weekly summary. The mechanic found that the air filter was overdue for replacement. After the service, consumption returned to baseline.
- Trip history for his own driving. Khalid drives the car himself on weekends. He found the weekly summary of his own driving — average speed, fuel efficiency, harshest braking events — genuinely interesting. His score on weekend driving was lower than the driver's weekday score. He started braking earlier on the motorway and watched the number move up over the following months.
What this case is really about
Khalid's story isn't primarily about driver monitoring. It's about what happens when a car owner finally has continuous visibility into a vehicle they own but don't fully see.
Most car owners in Dubai know three things about their vehicle at any given moment: whether it started this morning, roughly how much fuel is in it, and whether any warning lights are on. Everything else — where it was yesterday, how it was driven, whether the engine is running slightly outside normal parameters — is invisible.
A three-minute install changed that for Khalid. The original reason — a new driver, a daughter's commute — was the trigger. What kept the device in the car was everything the data revealed that had nothing to do with trust.
He hasn't thought about unplugging it since week two. The question doesn't come up.