What that ZIP file actually does for you in a dispute

Why a simple MP4 doesn't cut it anymore

When we first built Hawk, I assumed users would just email individual video clips to their insurance company or solicitor. That seemed obvious. Then we started getting support messages from people who'd done exactly that, only to have the other party claim the footage was 'edited' or 'taken out of context' or somehow fabricated. One user told us her insurer's fraud team had questioned whether the timestamp on her clip was genuine.

That's when we realised the real problem. A video file sitting on your phone can be altered. Metadata can be stripped. A single clip doesn't show continuity or prove nothing happened before or after the incident. Insurance companies and small-claims courts have seen enough deepfakes and edited videos that they're now genuinely sceptical of raw footage. We needed something that proved the evidence was authentic from the moment of recording.

The manifest is the chain of custody

Every clip Hawk records gets a SHA-256 hash written to it at the moment of capture. If you've ever seen a cryptography hash before, you know it's a long string of characters that changes completely if even a single pixel of the video is modified. It's mathematically impossible to alter the video and keep the same hash.

When you tap the export button, Hawk doesn't just zip up your clips. It creates a manifest file (a text file you can actually open and read) that lists every video file in the export, the hash for each clip, the GPS coordinates, timestamps, and speed data if you've enabled it. This manifest is itself hashed. If someone later claims you've added, removed, or edited clips in that ZIP, you can hand over the manifest and let the court or insurer verify that nothing has changed since you exported it. The hash proves it.

We ship the manifest as plain text, not some proprietary format. A judge or insurance assessor can understand what they're looking at. No special software required.

A real incident: continuity matters

One of our early Rideshare Pro users (a Lyft driver in London) had a passenger claim they'd been injured during their journey. The passenger alleged a sharp swerve caused them to fall against the window. The driver used Hawk to export her entire shift (Rideshare Pro records multiple trips in one session) and submitted the ZIP with the manifest to her insurance company. The footage showed continuous, smooth driving throughout the entire trip. No swerve. The manifest proved the clips had never been edited or rearranged. The claim was dismissed. Without the manifest, without the hashes, it would have been a he-said-she-said situation.

That's the thing most people don't immediately grasp about the ZIP export. It's not just about the videos. It's about proving that the sequence of events is genuine, uninterrupted, and untampered.

Why we didn't just put everything in the cloud

We could have made Hawk auto-upload every clip to MRVL servers, stamped it with our timestamp, and sold it back to users as 'cloud-backed evidence'. That would have been the easier sell. But we didn't, because a lot of people don't want their driving footage sitting on someone else's server. Rideshare drivers especially are cautious about privacy. So we built it the other way. Clips stay on your phone by default. Your Pro clips sync to your own iCloud account if you turn on iCloud sync. When you export, you're creating a self-contained evidence package that you control entirely. No intermediary. No subscription required to export. No waiting for cloud infrastructure.

The manifest lives inside your ZIP file. You own the evidence from the moment you hit export.

What actually happens when you hit the button

The one-tap export is straightforward from a user perspective. You open the evidence locker, select the clips you want (or Hawk can auto-select clips around a timestamp if you mark an incident), and tap Export. The app creates a folder structure, verifies the SHA-256 hash of each clip matches what was recorded, generates the manifest file, compresses everything into a ZIP, and drops it into your files app or email. You can then send it wherever you need: your insurance company, the police, a solicitor, a small-claims court.

Some users don't need the manifest at all. A simple insurance claim for a minor scratch sometimes settles on goodwill and a couple of videos. But if there's any dispute, if the other party contests the narrative, if a court is involved, that manifest becomes your best defence. We've had users tell us they've printed the manifest out, highlighted key entries, and brought it to mediation. The fact that it exists, that it's verifiable, that it's not locked in some proprietary format or hidden on a server, changes the tenor of the negotiation.

The feature nobody notices until they need it

When we added the manifest feature, I wasn't sure how much users would care. Most people don't think about cryptographic hashing when they download an app. They just want to know the dashcam works. But the support messages kept coming, and they weren't about the video quality or the battery drain. They were from people who'd actually needed to defend themselves in a dispute, who'd used the export, and who'd had that ZIP file taken seriously by insurers or courts precisely because the evidence was forensically sound.

That's become the quiet differentiator. Not marketing. Not a selling point we shout about. Just the thing that works when it matters most.