The two seconds that changed how we thought about dashcam evidence

The moment we realised dashcams needed a timestamp, not just a video

When we first built Hawk, we were chasing the obvious: continuous recording, no subscription, court-ready hashes on every clip. Our assumption was that raw video would be enough. Insurance companies and police would trust the footage because it came from your phone, and your phone had SHA-256 integrity hashes written to every clip.

Then we got the first support message from a rideshare driver in London. She'd been in a minor collision. The other driver claimed she'd run a red light. Her dashcam footage clearly showed she hadn't. But when she submitted the clip to her insurance company, the adjuster asked a question we hadn't anticipated: 'At what point in the video did you pass the intersection? And what speed were you doing?' Without timestamps and speed data overlaid on the video itself, the adjuster had to manually scrub through footage and estimate. She wanted evidence, not interpretation.

That's when we understood. A video is only as useful as the metadata someone can read from it in thirty seconds. A lawyer or insurance adjuster doesn't have time to decode your clip. They need to see the facts written on it.

Why GPS speed matters more than you'd think

Speed claims come up constantly. You're accused of speeding. You're blamed for a collision that happened because the other driver misjudged. You're fighting a claim that hinges on your velocity at a specific moment. In every case, you need proof, and proof isn't just 'I know I was doing 30 miles per hour.' It's a number locked into the video, timestamped to the millisecond, generated by your phone's GPS receiver.

The feature is gated by a GDPR profile setting because GPS data is sensitive. We built it so you choose whether your clips carry speed and location information. If you export a dispute ZIP, the manifest includes the GPS polyline so an insurer can see your route. If you don't enable the setting, the overlay simply doesn't appear. This matters because it's your data, and you should control what you're sharing.

What we've learned from customers is that the overlay itself is almost the entire value. One taxi driver told us: 'I don't think I've ever had to use the speed overlay in court. But knowing it's there, visible in the clip, means the other party never even starts the argument.' The presence of evidence changes behaviour. People don't dispute claims when they can see you have proof.

The technical decision we made quietly

Early on, we could have sent GPS data to MRVL's servers and calculated speed overlays in the cloud. Cleaner, scalable, and common in commercial dashcam systems. We didn't. We made the overlay on your phone, in the clip itself, so that the moment you export the dispute ZIP, everything you need is already baked into the video file. No internet required. No third-party service. No waiting.

This decision came down to one principle: your evidence should be portable. You should be able to hand someone a ZIP file with your clips, the manifest showing SHA-256 hashes, and the GPS polyline, and have them understand exactly what happened without needing to log in anywhere or trust another company's system. It's the difference between evidence and a link.

We also made sure the overlay doesn't distract from the footage. It sits in the bottom corner. Time, speed, and co-ordinates. Nothing more. Some commercial dashcams fill the screen with telemetry. We kept it minimal because the video is the story, and the overlay is just the proof.

When a timestamp saved more than a claim

Six months after launch, we got a message from a new driver in Manchester. He'd been in what he thought was a minor bump in traffic. The other vehicle's insurance company came back with photos and a claim that he'd hit them hard enough to cause injury. His word against theirs. He exported his Hawk clip with the GPS overlay. The timestamp showed the exact second of impact. The speed overlay showed he was doing 8 miles per hour in congestion. The polyline showed he was still in the same lane. The insurance company dropped the claim. He never had to go to court.

That's when we realised the overlay wasn't about dispute resolution. It was about prevention. If you're accused of something, and you can prove the opposite with data your phone recorded, most people won't push it further. The evidence is too clear.

It's also why we never made the overlay optional in the export. Once you've recorded a clip and exported it, the GPS speed and timestamp come with it. You can't accuse someone of something they can prove they didn't do, not with a GPS receiver and a timestamp backing them up.

The question we still get asked

People sometimes ask whether the timestamp and speed overlay make Hawk a 'surveillance' tool. We think it's the opposite. A timestamp is transparency. It proves what you were doing when you say you were doing it. The GPS overlay doesn't track you over time unless you choose to share your trip map with someone. It's just data about a single moment, locked into a clip, visible to anyone who watches the video.

Rideshare drivers use it most. They've got passengers, they've got insurance companies, they've got platform algorithms that track them. A GPS overlay and timestamp in their dashcam clips means they have their own record of what happened. It's not surveillance of them. It's evidence for them.