Benn Jordan thinks the surveillance problem is much bigger than Flock

What the episode covered

Ben Jordan said ALPR networks are an opt-outless, insecure surveillance problem that local governments enabled. The register is mixed, with concrete security anecdotes and several transcript breaks where answers are missing. Watch whether Flock and local governments publish warrant rules, audit logs, and security fixes.

Our summary, written from the transcript. Not the speakers' words.

The episode, in order

1. 01Why the Flock backlash matters

   The episode treats Flock as the visible example of a broader fight over surveillance, local government purchasing, and police access.

2. 02Why people reacted differently to ALPRs

   His core distinction is that this surveillance is public-space infrastructure rather than a consumer device people choose to buy.

3. 03Security weaknesses

   This makes the debate not only about privacy policy, but also about whether the systems were safe enough for police and government use.

4. 04Who should be accountable

   The episode shifts the target from one company to the public institutions that approved, bought, and operated the tools.

5. 05Possible compromises

   The practical path he describes is not only removing cameras, but making deployment narrower, auditable, and locally authorized.

Sponsors named in this episode

No sponsor named doesn't mean no ads. Each row was taken from the ad break as it was read on air. The verbatim passage behind every row is checked against the transcript character for character. Short excerpts appear below.

Roles and stated affiliations

Stated affiliation. Ben Jordan: He is presented as a musician, YouTuber, researcher, investigative journalist, and Senate witness whose recent public work focuses on Flock and ALPR systems.

Wakewire's read of interests

• Nilay Patel: He is the host and Editor-in-Chief of The Verge, and he frames the interview around surveillance, privacy, tech company accountability, and local government decisions.
• CrowdStrike: The recording states that CrowdStrike supports the show and advertises AI detection and response for enterprise cybersecurity.
• Doppel: The recording states that Doppel advertises an AI-native social-engineering defense platform.
• Outshift by Cisco: The recording states that Outshift advertises a resource for multi-agent AI systems.

Recording limits

• The transcript has mid-sentence commercial insertions and broken joins, including the spans beginning “Support for the crimes” and “Support for this could be Lorem,” so parts of several answers appear to be missing.

Claims that need more support

• Ben Jordan said he found Flock credentials on the dark web from a Russian vendor, but the recording did not provide dates, affected agencies, or independent evidence.

Claims made on air that the episode itself did not back up.

Questions the conversation didn't reach

• The recording did not answer what security changes Flock, Axon, or Motorola have implemented since the vulnerabilities Jordan described.

Topics the episode did not address. This does not mean anyone avoided them.

Are you from this show? You can ask for a correction, reply, or ask us to stop coverage on the rights page.

What was said

• Why the Flock backlash matters

  Patel framed Jordan as a public face of the Flock backlash and said the controversy includes Senate attention, contract cancellations, an investigation by Senator Josh Hawley, and reported layoffs at Flock.

• Why people reacted differently to ALPRs

  Jordan said people are upset because they cannot opt out of roadside ALPR cameras, were not asked to vote on them, and pay for them through taxes.

• Security weaknesses

  Jordan described absent multi-factor authentication at the time, police logins from non-police-station Wi-Fi, credentials found on the dark web, exposed administrative interfaces, and hardware vulnerabilities.

• Who should be accountable

  Jordan said Flock is a for-profit startup and placed more responsibility on legislators, police departments, city councils, and government purchasers.

• Possible compromises

  Jordan floated limits such as trained access gatekeepers, warrant requirements, opt-outs through the DMV, 24-hour retention, immutable audit logs, and local referendums or council accountability.

Our paraphrase, not the speakers' words.

The passages we relied on

Short excerpts, credited to the show, at most 40 words each and 150 per episode. We do not publish transcripts. We link to the episode so you can hear it from the show itself.

What to watch for

• Flock publishes or confirms mandatory multi-factor authentication, tighter account controls, and a process for reporting and remediating camera vulnerabilities. (near term)
• Local ALPR contracts or council approvals include retention limits, warrant or case-number rules, public audit logs, and a security assessment before deployment. (next local procurement cycles)
• A Senate or congressional document identifies specific ALPR security standards or legal limits for police searches. (after the hearings and investigation process)
• Flock, Axon, or Motorola publish ALPR network policies that state who can search data, how long data is retained, and how misuse is audited. (ongoing)