Flock, ALPRs, and surveillance
Questions about Flock and Pflugerville’s decision
These answers summarize the records, contract review, and nine-month investigation behind Pflugerville’s decision to end its Flock Safety agreement. Each answer links to the fuller explanation and source record in the three-part series.
For the City’s current Flock decision, camera update, and the latest published policy status, see the current issue record.
Ten direct answers
The questions cities and residents are asking
The short answers are here. The linked articles explain how I reached them and identify the records supporting the fuller account.
Flock Safety sells connected public-safety technology. Pflugerville used 28 automated license plate readers, commonly called ALPRs, and also routed feeds from 38 existing City cameras into FlockOS through a gateway. Police could use the system to search for vehicles and review City camera footage. The system extended beyond the roadside ALPRs most residents associated with Flock.
Council voted unanimously on August 25, 2026, to decline the proposed renewal and end its Flock Safety agreement. Staff began covering the cameras that day. In a September 22 announcement, the City reported the contract canceled, the system deactivated, and all 28 City-contract cameras removed.
No. Before the final discovery, the working number was about 80 outside organizations. A public-information request later showed access for 459 agencies and almost 1.6 million searches against Pflugerville’s data. Only 80 of those agencies had ever been authorized. That gap showed that the City’s understanding of the network did not match the access reflected in the records.
Pflugerville police used the system to look for vehicles and in investigations. This site does not have verified numbers for arrests, recoveries, or cases solved, and a vendor’s totals are not the same as verified outcomes. The SAFE policy now requires that kind of reporting. Public-safety value was part of the review. It did not resolve the separate questions about who could search Pflugerville’s data, whether the contract allocated risk fairly, or whether the City could enforce the protections residents were promised.
A city should request the full contract history, every document incorporated by reference, device and camera inventories, gateway details, enabled analytics, data-sharing settings, outside-agency access, individual search logs, audit records, and communications between staff and the vendor. An order form alone does not show the full legal or technical system.
A city can publish its policies and equipment inventory, require a case number and plain-language reason for each search, audit its own officers, limit local retention, improve public reporting, and change which agencies it intentionally shares data with. Pflugerville made several of those changes before the renewal vote.
Local policy cannot raise the vendor’s liability, bind its subcontractors, control every outside user, require the vendor to pay breach costs, or give the city a contractual right to cancel. Those protections must be written into the agreement.
Read how to separate local controls from vendor and network risk.
The proposed agreement capped Flock’s liability at 12 months of fees, did not require Flock to cover the City’s breach-response costs, and did not give Pflugerville a practical exit if the law, technology, ownership, or public risk changed. It also incorporated online policies without locking the City to a dated version. Flock could revise some of those online terms while the City remained bound to the agreement.
Ownership of the raw input does not answer every data-control question. A contract must also govern Flock’s license to use the data, derived outputs and analyses, training data, deletion, backups, subcontractors, and access by other agencies. Public statements about customer ownership do not replace those enforceable terms.
No. Audit logs can show who searched, when they searched, and the reason they entered. They help a city detect patterns and investigate misuse after a search occurs. They do not prevent someone from choosing an inaccurate reason code or stop an outside user before the search happens. Cities still need access limits, meaningful search explanations, regular review, suspension rules, and enforceable consequences.
Council unanimously adopted the SAFE technology policy on October 27, 2026. Before the City buys, renews, or expands a high-risk system, staff must write a review and Council must approve it in a public vote.
See the current Flock and policy status, with official sources.