Why we said no to live streaming Hawk footage to the cloud

The temptation was real

Building a dashcam app in 2024 means everyone expects the cloud. Real-time backup. Offload storage to a server. Stream everything home so you never lose a clip. Insurance companies want it. Police departments want it. There's a whole playbook for connected hardware, and we could have followed it.

For the first version of Hawk, we did seriously consider it. The engineering is straightforward: capture video, compress it, push it to MRVL infrastructure. You get redundancy, remote playback, maybe even instant incident alerts. Your phone's storage becomes almost irrelevant.

But then we started thinking about our actual users. A driver in Leeds who's been hit by an uninsured motorist doesn't need a cloud backup. She needs proof that's legally hers, locked down, and impossible for us to tamper with. A new driver building a track record for rideshare doesn't want his trips archived on someone else's infrastructure. And nobody should have to trust a company's data-retention promises when their safety is on the line.

The real problem with live sync

Here's what live streaming solves: peace of mind that your footage won't disappear if your phone is stolen or damaged. That's valuable. But it creates a dozen other problems.

First, evidence integrity becomes a question mark. The moment your footage leaves your device, you're trusting a third party's security, their access logs, their backup procedures. We built SHA-256 integrity hashes into every Hawk clip specifically so you can prove the footage hasn't been altered. But if that clip travels over the network, gets stored on a server, and syncs back to your phone, you've now got multiple copies, multiple timestamps, and a chain of custody that's harder to defend in court.

Second, there's the legal gray zone. If we hold your footage, we become custodians of evidence. That means data-retention laws, law-enforcement requests, subpoenas, and regulatory compliance in every jurisdiction you drive through. We'd have to hire lawyers to argue about whose data it is and when we're legally allowed to delete it. You'd be paying for that complexity whether you want it or not.

Third, it's a business-model trap. Once footage lives on our servers, we're incentivised to keep you subscribed. Unlimited cloud storage becomes a selling point. Then we're managing petabytes of video nobody asked us to keep. Eventually, someone gets hacked, or we go out of business, and thousands of drivers find their evidence isn't where they left it.

What we chose instead

With Hawk, your footage stays on your phone by default. Your storage, your responsibility, your evidence. The app handles loop recording so old clips automatically clear out, but the clips you want to keep are completely in your control.

For Hawk Pro users, we offer one exception: iCloud sync for clips in your Evidence Locker. That's the collection of footage you've explicitly marked as important. You decide what goes there. We don't touch it. It syncs to your own iCloud account, so Apple holds it, not us. If you ever need to export evidence for a dispute, one tap creates a ZIP file with the clips, GPS overlay, timestamps, and a manifest showing the SHA-256 hashes. That file is yours to send to your insurance company, the police, or a small-claims court.

The shift mode for Rideshare Pro works the same way. You're recording multiple trips in a session, and the app keeps them organised. But again, the footage lives on your device until you decide to lock it down or export it.

This approach isn't flashy. It doesn't give us a competitive moat or recurring revenue per gigabyte stored. But it means when you need your evidence most, it's genuinely yours.

Why this still matters

We launched Hawk knowing that dashcam users have real, legitimate concerns about privacy and security. Drivers record their journeys, their passengers, their routes, their daily routines. That's sensitive data. The fact that we're not a fleet-management platform matters. The fact that we're not a connected hardware company relying on server infrastructure matters. It means your iPhone or Android phone is your sovereign device, and we're a tool that runs on it, not a service you're dependent on.

It also means we can be honest about what we keep and what we don't. We don't have a massive data centre. We don't sell footage or analytics. We don't build customer profiles from driving patterns. We have no incentive to. The entire business model is built on helping you record evidence and export it when you need it, not on monetising your data or locking you into a subscription for redundancy you didn't ask for.

The question we still ask ourselves

This decision has trade-offs. Your phone's storage is finite. If you're recording eight hours a day in a double-shift rideshare session, you'll fill up faster than if we were offloading to the cloud. That's why Hawk Pro includes shift mode, so you can segment your trips and manage storage more deliberately. It's not as frictionless as 'record everything forever,' but it puts you in control of a real constraint instead of hiding it behind a server we operate.

Every few months, someone suggests we add live streaming, or automatic backup, or cloud-based replay. It's tempting. But I keep coming back to that original question from the beta driver. When your safety depends on evidence, the last thing you want is uncertainty about who owns it or where it really lives.