Key Takeaways
- The San Diego Police Department renewed its contract with Flock Safety for automatic license‑plate reader (ALPR) technology without fully informing the City Council’s Privacy Advisory Board.
- Flock’s cameras capture vehicle “fingerprints” (make, model, characteristics, license plates) and feed data into both the police department and the Automated Regional Justice Information System (ARJIS), which has historically been accessible to federal agencies such as Customs and Border Protection.
- A broad coalition of local and student groups, including the Students’ Civil Liberties Union (SCLU), condemned the deployment, arguing it constitutes mass surveillance and diverts funds from community services.
- At a public City Council hearing, all 27 speakers opposed continued ALPR use; SCLU organizers highlighted that the city has exchanged ALPR logs for over $300,000 in Department of Homeland Security grants since 2011.
- Councilmember Magdalena Donea succeeded in separating 53 other undisclosed surveillance technologies from the ALPR provision in the contract, but the council ultimately voted to reject ALPR usage until “specified codified recommendations” are completed.
- The Privacy Advisory Board is now reviewing the ongoing ALPR policies; Vice Chair Ted Womack Jr. cited a mere 0.177 % success rate in ALPR‑assisted cases, questioning the public benefit relative to cost.
- SCLU warns that ALPR data can be retained and accessed for up to eight years, and they have made a public camera map available at deflock.org (though the UCSD portion remains incomplete).
Background on the Flock Safety Contract Renewal
In December 2023 the San Diego Police Department (SDPD) renewed its agreement with Flock Safety, a vendor that supplies automatic license‑plate reader (ALPR) systems. The renewal was processed without a full briefing to the City Council’s Privacy Advisory Board, the body tasked with overseeing surveillance technology purchases. This omission triggered concerns about procedural transparency and the board’s ability to assess privacy implications before the contract took effect.
How Flock’s ALPR Technology Works
Flock Safety’s cameras are equipped with “vehicle fingerprint” ALPR technology. Each unit records a passing vehicle’s license plate, make, model, color, and other distinguishing features. The data are then matched against law‑enforcement databases to associate plates with registered owners. While Flock insists it is not a mass‑surveillance company, the capability to continuously log and store vehicle movements across public spaces raises significant privacy questions for civil‑rights advocates.
Data Sharing Practices and Federal Links
Beyond the immediate police use, SDPD stores Flock‑generated data in the Automated Regional Justice Information System (ARJIS). ARJIS has a historical record of being accessible to federal agencies, including Customs and Border Protection (CBP). Critics argue that this creates a conduit for local surveillance information to flow into national immigration enforcement networks, undermining community trust and potentially violating existing trust ordinances that limit data sharing with federal authorities.
Grassroots Opposition Mobilizes
Numerous local organizations, neighborhood associations, and student groups have issued statements condemning the ALPR program. Their opposition centers on claims that the technology infringes on privacy, disproportionately impacts marginalized communities, and diverts funding from essential services such as libraries, parks, and youth programs. The coordinated push reflects growing unease about the expansion of surveillance infrastructure in urban settings.
City Council Public Comment Session
On the Thursday evening following the contract renewal, the San Diego City Council convened a public hearing to gather community input on ALPR use. Twenty‑seven individuals signed up to speak, and every speaker voiced opposition to the continued deployment of Flock cameras, the associated funding, and any further implementation of ALPR technologies. The unanimous stance underscored the depth of community concern and set the stage for a contentious deliberation.
Student‑Led Advocacy and the “Fund Communities, Not Cameras” Campaign
Two days before the hearing, the Students’ Civil Liberties Union (SCLU) released an Instagram flyer urging students to attend the council meeting and voice their dissent. The post, titled “Fund Communities, Not Cameras,” framed the issue as a choice between investing in public safety through surveillance versus reinvesting in social services. Twelve SCLU organizers participated in the meeting, bringing a youthful, organized presence to the debate.
Voices from the SCLU: Daniel Soria’s Testimony
Daniel Soria, a recent UC San Diego graduate and co‑founder of SCLU, addressed the council, highlighting the apparent misalignment of budget priorities. He noted that the city had closed libraries and parks to address a $120 million deficit while preserving surveillance contracts. Soria argued that the existing data‑sharing arrangement with border patrol violated the established trust order and urged the council to enforce real consequences for any misuse of ALPR data under the trust ordinance.
Prior SCLU Mobilization: The March Rally
The SCLU’s activism is not new; the organization had previously organized a rally in March demanding transparency and accountability from local authorities regarding surveillance technologies. That event laid the groundwork for the later council hearing, reinforcing consistent calls for oversight, community impact assessments, and stricter limits on data retention and sharing.
Councilmember Magdalena Donea’s Procedural Move
During the hearing, Councilmember Magdalena Donea introduced a motion to separate 53 other undisclosed surveillance technologies embedded in the Flock contract from the specific ALPR provision. Her amendment aimed to isolate the ALPR debate, allowing the council to address the license‑plate technology on its own merits while retaining the ability to review other surveillance tools separately. The motion passed, clarifying the scope of the subsequent discussion.
Council Deliberation and President Joe LaCava’s Perspective
The council then devoted approximately two hours to discussing ALPRs. Council President Joe LaCava framed the conversation as a effort to ensure the police department could operate effectively while addressing public concerns. He emphasized the need to balance operational support for law enforcement with safeguards for civil liberties, reflecting the broader tension between public safety imperatives and privacy protections.
Vote to Suspend ALPR Use Pending Recommendations
After extensive debate, the City Council voted to reject the continued use of ALPR technology until “specified codified recommendations” are finalized. The vote represents a conditional moratorium: ALPR deployment will halt while the council works with experts, the Privacy Advisory Board, and community stakeholders to develop clear guidelines on data use, retention limits, sharing protocols, and oversight mechanisms. The board is still deliberating the exact nature of those recommendations.
Ongoing Review by the Privacy Advisory Board
The moratorium triggers an active review by the Privacy Advisory Board, which will evaluate the current ALPR policies, assess compliance with existing privacy ordinances, and propose any necessary reforms. Councilmember and Privacy Advisory Board Vice Chair Ted Womack Jr. voiced his skepticism during an interview with The UCSD Guardian, stating that police‑provided data indicated a mere 0.177 % success rate in cases where ALPRs contributed meaningfully to investigations. He argued that such a low efficacy does not justify the financial and privacy costs incurred by the public.
SCLU’s Findings on Data Sharing and Federal Grants
Following the meeting, SCLU organizers Angelica Yeleshwarapu and Daniel Negrete elaborated on their research to The Guardian. They disclosed that the city has exchanged ALPR logs and search histories for over $300,000 in Department of Homeland Security (DHS) grants since 2011. According to the organizers, this pattern is not isolated; data are aggregated across multiple agencies and retained for up to eight years, enabling law‑enforcement officials to retrieve historical vehicle movements at will. They warned that this extensive data reservoir amplifies the potential for misuse and erodes trust between the police and the communities they serve.
Public Access to Camera Locations
Negrete also pointed out that a public map of Flock camera locations in San Diego is available at deflock.org. The map aims to increase transparency by showing where surveillance devices are deployed. However, he noted that the portion covering the University of California, San Diego (UCSD) campus remains incomplete, limiting the usefulness of the resource for students and staff seeking to understand the extent of monitoring on campus.
Implications and Next Steps
The San Diego City Council’s decision to pause ALPR use reflects a responsive, albeit cautious, approach to mounting public pressure. The forthcoming codified recommendations will likely address key concerns: limiting data retention, prohibiting indiscriminate sharing with federal agencies, establishing independent audits, and ensuring community oversight through the Privacy Advisory Board. Until those measures are adopted, the moratorium stands as a temporary safeguard, signaling that the city values civil liberties enough to suspend a contentious surveillance tool while it seeks a more balanced, accountable framework.
The ongoing dialogue—spanning grassroots activism, student advocacy, council deliberations, and advisory‑board scrutiny—illustrates a broader national conversation about the role of automated surveillance technologies in modern policing. How San Diego navigates this terrain may serve as a bellwether for other municipalities weighing the trade‑offs between technological crime‑solving capabilities and the preservation of privacy and public trust.