The ZIP file that changed how we think about dashcam evidence

The moment we realised integrity meant nothing if you couldn't prove it

We'd already invested heavily in SHA-256 hashing. Every clip recorded in Hawk gets a cryptographic signature written to its metadata, which means if someone tampers with the footage later, the hash breaks. It's the kind of thing that matters in court. But we kept getting the same question from early users: 'How do I show this to my insurer so they know it hasn't been edited?'

The answer we were giving them was technical and clumsy. Use the Files app. Find the clip. Try to explain to a claims adjuster what SHA-256 is. We'd solved the hard problem (maintaining evidence integrity) but created a new one (proving that integrity to someone who didn't have a PhD in cryptography).

That's when the real work started. Not writing the hash algorithm. Actually making the evidence useful.

What a dispute export actually needs to do

We spent weeks talking to people who process dashcam claims. Insurance adjusters. Police officers taking witness statements. A few small-claims court administrators. What we learned changed how we thought about the feature entirely.

They didn't want a folder of loose files. They wanted a package. A single ZIP archive that contained the video clips, the GPS data, the timestamps, and crucially, a manifest file that listed every clip with its hash so they could verify nothing had been altered since the moment you exported it.

The manifest is the difference between 'here's a video' and 'here's a video I can prove hasn't been touched.' The SHA-256 hash for each clip sits right there in that manifest. Anyone with basic command-line knowledge can check it. Better still, most professional claims software now has built-in hash verification, so the moment an adjuster opens your ZIP, their system already knows the evidence is intact.

We made it one tap. That was non-negotiable. You select the clips you want to dispute. You tap once. You get a ZIP file ready to email or upload to your insurer's portal. No intermediate steps. No guesswork about which file format to use or whether you've included everything.

Why we didn't just upload everything to our servers

Early versions of Hawk did cloud sync, but only for your Pro clips in iCloud, and only because you chose it. We never built the feature where everything auto-uploads to MRVL servers and we email you a link. Every conversation about that feature ended the same way: who owns the evidence? Where is it actually stored? What if you need it offline?

The dispute export ZIP sidesteps all of that. Your clips stay on your phone until you decide they matter. Then you create a package and send it where you choose. Insurance portal. Police department. Your solicitor. You control the chain of custody entirely.

That matters more than people realise. In a courtroom or a formal claims process, if evidence passes through someone else's server, questions get asked. With a ZIP file and a manifest hash, the evidence is atomic. It's a package you created, at a specific moment, that you can prove hasn't changed.

The details that took the longest to get right

We spent more time on the manifest format than we did on the export button itself. It needed to be simple enough that a claims adjuster could read it, but formal enough that it satisfied technical scrutiny. We settled on a plaintext file listing each clip's filename, duration, SHA-256 hash, and timestamp range. No XML. No proprietary format. Just readable, verifiable information.

We also added an option to include the trip map polyline if you've got GPS enabled. Some people have it switched on for their own records. If you do, and you export a dispute, the ZIP includes a map showing your route and speed during that journey. It's optional, gated by your privacy settings, and honestly, it's saved a few people's claims when they needed to prove they weren't speeding or that they were where they said they were.

The smallest thing we got right was making the filename itself useful. Your ZIP is named with a timestamp and a trip ID, so if you export multiple disputes from different days, you can't accidentally mix them up.

What changed after we shipped it

Within the first week, we got an email from a driver who'd used the export to settle a claim in less than 48 hours. Not because the evidence was different from before. Because the insurer could open one file, check the hashes, and move forward without asking a dozen follow-up questions about where the video came from or whether it was authentic.

We've since added the same one-tap export to NDSP police-report submission on iOS, so you can file a report directly from Hawk without repackaging your evidence. A few police forces have integrated the ZIP manifest verification into their intake system. It's not widespread yet, but it's spreading.

The feature also surfaced something we didn't entirely expect. Users started exporting and saving their ZIPs even when they weren't disputing anything. Just insurance archive files, just in case. Evidence locker with a proper backup. That's exactly what we hoped would happen.