Staff Reports
The short version: a hacker-researcher mapped what looks like a huge network of Flock Safety devices, then a brand‑protection firm quietly asked a host to take the map down. The fight is small‑c and big‑P — private power, public surveillance — and it raises a simple question: who gets to know who is watching us?
Map exposes massive Flock footprint
What the map shows
Cybersecurity researcher Joshua Michael published an interactive “Flock Surveillance Map” built from an exposed mapping token. The export he used lists roughly 335,700 device records nationwide, with more than 170,000 labeled as cameras and another 130,000 listed as supporting gear or planned units. That’s a lot more than the handful of public figures Flock Safety has been handing out. To be fair, the researcher’s snapshot includes planned and decommissioned entries, so you shouldn’t take the number as a neat count of active cameras. Still, it’s enough to suggest the network is far larger and more complex than many citizens know — and that should make people sit up whether they’re for law and order or worried about Big Brother.
Trademark takedown: brand protection or censorship?
How the takedown worked
One day after the map went public, a brand‑protection firm called Doppel submitted a trademark complaint to a registrar on behalf of Flock Safety asking that the site be removed. That’s the modern playbook: instead of suing in open court, companies push a registrar or host to yank content fast. It’s legal theater with practical teeth — hosts often comply quickly, and the content disappears before anyone argues the First Amendment or fair use. The ACLU’s Senior Policy Counsel called the move “ridiculous,” noting it’s odd for a company that sells surveillance to rush to hide its own footprint. Meanwhile a pro‑ALPR sheriff complained the mapmakers should be punished. The optics are bad either way: a surveillance firm tries to scrub a map of where its cameras are, and it looks like privacy for the company matters more than transparency for the public.
Congressional hearing and public scrutiny
The map and its takedown landed during congressional scrutiny of automated license‑plate readers. The Senate Judiciary Subcommittee put Flock’s practices on the table, and privacy advocates testified that the network poses real risks. Flock’s founder and CEO has defended the company’s record and product fixes, but the CEO did not show at the hearing. Instead, Flock seemed to respond with a job listing for a Public Policy Manager — hire a spokesperson and hope the controversy goes away. That’s not leadership; it’s damage control.
Why this matters
Conservatives who care about public safety and limited government should not reflexively cheer every camera on a pole. Tools that help fish out criminals also create enduring databases and power for private companies. If Flock or any vendor wants to sell mass surveillance to police, voters and taxpayers deserve clear, honest accounting — not bland press releases and registrar complaints. Congress and local officials should demand transparent device counts, clear retention rules, and independent audits. And if a company is going to use legal muscle to hide the scale of its surveillance, citizens should ask why they are so afraid of a map. After all, sunlight is still the best disinfectant — even if some firms would rather keep the bulbs off.
