Tech
While the Country Rejects ALPR Mass Surveillance, SF Settles for Weak Safeguards
Publication: Deeplinks
Authors: Rindala Alajaji, Adam Schwartz, Sarah Hamid
Source published: 29/09/2026, 21:30:22 UTC
Briefing created: 30/09/2026, 00:21:58 UTC
Based on a feed excerpt; full article content has not been acquired. Source evidence retrieved 30/09/2026, 00:20:24 UTC.
Briefings
San Francisco's decision to retain Automated License Plate Reader (ALPR) surveillance cameras endangers residents and threatens privacy, as the city's policy fails to stop harms caused by erroneous matches and data misuse. The evidence indicates that innocent drivers face threats from officers using Flock to stalk romantic partners, while ICE accesses data for deportations. The city's new policy lacks a warrant requirement for searching stored ALPR data, allowing searches without probable cause. Unlike other jurisdictions requiring immediate deletion, San Francisco has no deadline to delete ALPR data, leaving it as a permanent record of public movements. The city's policy also lacks accountability rules requiring officers to state their search reasons in their own words, unlike those that exposed abusive searches nationwide. While the city claims it is behind other communities that ended ALPR contracts, the evidence suggests it should do the same.
Key points
- San Francisco retains ALPR surveillance despite evidence that innocent drivers face threats from officers using Flock to stalk romantic partners and that ICE accesses data for deportations.
- The city's policy lacks a warrant requirement for searching stored ALPR data, allowing searches without probable cause and without judicial authorization.
Context and limitations
Evidence is limited to the city's press release and announcement; it does not include independent audits, vendor reports, or community impact studies.
Generated by Bittrees-hosted qwen35-2b sha256:aaf42c8b7c3c on 30/09/2026, 00:21:58 UTC. Based on publisher-provided feed evidence; may not cover the full original article. Check the source for details.
View archived briefing on IPFS
bafybeigttoqhyp4dytbqxmbqd3gbhg3rdfpgqqg4mfu7cocjok5bbrlehq