The moment I realised our export had to be bulletproof

Why a ZIP file with a manifest isn't fancy, it's necessary

Most dashcam apps hand you a video file and call it evidence. We spent months learning that courts and insurers don't work that way. They need proof that your footage is exactly what was recorded, unaltered, timestamped, and genuine. That's not paranoia on their part. It's due diligence.

When you tap the export button in Hawk, you don't get a loose MOV file. You get a ZIP package containing your video clips, metadata, and a SHA-256 manifest that cryptographically proves every file's integrity. The manifest is like a tamper-evident seal. If someone changes a single frame of footage after export, the hash breaks, and that's visible. Lawyers and adjusters understand that immediately.

We chose SHA-256 because it's the standard used in forensic analysis and courtroom evidence handling. Not because it sounds technical, but because it's what the legal system already trusts. When an insurance company sees that hash, they know we're not guessing at security.

The rideshare driver who needed this more than anyone

Our Rideshare Pro tier exists largely because one customer, a Lyft driver in Manchester, sent us a detailed breakdown of a passenger dispute that went sideways. He'd recorded the incident, but exporting it as individual clips felt weak. His insurance asked for a timeline. Police wanted proof the cabin camera was on during the relevant window. Our basic export couldn't answer those questions fast enough.

That prompted us to rethink the export itself. The ZIP manifest now includes GPS coordinates, precise timestamps, and cabin / road camera metadata tied together. When a rideshare driver exports, they're not hoping the adjuster believes them. They're handing over a package that proves the state of their vehicle, the route taken, and which cameras were active. One tap. Done.

The driver tested our new export format with his insurance company. They processed the claim in four days instead of the usual six weeks. That mattered to him more than any marketing language we could write.

How the manifest works, without the jargon

Here's what actually happens when you export a dispute in Hawk. Every clip recorded in your Evidence Locker has already been hashed as it was written to storage. That hash is cryptographic proof of what was recorded, byte for byte. When you export, we create a manifest file listing every clip, its hash, its GPS data, and its exact timestamp.

Open the ZIP on your computer. You'll see your video files plus a manifest.txt file. The manifest lists each clip and its SHA-256 hash. If you ever need to prove the footage is authentic, you or your legal representative can run the files through a hash checker. They'll match. If anyone claims you edited the footage, the hashes will tell the true story.

This isn't us being paranoid. It's us recognising that in a dispute, you're not just handing over evidence. You're handing over proof that your evidence is real. The ZIP format keeps everything together, portable, and organised. The manifest is the insurance company's or court's confidence check.

What we learned by actually talking to people who use this

Early versions of Hawk exported video. That felt like enough to us. Then we launched and started reading customer feedback. Insurance adjusters were asking for GPS overlays to prove the accident location. Police wanted timestamps they could cross-reference with traffic cameras. Small-claims courts wanted to know the device was set up correctly and recording continuously.

We kept iterating. GPS overlay became a core feature (gated by GDPR settings, of course, because not everyone wants location data in their exports). Timestamps became precise and layered into both the video and the metadata. The manifest emerged as a way to bundle everything with proof of integrity.

What surprised us most was how rarely the technical detail mattered to the end user. A commuter just wanted to know that when they hit export, their insurance would actually believe them. A rideshare driver wanted the adjustment process to be fast. Courts wanted to see the evidence was real. We built the manifest because solving that problem was more important than simplifying our feature list.

From export to actual resolution

The ZIP export is useful only if it actually ends disputes faster. We've watched customers send their exports directly to insurance companies through the app, to police through our NDSP integration on iOS, and to small-claims court as exhibits. In each case, the manifest does its job silently. The adjuster or judge doesn't think about SHA-256. They just see that the evidence is verified, organised, and credible.

Some customers never need the export. They mount their phone on the dashboard for continuous recording and never see an accident. Others export once and that single ZIP file changes the outcome of a claim. The feature has to work for both. So it does. One tap. The rest is system integrity doing what it's supposed to.