The 47 mph question: why we added GPS speed overlay to Hawk
Three months after launch, a Hawk user emailed us a recording of a collision at a junction. Clean footage. Sharp audio. But the insurance adjuster asked a single question: what speed were you doing? The user had no answer. That email changed how we thought about evidence.
The gap between footage and proof
Dashcam footage is powerful, but it's incomplete. You can watch a car run a red light. You can see the impact. But to a claims investigator, speed, time, and direction matter as much as the pixel count.
When we first designed Hawk, we focused on the recording engine itself: stability, clarity, retention. We built SHA-256 integrity hashing into every clip so that when you export to an insurer or court, they know the footage hasn't been tampered with. That's the foundation. But one user's insurance rejection made us realise we'd missed something obvious.
Speed data from GPS isn't just a detail. It's often the deciding factor in fault determination. Was he speeding? Was she maintaining legal distance? Did the other driver exceed the limit before the incident? Without it, you're asking an adjuster to guess.
Building it responsibly, not by default
GPS overlay sounds straightforward. You have the GPS co-ordinates from the user's phone. Drop the speed and timestamp onto the video frame. Ship it.
Except it's not that simple. GPS location data is sensitive. A timestamp overlay combined with location data can reveal not just where an incident happened, but where a driver travels every day, what time they leave home, where they spend lunch.
That's why we gated the feature behind a GDPR profile setting. You choose whether to enable speed and timestamp overlay. You control whether that data gets written to your exported clips. If you turn it off, Hawk still records everything, but the overlay stays blank. The integrity hash is still there. The court-ready proof is still there. The personal location pattern isn't.
It took longer to build it that way. A privacy-first default always does. But it felt non-negotiable. You're buying a dashcam to protect yourself, not to broadcast your commute.
What the numbers actually tell adjusters
Once we shipped the feature, we started hearing from rideshare drivers. That made sense. Uber and Lyft drivers face dispute scenarios almost weekly: a passenger claims they were reckless, or a collision report goes sideways.
One Hawk Pro user in London messaged us after an incident at Clapham Junction. A car cut in front of him. His Hawk footage showed it clearly. But what won the dispute with his insurance wasn't the video alone. It was the GPS overlay showing his speed at 28 mph in a 30 zone, and the timestamp placing the other vehicle's entry at 2.47 pm, precisely matching the CCTV footage the council provided.
The adjuster closed the claim in his favour within a week. No court. No back-and-forth. The overlay transformed footage into forensic evidence.
We also built a trip map replay feature that uses MapKit to show the polyline of your journey during an incident. Insurance companies use that. Police use that. Small-claims courts use that. It's no longer your word against theirs. It's data.
Why timestamp matters as much as speed
Speed gets the attention, but timestamp is just as critical. A collision happens at exactly 14.23 and 17 seconds. You have the timestamp. The other driver claims it was 14.20. The traffic light cycle changes every 85 seconds. A three-second difference can mean the difference between running a light and crossing on green.
When you export a dispute package from Hawk, it's a ZIP file with every clip, a SHA-256 manifest proving nothing's been altered, and metadata including timestamps and speed. It's what insurance and police want before they even open the video.
That export structure isn't flashy. It doesn't sell. But it's the reason Hawk works in small-claims court. You're not handing over a video file and hoping the judge believes you. You're handing over cryptographically signed proof.
The conversation we keep having
We still get users asking whether we can enable the overlay by default, or upload everything to our servers for extra security. The answer is always no, for different reasons.
Default-on would compromise privacy for convenience. Uploading to MRVL servers would add subscription lock-in. We designed Hawk so that a free user with 10 clips a month gets evidence-grade recording with full export capability. You own the footage. It syncs to your own iCloud if you go Pro, not to our cloud.
That philosophy shaped the GPS overlay too. It's a feature you control, not a default we impose. You can have it on for rideshare incidents and off for family trips. You can clear the setting whenever you want.
It's harder to market that way. 'Customisable privacy controls' doesn't sound as exciting as 'court-ready GPS overlay'. But it's why we built it the way we did.
That user who asked the speed question after the collision? He's still using Hawk. Not because we fixed his dispute (the overlay came later), but because he knew we'd listen. Do you know what data you'd want visible in your own incident footage if you needed to prove it?