Ban Routine Police Use of Networked ALPRs
A direct local-and-state campaign to terminate networked ALPR contracts, remove cameras, and ban warrantless law-enforcement use and sharing.
End routine police use of networked automated license-plate readers.
- Local governments: terminate contracts, disable access, require verified deletion, and remove cameras.
- States: ban warrantless law-enforcement ALPR use and cross-jurisdictional sharing.
This is a technology-neutral position about police use of networked ALPR systems, not a vendor-only boycott. Flock Safety is named where the evidence concerns its platform. Documented cases are not prevalence estimates; charges and complaints remain allegations unless adjudicated. Flockwatch does not publish live vehicle movements or unnecessary personal information.
Why this line
Routine networked ALPR use combines four powers that should not be normalized: continuous capture of vehicle location, retention searchable after the fact, access beyond the camera-owning jurisdiction, and an alert-to-stop pathway that can turn uncertain data into coercive force.
- California's attorney general sued El Cajon over alleged sharing with federal and out-of-state agencies prohibited by state law. The filing is an allegation, not a final judgment.
- University of Washington researchers documented federal immigration access through direct, indirect, and agency-on-behalf-of routes in Washington public records.
- Flock Safety itself said it paused federal pilot programs and changed federal-user access controls. A safeguard added after access existed does not make the underlying network safe by default.
- An Albany Police Department audit led Georgia investigators to charge five former officers with alleged non-law-enforcement use of retained Flock data. The GBI release says the investigation remains active; the charges are allegations unless adjudicated.
The incident registry supplies case-level evidence. It does not establish a national incident rate. The findings document system scale with explicit denominators. Together they support a precautionary policy judgment: police should not maintain a routine, suspicionless location-search network and wait for controls to fail.
Government target ladder
Stop the system now
Place termination, deactivation, verified deletion, and physical removal on the public agenda. Freeze renewals and expansions while the vote is pending.
Close the contract exits
Publish contracts, amendments, data-sharing settings, audit logs, deletion attestations, and termination costs. Bar replacement with another networked vendor.
Ban warrantless use and sharing
Cover government-owned, vendor-hosted, and privately collected ALPR data. Prohibit purchase, agency-on-behalf-of searches, and interstate or federal workarounds.
Make the ban real
Require suppression, deletion, notice, damages, attorney fees, discipline, public audits, and a private right of action where legally available.
Cambridge terminated its Flock contract. Evanston deactivated 19 cameras and issued a termination notice. These are concrete precedents for the first rung; they do not by themselves prevent another agency from querying another jurisdiction's network.
Policy floor
The default rule should be a ban on routine police use. Any narrow emergency exception must include all of the following:
- Individualized judicial authorization. A warrant or equivalent order must identify the vehicle, suspected serious offense, search window, and factual basis. No categorical, dragnet, or post-hoc authorization.
- Strict purpose limits. No immigration, reproductive-health, First Amendment, association, debt, civil, or generalized intelligence use. No repurposing after collection.
- Rapid deletion. Non-responsive data should be deleted in minutes, not retained for weeks or months. Responsive material expires with the order unless a court extends it.
- No network workaround. The rule follows the query, whether data is owned, purchased, donated, vendor-hosted, or requested through another agency. Cross-jurisdictional sharing is prohibited absent the same order.
- Verification before force. An ALPR alert alone cannot justify a stop, detention, search, or use of force. Officers must independently verify the complete plate, state, vehicle, and hot-list status.
- Auditability and notice. Tamper-evident query logs, published aggregate audits, prompt misuse investigations, and notice to affected people when it no longer jeopardizes an authorized investigation.
- An enforceable remedy. Suppression, deletion, damages, attorney fees, discipline, and a private right of action where constitutionally available. A policy with no remedy is a request, not a limit.
The Virginia Court of Appeals' October 2025 unpublished opinion in Commonwealth v. Church (Rec. No. 0737-25-1) reversed the Norfolk circuit court's warrant ruling. Because the opinion is unpublished and not current statewide precedent, it is evidence that warrant protection cannot be assumed from unsettled doctrine; legislatures must supply a clear floor.
Resident actions
- Map authority, not vehicles. Identify the contract owner, renewal date, funding source, camera count, data host, governing body, and meeting calendar. Do not publish live camera queries or vehicle movements.
- Request records. Ask for the contract and amendments, policies, data-sharing configuration, agency list, query/audit logs with personal data minimized, deletion records, training, complaints, and effectiveness reports.
- Demand a recorded vote. Ask for a public agenda item containing four verbs: terminate, deactivate, delete, remove. Oppose a quiet vendor swap that preserves networked police access.
- Press the state rule. Ask legislators to cover vendor, government, and privately sourced ALPR data; ban indirect searches; require judicial authorization for any narrow exception; and attach remedies.
- Track implementation. Confirm account shutdown, sharing revocation, vendor deletion attestation, hardware removal, final invoices, and audit-log preservation for oversight.
Start with the incident-audit guide → · Review local termination examples → · Download the source registry →
Objections and responses
“ALPRs solve crimes.”
They can generate leads and locate listed vehicles. That is not the whole policy question. Routine operation also records overwhelmingly non-hit travel, retains search power, and distributes access. The burden is to show that a continuous network is necessary—not merely useful—and that narrower, judicially authorized tools cannot do the job.
“The cameras only observe public roads.”
A single observation in public is not the same as an organization-wide, retrospective location index. Network aggregation changes what can be inferred about work, worship, medical care, association, and movement over time.
“Short retention solves the privacy problem.”
Short retention reduces exposure but does not cure suspicionless collection, immediate alerts, network sharing, or misuse during the retention window. The correct default is no routine police network; rapid deletion is a minimum for any judicially authorized exception.
“Sharing is optional and locally controlled.”
Public records and official responses show that direct access is only one route. Agency-on-behalf-of searches, configuration errors, purchased data, and federal pilots can cross local policy lines. A binding rule must follow the query and prohibit indirect workarounds.
“Audit logs catch abuse.”
Logs matter, but they usually expose misuse after a search has occurred. The Albany charges followed an internal audit; they do not undo the alleged access. Authorization, minimization, auditing, notice, and remedies must work together.
“Warrants are too slow for real investigations.”
Courts routinely handle time-sensitive applications, and law can define a genuinely narrow emergency process with prompt judicial review. Administrative convenience is not a reason to keep a population-scale location database available for routine searches.
Source discipline
The campaign judgment is explicit; the evidence remains bounded. Claims above link to government, court, university public-records, municipal, and vendor sources retrieved and hashed in the repository's August 2026 provenance bundle. See the methods, limitations, and full incident status notes before reusing a claim.