More Than 150 U.S. Cities Restrict or Reject Flock Safety Cameras

Flock Safety’s AI-enabled license-plate reader network is used by police departments and private clients, placing the technology within a growing public-sector debate over surveillance, data access, and privacy. According to the reported signal, more than 150 U.S. cities have banned, rejected, or deactivated the cameras. The reported actions span different adoption decisions; they do not establish that every city took the same step or acted for an identical reason. The underlying concerns include reported misuse, data-sharing practices, and privacy challenges, issues that can shape both initial purchases and decisions about retaining systems already in operation.

The signal identifies no specific solicitation, award, or contract action. Its procurement relevance instead lies in how agencies may evaluate surveillance technology and govern its use after deployment. Buyers considering license-plate readers or similar systems can make intended uses, authorized users, data access, retention, sharing, and oversight part of procurement planning. A proposed system’s technical capabilities are only one consideration: agencies also need to assess whether policies and controls can limit use to approved purposes and support meaningful review of system activity.

Local police departments are among the government users identified in the source, and U.S. Immigration and Customs Enforcement (ICE) is also listed among the agencies. The available information does not specify which city actions involved which agency, nor does it describe a particular ICE procurement or deployment. For contractors pursuing public-sector surveillance work, the broader signal is that proposals may face questions about responsible use and controlled data sharing. Vendors should be prepared to explain how their products support access controls, auditability, and agency oversight, while recognizing that each jurisdiction’s legal and policy requirements may differ.

For procurement teams, the reported city actions are a reason to consider governance alongside operational requirements—not evidence that every camera network will be rejected or that a single policy response applies nationwide. Solicitation documents and evaluation plans can address transparent use policies, role-based access, logging and audit capabilities, data-sharing boundaries, and legal review before deployment. Agencies weighing adoption or retention can also compare the operational value of a system against privacy concerns and the resources required to supervise it. These considerations may affect vendor qualification, proposal evaluation, implementation planning, and contract oversight for surveillance systems, even where no active procurement is identified.

• More than 150 U.S. cities have reportedly banned, rejected, or deactivated Flock Safety cameras; the source does not break down the actions by city or rationale.
• Flock Safety provides an AI-enabled license-plate reader network used by police departments and private clients.
• Reported concerns include misuse, data sharing, and privacy challenges.
• The signal identifies no specific solicitation, contract, or award; procurement implications are indirect and center on heightened scrutiny.
• Agencies evaluating surveillance systems can define permitted uses, authorized users, and data-access rules before purchase and deployment.
• Procurement and oversight plans can address auditability, transparent policies, data-sharing limits, and legal review.
• Contractors should be ready to explain how their systems support accountable use, controlled access, and agency oversight.
• Adoption and retention decisions for similar camera networks may weigh operational needs against privacy concerns and governance requirements.
• Local police departments and U.S. Immigration and Customs Enforcement are identified in the source; no specific deployment or contract is attributed to either.