Why we hash every frame: the integrity layer nobody talks about
Last autumn, a user messaged me from Edinburgh. She'd been in a three-car pile-up on the M8, and her insurer was demanding proof that her Hawk footage hadn't been edited. She'd never heard the word SHA-256 before, but she needed to know: could she prove her clips were genuine?
The problem we heard about, over and over
When Hawk first launched, the feedback was consistent. Users wanted to record their commutes and their rideshare shifts, yes. But what they really wanted was insurance companies and police officers to believe them. The moment a claim goes to an insurer or a small-claims court, your dashcam footage becomes evidence. And evidence gets scrutinised.
Video is easy to manipulate. Anyone with basic software can cut scenes, overlay text, adjust timestamps. If you hand an insurer a video file from your phone, they'll accept it, but they'll also wonder: how do we know you didn't edit this? How do we know the timestamp is real? The scepticism isn't malice. It's risk management.
We realised that having a camera wasn't enough. We needed Hawk to produce footage that could withstand that scrutiny.
What a hash actually does (and doesn't do)
A hash is a mathematical fingerprint. When Hawk records a clip, it calculates a unique 256-character string, called a SHA-256 hash, based on the exact contents of that file. If even a single pixel changes, the hash changes completely. If someone edits the clip, the hash no longer matches. You can't fake it. You can't bypass it.
Here's what matters: the hash is written to the clip's metadata at the moment of recording. When you export your evidence from Hawk, the manifest file includes both the clip and its hash. You're not trusting Hawk to tell you the footage is real. You're giving the insurer or the court a mathematical proof.
This isn't theoretical. It's the same mechanism used by law enforcement to validate body camera footage, by digital forensics examiners, and by courts across the UK and EU. We didn't invent it. We embedded it into an app.
The export moment: when integrity matters
Most days, you record driving footage and you never think about it again. Loop recording overwrites old clips. Life goes on. But the moment you need the footage, everything changes. Someone's claiming you hit them. Your insurer is asking questions. A police report is on the table.
That's when you tap the export button in Hawk. One tap. The app builds a ZIP file with your selected clips and a manifest listing every file's SHA-256 hash. You send that ZIP to your insurer, your solicitor, or the police. The recipient can verify that every clip inside is exactly what you recorded, unchanged, unedited.
We designed this flow during the beta phase, when rideshare drivers were our loudest testers. They were the ones saying: "I need proof this is genuine. My job depends on it." That pressure pushed us to make the export mechanism transparent and portable. You're not locked into Hawk's servers. The evidence is yours to send wherever it needs to go.
Why we didn't take the easy route
We could have made Hawk simpler. Auto-upload everything to our servers. Let us handle the integrity verification. Offer you a certificate that says "Hawk says this is real." Some dashcam services do exactly that.
We didn't, because we understood the use case. When you're filing an insurance claim or talking to police, you don't want their trust in Hawk. You want them to trust the mathematics. You want them to be able to verify the footage independently, using free tools, without needing to believe us.
The Professional tier syncs your locked clips to your own iCloud for backup. That's it. You control the data. You control the export. The hash is the only thing we insist on, because it's the only thing that actually proves integrity.
The reality of what this means on the road
So back to the woman from Edinburgh. She pulled up Hawk's export feature, selected the clips from her multi-car accident, and downloaded the ZIP. Inside it was her video evidence and a manifest with SHA-256 hashes. She sent it to her insurer along with a brief note explaining what the hashes were and why they mattered.
The insurer didn't question the footage's authenticity. The claim moved forward. She told us later that having something concrete to hand over, something that couldn't be dismissed as "just video from a phone," changed how seriously they treated her account.
That story happens every week now, in different forms. Commuters in disputes. Rideshare drivers protecting their income. People who just wanted a dashcam without buying a dedicated device, and ended up with something more: evidence that holds up.
If you've ever wondered why dashcam footage gets questioned in court, now you know. The question isn't whether cameras lie. It's whether we can prove they don't. Does your current setup give you that proof?