You’ve been told a camera can do something. Then you’re told it doesn’t. Same company, same product, same mouth. And somehow, you’re supposed to feel reassured.
That’s the situation Flock Safety customers found themselves in this week, when CEO Garrett Langley — after repeatedly announcing that his company’s ALPR (Automated License Plate Reader) cameras can record video — suddenly insisted they don’t.
Notice the wordplay. He didn’t say “never could.” He said “don’t.” As in: not currently. As in: technically possible, just not switched on. As in: trust us, we’re choosing not to — for now.
When a company’s defense relies on the difference between “can” and “do,” you’re not being reassured. You’re being managed.
Here’s the background. Flock Safety sells license plate readers to law enforcement, HOAs, parking enforcement, and property managers across the United States. Their pitch has long been privacy-forward: we only capture plates, not people. But over the past year, the company repeatedly promoted video capability — in press releases, in product announcements, in marketing materials. Then 404 Media called them on it, and Langley’s response was a semantic escape hatch: the hardware can, but the software doesn’t.
That distinction isn’t a clarification. It’s a confession.
Think about what it actually means. Flock built cameras with video capability baked into the hardware. Then they shipped them to police departments and neighborhood watches without activating that feature — or at least, without admitting they activated it. Which means the capability is sitting there, dormant, waiting for a software update, a policy shift, or a quiet toggle that nobody announces.
The camera on your street corner isn’t just what it does today. It’s everything it could do tomorrow — and you’ll never be told when that tomorrow arrives.
This is the part that should make you angry, whether you’re a homeowner who bought one of these systems or a citizen who never consented to one being installed on your block. The product you’re being sold isn’t a static tool. It’s a modular surveillance system dressed up as a single-purpose device.
Langley’s wordplay reveals a deliberate product architecture: separate the hardware capability from the software activation. Build the surveillance infrastructure first. Turn on the features later. And when someone asks uncomfortable questions, hide behind the present tense.
“Can” versus “do” isn’t an accident. It’s a strategy. It lets Flock overpromise to investors and partners while underdelivering to the public — then reverse course whenever the political wind changes. Today it’s “we don’t do video.” Tomorrow it’s “we’ve added video to better serve our law enforcement partners.” Same hardware. Same camera on the same pole. Different story.
Every customer who installed a Flock camera thinking it only reads plates is now an unpaid beta tester for a surveillance platform they didn’t agree to.
If you work in law enforcement procurement, this should embarrass you. You signed contracts based on marketing claims that the CEO now contradicts. If you’re a privacy officer at a municipality that deployed these, you have a trust deficit that no press release will fix. And if you’re a resident living under one of these cameras, you now know the device watching your street has more capability than anyone admitted — and the company’s word is worth exactly as much as their latest verb tense.
The real lesson isn’t that Flock lied. Companies lie. The lesson is that in the age of software-defined hardware, the gap between what a device can do and what it does do is where all the danger lives. That gap is controlled entirely by the manufacturer — not by you, not by your city council, not by the police chief who signed the purchase order.
Demand technical transparency, not verbal loopholes. Ask for the firmware logs. Ask whether video capture can be enabled remotely. Ask what audit trail exists when features are toggled. Because the answer you get will tell you everything about whether you’re a customer or a test subject.
When a surveillance company’s honesty depends on which verb they choose, the verb isn’t the problem. The company is.
FAQ
Q: Isn't 'can' vs 'do' just a reasonable technical distinction?
A: It's a distinction that only benefits the company. When the hardware has the capability and the company controls activation via software, the customer has no way to verify what's actually running. The distinction lets Flock claim whatever is convenient at any given moment.
Q: What should Flock customers actually do about this?
A: Demand firmware-level audit logs, written confirmation of which features are enabled, and contractual guarantees that remote feature activation requires customer consent. If Flock won't provide that, treat every camera as a full video surveillance device for risk assessment purposes.
Q: Is this really a big deal if the video feature isn't turned on?
A: The entire problem is that you don't know whether it's on. A dormant capability controlled entirely by the manufacturer is functionally identical to an active one — the only difference is a software update you'll never be told about. The trust gap is the threat, not the feature itself.