The map that tells your story: how trip map replay works in Hawk

Why location matters more than you'd think

When you're in a collision or a dispute, time becomes elastic. A witness says one thing; you remember another. But a line on a map doesn't lie. It shows exactly where you were, at what speed, when the incident happened.

That's why we built trip map replay into Hawk from the start. Not as a nice-to-have, but as part of the evidence chain. Every clip Hawk records includes GPS data (when you've enabled it in your privacy settings). We layer that onto a MapKit polyline so you can see your exact route, frame by frame, superimposed on real geography.

The idea came from listening to drivers. Commuters told us about disputes where they couldn't prove they'd been in the correct lane. Rideshare drivers mentioned insurance arguments where their word against someone else's meant weeks of back-and-forth. All of them said the same thing: show me on a map, and it's over.

How it actually works when you need it

You've got a clip locked in your Evidence Locker. You tap it, and Hawk plays back the video with a live map overlay that moves in sync with your driving. The map shows your polyline in real time as the video rolls, so you can see exactly where you were at any moment in the incident.

When you're ready to file a dispute, Hawk exports everything as a single ZIP file with your video, the GPS manifest, SHA-256 integrity hashes, and metadata. That ZIP file goes straight to your insurer, your solicitor, or the police. No explanation needed; the evidence is self-contained and cryptographically verified. The map is there in the export, too, so whoever reviews it can see the visual proof of your route and speed without having to trust your account.

We made sure the export doesn't send your data anywhere near our servers. It stays on your phone, synced to your iCloud if you're using Local Pro or Rideshare Pro, then sent directly to whoever you choose. You control where the evidence goes.

The technical truth underneath

GPS data is only as good as your phone's receiver. In cities, signal can bounce off buildings. On motorways or in open countryside, it's usually clean. We account for this by writing every GPS point with a timestamp and validating it against the video's frame rate. If there's a gap or a jump, it's flagged.

When you export, the manifest includes the SHA-256 hash of every clip plus its GPS trace. This isn't just about proving you had the evidence; it's about proving the evidence hasn't been altered. A court or an insurer can independently verify that hash. We've seen this matter in small-claims cases where the other party tried to claim the video had been edited. One hash check, and the dispute ended.

One thing we're honest about: trip map replay isn't a replacement for a video. It's a companion to it. The map shows your path; the video shows what happened. Together, they tell a complete story. Alone, a line on a map can be argued with. Together, they close the argument.

When we got the detail wrong, and what we learned

During the first week after we shipped trip map replay, a user reported that the polyline was offset by about fifty metres on their commute through London. We pulled the data and saw it immediately: their iPhone's GPS had a consistent bias, probably from the urban canyon effect. We checked another user's device and it was accurate. So we knew the feature worked, but we also knew it would sometimes be imperfect.

We could have removed the feature or added a disclaimer. Instead, we added a confidence indicator to the export manifest so an insurer could see whether the GPS signal was strong or weak during the incident. That way, the evidence speaks honestly about its own reliability. If your GPS was weak, the manifest says so. An insurer sees that and adjusts their assessment accordingly. It's more honest than pretending technology is perfect when it isn't.

Who actually uses this, and how they describe it

We've seen trip map replay used in ways we didn't predict. One driver exported a clip with the map and sent it to her insurer with a two-sentence email. They settled within a week. Another used it in small-claims court; the magistrate said it was the clearest evidence of fault he'd seen in months. A third driver exported it and sent it to a solicitor, who used it to push back against a fraudulent claim.

But the most common use is the one we heard first: it ends the argument before the argument starts. You've got a collision. Instead of describing it, you pull up Hawk, show the map and the video together, and the other driver's insurance representative sees the proof immediately. Their tone changes. Suddenly they're not questioning your account; they're asking if you're injured.

That shift, from doubt to acceptance, happens because a map is harder to argue with than words. It's visual. It's spatial. Your brain accepts it as evidence in a way it accepts a verbal account with less certainty.