AINEWS
Two 404 Media investigations and a Flock city council webinar show the second half: a productized playbook that coaches police through the public safety tech pitch.
Flock Safety pitched Uber and Lyft on turning roughly 350,000 rideshare drivers into a rolling network of license-plate readers, 404 Media reported from a leaked proposal. The pitch was the hardware half of a paired strategy whose other half is a leaked company guide that coaches police on how to "Own the Narrative" when selling the same technology to city councils.
Read the two together and the unit Flock actually sells is a package: the camera, the centralized plate-matching backend, and the script for getting local approval.
The rideshare proposal, detailed in 404 Media's investigation, described a Flock dashcam that scans plates on every trip and forwards matches to the company's existing LPR (license-plate recognition) network, the same fixed-camera infrastructure Flock already runs for police departments at city-owned poles and intersections. Mounted on a privately owned vehicle, the device would read plates every time a driver pulled out of a parking lot, idled at a curb, or passed another car. Decrypt, covering the investigation, described the target as a "nationwide plate-scanning fleet."
The narrative half is a separate Flock product. A second 404 Media investigation the same week published a leaked company guide that walks law-enforcement customers through "Owning the Narrative" when pitching the technology to city councils and the public. Flock's own website promotes a related public-facing session, "How to Speak to City Councils About Public Safety Tech," confirming the company treats the sales conversation itself as a product.
The two products are calibrated to each other. A 350,000-vehicle mobile LPR fleet is not the kind of deployment a city council approves on a single procurement vote. It requires sustained public buy-in over multiple council cycles, which is what the leaked guide supplies: a script for shaping local press, framing the program as crime prevention, and avoiding the surveillance vocabulary that triggers organized opposition. The dashboard a cop brings to a council meeting is the same one a rideshare dashcam feeds from the road.
The passenger-consent gap is the part neither 404 Media piece centers and neither wire re-report picks up. A rider who summons an Uber or Lyft has no relationship with Flock, no privacy notice, and no opt-in path. A rider can refuse a driver with a low star rating. They cannot refuse the plate reader bolted to the windshield, because the choice was made by a vendor, a fleet program, and a driver who may not know the device is there. Fixed LPR on a police cruiser or a city-owned pole is governed by the agency's accountability structure. A Flock unit in a privately owned vehicle operating under a rideshare gig is governed by none of it.
WIRED surfaced the cluster in its Aug 8, 2026 security roundup, placing the two investigations alongside Black Hat and DefCon disclosures, an OpenAI rogue-agent incident, and other surveillance items. Flock's pitch to city councils is now part of the product: the company is selling the second-order work of getting plate readers accepted by local government.
The architecture will be tested when Uber, Lyft, or any city council publishes the terms of a pilot: who owns the data, who can query it, and whether passengers ever see a notice.