Despite claims of strengthened privacy, San Francisco's decision to continue using **ALPR** technology from vendors like **Flock Safety**, **Motorola**, and **Axon** has ignited a fierce debate. Critics contend that the city's new policy fails to address fundamental issues surrounding data collection, potential misuse, and the inherent threat to civil liberties. ### The Human Cost of ALPR Errors Advocates highlight a troubling pattern of **ALPR** errors leading to innocent drivers being stopped and intimidated by law enforcement. Beyond technical inaccuracies, there are documented instances of officers abusing **ALPR** data to stalk individuals, including former romantic partners. Furthermore, the data has reportedly been accessed by **Immigration and Customs Enforcement (ICE)**, facilitating deportations. "These are not isolated mistakes that another policy can fix. They are consequences of building a system that records everyone’s movements and makes them searchable by police," states a recent press release from privacy advocates. ### Inadequate Safeguards: The Lack of Warrant Requirements A central point of contention is the absence of a warrant requirement for searching stored **ALPR** data. The city's reliance on incident or computer-aided dispatch (**CAD**) numbers is not considered a sufficient judicial authorization. Without probable cause reviewed by a judge, officers can freely search location data, increasing the risk of abuse. Privacy groups argue that even a warrant requirement wouldn't fully justify maintaining the **ALPR** network, emphasizing that the community's demand is for an end to the collection of this data altogether. ### Data Retention: Relocation is Not Deletion The new policies also lack a clear deadline for deleting **ALPR** data. Instead, there's a 30-day window to transfer data from vendor servers to city servers. Critics firmly assert that moving data is not equivalent to deleting it. Whether stored by **Flock Safety** or the **San Francisco Police Department (SFPD)**, this data creates a permanent record of individuals' movements, including where they live, work, worship, and seek care. Best practices, as demonstrated by states like New Hampshire (which mandates deletion in three minutes) and **Flock Safety** itself (with a default retention of seven days), lean towards swift deletion. ### Transparency vs. Accountability: The Limits of Audit Logs While transparency and documentation are acknowledged as important, improved audit logs are not seen as a panacea. Audit logs can only expose abuse *after* a search has occurred, unable to undo the disclosure of sensitive movement data or justify its initial collection. The city's policy also fails to require officers to articulate their reasons for searching **ALPR** data, a crucial accountability measure that has previously exposed abusive searches nationwide. San Francisco now finds itself behind many other communities that have weighed the trade-offs of **ALPR** surveillance and opted to terminate their contracts. Advocates urge the city to follow suit and prioritize the privacy and civil liberties of its residents.