The hash that changed how we built Hawk

The moment we realised we were selling trust, not features

That question sits differently when you're a founder than when you're building a feature roadmap. Every dashcam app records video. We could stabilise it, add GPS, sync it to iCloud. But none of that mattered if the evidence itself couldn't be verified.

The legal world doesn't care about your app's design. A solicitor cares about whether a video clip is authentic. Whether anyone, including you, could have tampered with it between recording and submission. In a courtroom, 'we don't have logs of that' isn't a defence. It's a defeat.

We spent a week reading about cryptographic hashing. SHA-256 isn't new technology. It's been used for decades in security, blockchain, and digital forensics. But I realised almost no mobile dashcam app actually implemented it. Most competitors treated video as just another file.

We couldn't compete on that basis. We had to compete on integrity itself.

What happens when every clip carries its own fingerprint

SHA-256 is a mathematical function that creates a unique 64-character string from any file. Change one pixel, one frame, one millisecond of audio, and the hash changes completely. It's deterministic: the same video always produces the same hash. Different videos, even if they look identical to the human eye, produce different hashes.

We decided that every single clip Hawk records would have this hash written to it at the moment of recording. Not later. Not optionally. Built in, permanent, immutable.

This meant something specific for a driver taking a clip to court. They could export a ZIP file (one tap, really) that contained the video, the metadata, the GPS overlay, and a manifest listing every file's SHA-256 hash. An expert witness could verify independently: this file hasn't been altered since it left Hawk on your phone.

No subscription required. No cloud upload required. No trusting MRVL's servers. The cryptographic proof is mathematical, not institutional.

The engineering conversation nobody wants to have

Once we committed to this, the engineering got thorny. Writing the hash at the moment of recording is trivial. Storing it reliably, retrieving it when the user exports, making sure it survives iCloud sync for Pro users, handling it across Android and iOS, testing it with officers and solicitors to make sure they actually trusted it - that was weeks of real work.

We tested it with police services. We spoke to small-claims advocates. We even had a lawyer friend run through a mock dispute scenario, exporting the ZIP, checking the manifest, calculating her own hash to verify ours matched.

The moment she confirmed it worked was the moment I knew we weren't just adding a feature. We were changing what a driver could actually do with their phone.

Why this matters more for rideshare than for anyone else

A commuter with a daily route has one perspective. A rideshare driver has a different problem entirely. They're working with the public. They might be disputed by passengers. Insurance companies want evidence. They need to prove what happened in a cabin - and that's why Rideshare Pro includes cabin recording, along with shift mode for managing multiple trips in a single session.

But the hash layer matters even more here. A rideshare driver who can hand over a manifest with cryptographic proof that footage is unaltered? That's not just feature parity. That's legal protection.

What this actually means for you as a user

In practical terms: you record. The app hashes every clip automatically. You lock your evidence in the Evidence Locker with biometric authentication (it fails closed, so if your phone is stolen, your footage stays locked). If you need to dispute something, you export. You get a ZIP with video, map, metadata, and a manifest. You send it to your insurer or solicitor.

You don't think about hashes. Hawk does.

The only time the hash matters to you is the moment when you realise you have something that holds up. Not in theory. In reality. In a solicitor's office, reading your manifest and nodding.