Filing a police report with your dashcam footage

Why dashcam evidence matters to police

Police statements rely on witness memory. Witness memory is fragile. A dashcam turns a conversation into a record. When you hand an officer a video of what happened, with a GPS overlay showing speed and location, and a cryptographic hash proving the file hasn't been tampered with, you've moved from "I think that's what happened" to "here's what happened."

The National Driver Safety Partnership (NDSP) recognised this. They've integrated a submission channel for dashcam evidence, and Hawk connects directly to it on iOS. You don't have to email a file, explain what app you used, or hope the officer knows how to handle video evidence. You export, you submit, the system recognises the format and metadata, and your report is logged with court-grade proof attached.

It's a small friction point removed. But that removal matters when you're stressed, injured, or trying to get home after a collision.

How the evidence export actually works

Here's the moment we spent longest thinking through: what does a police officer actually need? Not what we think they need. Not what sounds impressive. What do they actually use?

When you tap "Export for Dispute" in Hawk, the app builds a ZIP file. That file contains your video clip, GPS coordinates, speed overlay data, timestamp, and a SHA-256 manifest that proves every frame is original. No editing, no splicing, no creative interpretation. The manifest is the lock. If anyone tries to change a single frame, the hash breaks, and anyone checking will know.

The NDSP submission flow reads that ZIP natively. You select your clips, hit "Submit to Police," and the system validates the package before sending. There's no ambiguity about format or proof. The officer receives evidence that's already verified.

This is different from emailing a video file to a generic police email inbox, where it lands as an attachment no one has verified, and someone has to manually check if it's trustworthy. This is structured, cryptographic, and built for the job.

What happens after you submit

You submit, and then what? That's the question we hear most often, because the experience of filing evidence should be clear, not mysterious.

The NDSP system creates a receipt. You get a reference number tied to your submission and your report. That number is trackable. If your insurance company needs to cross-reference the evidence later, they can. If the police officer needs to pull up exactly what you submitted, they can. The chain of custody is documented.

We built this on iOS first because that's where we saw the demand, and where the platform tools were most mature. The submission happens over an encrypted connection, and your location data is only included if you've enabled the GPS overlay in your GDPR privacy settings. If you've disabled it, the timestamp and video remain, but not your coordinates.

The whole experience takes about ninety seconds from clip selection to confirmation. And then you have a record that you submitted evidence, with a timestamp proving you did it promptly.

The integrity hash is the thing that mattered most

When we were designing Hawk, we made a decision early: every single clip gets a SHA-256 hash written to it the moment it's recorded. Not encrypted. Not hidden. Written to the file itself. Open and verifiable.

Why? Because in court, or in an insurance claim, someone will ask: "How do we know this footage is real?" If you hand them a video file with no proof of origin, they have to trust you. If you hand them a video file with a cryptographic hash that can be independently verified, you've answered the question before it's asked.

The police evidence submission system recognises this hash. It validates it on receipt. If someone tried to edit your footage after you submitted it, the hash would break, and the system would flag it. You can't accidentally corrupt your own evidence.

This sounds technical, but the user experience is simple: you export, you submit, the system says "verified," and you move on. The security is invisible because it works.

When you actually need this

A dashcam and a submission process don't matter until they do. You drive thousands of miles without needing evidence. Then one morning a driver runs a red light, or someone clips your door in a supermarket car park, or you witness something that needs reporting.

The people who love Hawk most aren't the ones who never have incidents. They're the ones who've had one, and suddenly understood the difference between "I saw what happened" and "I can prove what happened."

New drivers sometimes message us after their first minor bump. Experienced rideshare drivers use it constantly, because the cabin camera and shift mode mean they're documenting every trip. One user told us it meant the difference between a £4,000 insurance claim being rejected and being paid in full.

Hawk is free to start with, which matters. If you want the Evidence Locker, iCloud sync, and the dispute export, that's Local Pro at £3.99 a month or £39.99 a year. The NDSP submission itself is included.