The Surveillance That Stalks

Here's how it's supposed to work, and how it actually does. Flock cameras photograph every vehicle that passes, logging the plate, the time, the location, and stitching it into a nationwide map of where cars — and the people in them — have been. Police query that map to track suspects. The pitch is public safety. The architecture is a search engine for human movement, and a search engine doesn't care who's typing.

Take Officer Jarmarus Brown, Orange City, Florida, summer 2024. He ran his ex-girlfriend's plate through Flock more than 69 times. Her mother's, 24 times. Her father's, 15. He wasn't investigating a crime. He was finding a person who didn't want to be found, over and over, with infrastructure the public paid for. And here's the part that should end the marketing: he got caught because a colleague physically watched him do it from the passenger seat and told him to knock it off before he got in trouble. Not because the system flagged 69 searches of the same private citizen. Not because an audit triggered. Because another human happened to be sitting there.

That's the pattern, and it's not specific to Flock. Every surveillance system is one disgruntled login away from being a stalking tool. The capability is the vulnerability. "Built to track cars" and "built to track people" are the same sentence — the only difference is the query you type, and there is nothing in the box that knows the difference. The oversight that caught Brown wasn't a control. It was a coworker's conscience. Conscience does not scale, and it doesn't read logs at 2 a.m.

This is what it looks like when technology amplifies what's already there. A network that can locate any car anywhere doesn't turn benign because the slide deck says "law enforcement." It amplifies whatever the person at the terminal wants — a fugitive, or an ex who blocked your number. The system can find the vehicle. It cannot feel why running a frightened woman's plate 69 times is the whole problem. The harm isn't a bug sitting somewhere in Flock's codebase waiting to be patched. The harm is Flock, working perfectly, pointed at someone.

The audit trails exist, by the way. Every one of those searches was logged. The data to catch Brown on his second illegitimate query was sitting right there. Nobody was reading it, because reading it isn't anyone's job, because the system was sold on the promise that the people using it are the good guys. That promise is the product.

More than a dozen — and those are the ones who got caught, mostly by colleagues rather than by code. The unaudited searches don't show up in the count, because by definition nobody counted them. The next one won't either, until another coworker happens to be sitting in the passenger seat — and the camera that could have flagged it will keep right on logging, faithfully, for no one. Somewhere, a plate is already running.