Benn Jordan on Flock, privacy, and the new surveillance backlash

Introduction

Benn Jordan—musician, YouTuber, and self‑described hacker—has become a prominent voice in the fight against automated license‑plate readers (ALPRs) made by Flock Safety. His deep‑dive videos, testimony before a Senate subcommittee, and on‑the‑ground work with city councils have turned a niche technical concern into a broader public debate about privacy, government transparency, and the intertwining interests of private surveillance firms.

From Music to Monitoring

Jordan’s career began in experimental music, but his curiosity about how technology works soon led him to reverse‑engineer products and expose hidden functionalities. Living in Atlanta, a city saturated with Flock cameras, he noticed the devices and initially mistook them for ordinary traffic cameras. A closer look revealed a network that continuously scans and records license plates, feeding data to law‑enforcement agencies without any opt‑out mechanism for residents. This discovery sparked a personal project: documenting security flaws, publishing findings on YouTube, and reaching out directly to Flock’s leadership with vulnerability reports.

The Power of Local Democracy

Jordan argues that the backlash against Flock is less about a single company and more about the way local governments have quietly adopted surveillance infrastructure. When residents learn that their municipal budgets are funding continuous vehicle tracking, they begin to attend town‑board meetings, question elected officials, and demand transparency. The recent wave of contract cancellations across dozens of cities illustrates how grassroots pressure can translate into concrete policy change. Jordan sees this as a rare example of citizens reclaiming agency in a domain usually dominated by opaque contracts between police departments and private vendors.

A Pragmatic Approach to Accountability

Rather than framing his work as a crusade against Flock, Jordan positions himself as a facilitator of accountability. He maintains an “olive‑branch” dialogue with the company, reporting bugs and encouraging responsible disclosure while also collaborating with civil‑rights groups and journalists to amplify the issue. This strategy aims to produce tangible fixes—such as patched firmware or clearer data‑retention policies—rather than merely demonizing a single vendor. Jordan’s testimony before the Senate Judiciary Committee’s Subcommittee on Crime and Counterterrorism highlighted the systemic nature of the problem, emphasizing that similar ALPR systems from competitors like Axon and Motorola operate under comparable secrecy.

Why the Surge Now?

The current surge in privacy concerns mirrors earlier reactions to mass‑surveillance revelations, but it is amplified by the ubiquity of low‑cost, city‑wide camera networks. Unlike the NSA’s national‑scale programs, ALPRs sit in neighborhoods, parking lots, and school zones, making the surveillance feel immediate and personal. Jordan points out two key frustrations for citizens:

1. No Opt‑Out – Residents cannot refuse the installation of cameras that capture their movements on public roads.
2. Tax‑Funded Monitoring – Surveillance costs are bundled into property taxes, meaning citizens fund the system without explicit consent.

These factors combine to create a sense of “surveillance fatigue” that is now being channeled into civic action.

Looking Ahead

Jordan believes the fight against pervasive surveillance will continue to evolve. He encourages creators and technologists to adopt a “responsible disclosure” mindset, to document findings publicly, and to partner with local advocacy groups. By keeping the conversation grounded in concrete policy outcomes—such as stricter data‑retention limits, independent audits, and public oversight boards—activists can move beyond protest to sustainable reform.

--- Practical Takeaway: If you suspect your community is deploying ALPRs or similar surveillance tools, start by requesting public records on contracts and data policies, attend city council meetings, and share any technical findings with both the vendor and local media. Collective, informed pressure can turn hidden infrastructure into a public‑interest discussion and, ultimately, into accountable governance.