Why we synced your evidence to iCloud, not our servers

The problem no one asked for (until they needed it)

When we built the evidence locker, we focused on what made sense: biometric lock, SHA-256 hashes on every clip so the file couldn't be tampered with, one-tap export to a ZIP manifest you could hand to the police or your insurer. It was fortress-like. Local. Secure on the device itself.

But we'd made an assumption. We thought 'local' meant safe. What we hadn't fully reckoned with was the thousands of drivers who carry one phone doing multiple jobs, or who upgrade devices every couple of years, or who had simply experienced the hollow panic of a cracked screen with irreplaceable footage trapped inside.

The Bristol driver's message arrived the same week we got three support emails with similar threads. Not panic. Just the quiet realisation that a locked clip on a single phone is only as durable as that phone.

The tension between security and custody

Here's where it got interesting. We could have built our own server. Cloud-synced every locked clip to MRVL's infrastructure. It would have been the obvious move for a software company. More engagement metrics. More data. A moat around the product.

But there was a problem buried inside that logic. The whole point of the evidence locker is that you own the evidence. Biometric lock means you control access. SHA-256 hashing means the file is tamper-proof. If we became the custodian of your clips on our servers, we'd become a point of failure. If we get hacked, you're exposed. If we get subpoenaed, your footage is discoverable. If our service goes down, you can't export your evidence when you need it.

We had a long conversation about this. The outcome was simple: your evidence should sync to your cloud. Not ours. iCloud for iPhone users. Google Drive for Android. The infrastructure you already trust with your photos, your messages, your most sensitive data. We act as the vault logic. You own the keys.

What actually happens when you lock a clip

When you tap the lock button on a clip in Hawk Pro, the evidence locker moves it to a protected zone. That file gets a SHA-256 hash written to its metadata. The clip itself is encrypted at rest on your device. If you're syncing, that locked clip now syncs to iCloud via your iPhone's native backup, or to your Google Drive via our sync toggle on Android.

It sounds simple. It wasn't. We had to decide what gets synced and what doesn't. We don't sync your continuous recording buffer. That's local, ephemeral, yours to review and discard. Only locked clips go to your cloud. Only the evidence you've deliberately protected.

The hashes stay. The timestamp stays. The GPS overlay stays, assuming you've allowed it in your GDPR profile settings. Everything you'd need to export to a ZIP manifest and hand to a solicitor or a police officer stays intact. The moment you lock a clip, you've created a verifiable record that cannot be altered.

A driver in Manchester used this last month. She locked three clips after a minor scrape. Her phone was stolen two days later. Because those clips were synced to iCloud, she could restore them on a replacement device and export the evidence three weeks later when the other party's insurance demanded proof. The timestamp, the speed overlay, the hash. All present. All verifiable.

The trust problem with dashcam evidence

There's a deeper reason we chose iCloud and Google Drive over building our own backend. Dashcam footage is evidence. Evidence is only as credible as its chain of custody. If you lock a clip in Hawk, then export it as a ZIP with a SHA-256 manifest, a police officer or an insurance adjuster needs to believe that file is genuine and hasn't been tampered with.

They don't know us. They know iCloud. They know Google. When a clip syncs to your personal cloud and you export it with a manifest showing the original hash, you're not asking them to trust a company. You're asking them to verify a record. That's a fundamentally different position.

We've designed it so the chain of custody is yours. You locked it. Your biometric confirmed it. Your cloud stored it. You exported it. No MRVL server in the middle. No terms of service that change next year. No question about whether we have access to your footage or whether we've been served with a warrant.

The launch itself was quiet

We shipped iCloud sync for Hawk Pro in a Friday afternoon update. No fanfare. No marketing email. A few lines in the release notes. A toggle buried in settings under 'Evidence'.

The reason we kept it quiet is that it's not a feature meant to impress. It's meant to solve. The moment you enable it, you stop thinking about it. Your locked clips just exist in two places now. Your device and your cloud. If your phone breaks, you still have them. If your phone is stolen, you still have them.

The Bristol driver didn't need us to announce anything. She just needed the answer to her Friday night question. Now she has it.