[REVISION HISTORY]
US license plate reader privacy and surveillance scrutiny
Updated 45 times since CLSTR started tracking revisions of this situation.
What changed
2026-10-07 23:30 UTC → 2026-10-09 04:51 UTC ·
added
removed
The conflict surrounding Flock Safety has intensified, involving both corporate scrutiny and personal targeting. CEO Garrett Langley has faced online campaigns, including the circulation of an unverified home address and digital pranks, following his suggestion that Americans should accept a “compromise” between privacy and public safety. Additionally, a resident in Ridge Spring, South Carolina, alleged he was threatened with arrest via a police department Facebook account after posting profane criticism of local Flock cameras. Questions regarding the efficacy of the technology have also emerged. While Langley previously claimed the company helped solve over one million crimes in 2025, a spokesperson clarified that this figure refers to investigations and incidents supported by the technology, such as investigative leads, rather than strictly solved crimes. Privacy debates continue to drive policy shifts. In Minnesota, local officials have paused or canceled contracts, with St. Paul City Council President Rebecca Noecker calling for an end to the city and county’s contract due to concerns over data sharing. In response to mounting privacy pressures, Flock Safety recently announced it would reduce its default data retention period from 30 days to seven days. Resistance is expanding in Wisconsin, where approximately 25 communities are disconnecting or covering automated license plate readers. This resistance has moved to federal court via a lawsuit filed by ‘No Cams Muskego’ against Waukesha County municipalities. The Wisconsin Institute for Law & Liberty argues the technology constitutes “intrusive surveillance” and requires a search warrant for data access. In Milwaukee, Mayor Cavalier Johnson introduced a policy limiting camera access to supervisors and restricting use to serious crimes following allegations crimes. Recent developments include the University of an officer using North Carolina Police Department deciding to disable the system automatic data-sharing feature of its Flock system. Chief Brian James cited concerns regarding potential misuse and rhetoric surrounding the technology, noting that other agencies must now contact the university directly to track a dating partner. request information.
Versions
- 2026-10-09 04:51 UTC US license plate reader privacy and surveillance scrutiny
- 2026-10-07 23:30 UTC US license plate reader privacy and surveillance scrutiny
- 2026-10-07 02:04 UTC US license plate reader privacy and surveillance scrutiny
- 2026-10-03 19:54 UTC US license plate reader privacy and surveillance scrutiny
- 2026-09-30 21:53 UTC US license plate reader privacy and surveillance scrutiny
- 2026-09-28 16:52 UTC US license plate reader privacy and surveillance scrutiny
- 2026-09-26 12:41 UTC US license plate reader privacy and surveillance scrutiny
- 2026-09-25 17:02 UTC US license plate reader privacy and surveillance scrutiny
- 2026-09-25 12:15 UTC US license plate reader privacy and surveillance scrutiny
- 2026-09-24 04:49 UTC US license plate reader privacy and surveillance scrutiny
- 2026-09-20 00:03 UTC US license plate reader privacy and surveillance scrutiny
- 2026-09-18 19:47 UTC US license plate reader privacy and surveillance scrutiny
- 2026-09-18 01:28 UTC US license plate reader privacy and surveillance scrutiny
- 2026-09-18 00:48 UTC US license plate reader privacy and surveillance scrutiny
- 2026-09-17 21:37 UTC US license plate reader privacy and surveillance scrutiny
- 2026-09-17 13:41 UTC US license plate reader privacy and surveillance scrutiny
- 2026-09-16 21:53 UTC US license plate reader privacy and surveillance scrutiny
- 2026-09-16 18:07 UTC US license plate reader privacy and surveillance scrutiny
- 2026-09-16 18:07 UTC US license plate reader privacy and surveillance scrutiny
- 2026-09-16 15:34 UTC US license plate reader privacy and surveillance scrutiny
- 2026-09-16 04:13 UTC US license plate reader privacy and surveillance scrutiny
- 2026-09-15 14:39 UTC US license plate reader privacy and surveillance scrutiny
- 2026-09-15 12:56 UTC US license plate reader privacy and surveillance scrutiny
- 2026-09-13 18:04 UTC US license plate reader privacy and surveillance scrutiny
- 2026-09-07 08:54 UTC US license plate reader privacy and surveillance scrutiny
- 2026-09-06 19:12 UTC US license plate reader privacy and surveillance scrutiny
- 2026-09-06 01:43 UTC US license plate reader privacy and surveillance scrutiny
- 2026-09-05 10:39 UTC US license plate reader privacy and surveillance scrutiny
- 2026-08-29 01:51 UTC US license plate reader privacy and surveillance scrutiny
- 2026-08-29 00:27 UTC US license plate reader privacy and surveillance scrutiny
- 2026-08-28 19:07 UTC US license plate reader privacy and surveillance scrutiny
- 2026-08-28 10:13 UTC US license plate reader privacy and surveillance scrutiny
- 2026-08-27 20:58 UTC US license plate reader privacy and surveillance scrutiny
- 2026-08-27 01:21 UTC US license plate reader privacy and surveillance scrutiny
- 2026-08-24 19:06 UTC US license plate reader privacy concerns
- 2026-08-24 02:10 UTC US license plate reader privacy concerns
- 2026-08-20 22:33 UTC US license plate reader privacy concerns
- 2026-08-20 19:35 UTC US license plate reader privacy concerns
- 2026-08-20 19:35 UTC US license plate reader privacy concerns
- 2026-08-20 13:40 UTC US license plate reader privacy concerns
- 2026-08-20 00:31 UTC US license plate reader privacy concerns
- 2026-08-19 23:58 UTC US license plate reader privacy concerns
- 2026-08-19 15:28 UTC US license plate reader privacy concerns
- 2026-08-19 00:43 UTC US license plate reader privacy concerns
- 2026-08-18 18:49 UTC US license plate reader privacy concerns
- 2026-08-11 22:10 UTC US license plate reader privacy concerns
Only revisions since CLSTR began indexing content versions appear here. Select a version to see what changed compared to the one before it.