In June 2026, Joel Feder backed a borrowed Range Rover out of a parking space outside a Kohl’s in Plymouth, Minnesota. Four police cars closed around him.
Officers approached with their hands on their guns. They ordered Feder and his wife out, patted them down, and held them at the scene while they sorted out the plate. Police said the New Jersey plate on the press vehicle was stolen. They had been following the car for two days through Flock Safety’s automated license-plate-reader network. Feder later obtained body-camera footage and reconstructed the encounter with Plymouth’s police chief and Flock.
The plate was not stolen. Neither was the vehicle.
A similar manufacturer plate had been lost in California. Its number was entered incompletely into the FBI’s National Crime Information Center as “34 DTM.” Feder’s plate read “34 10 DTM,” with the middle digits printed smaller. Flock’s system was designed to return partial matches. It found the larger characters. Officers could see the full plate in Flock’s image but did not verify it before the stop. Flock told Feder that the machine had done what it was asked to do and that humans were expected to check the result.
That explanation matters. The failure did not belong solely to an algorithm or solely to an officer. It emerged from the system between them: incomplete government data, a private matching platform, automatic alerts, broad geographic coverage, and a police response that treated a lead as a target.
Before Feder ever became a target, his car had passed an ordinary-looking roadside camera. No warrant had been issued. No officer was following him. The camera recorded first.
That is Flock’s architecture in miniature.
The camera is the entrance
Flock sells fixed cameras and the cloud software that makes their output searchable. Flock’s FAQ says the cameras run on solar and battery power and use a cellular LTE connection, which is what lets them go up without wiring. Its license-plate readers do not wait for suspected vehicles. A motion sensor triggers as traffic passes. Its system extracts the plate number and state, photographs the vehicle, and records the date, time, and camera location. Machine learning classifies visible features such as color, make, body type, damage, bike racks, trailers, toolboxes, and other alterations. Flock says one camera is designed to cover about one and a half lanes heading in a single direction, so catching both directions takes at least two. Flock’s own LPR policy lists the collected fields, and its product materials describe searches by distinctive vehicle features.
Flock says its cameras do not use facial recognition and are “not designed to search for people, scan faces, or track individuals.” Those limits matter, but the records are not anonymous. A plate can be linked to a registered owner through government databases, while repeated sightings can disclose where a vehicle sleeps, works, worships, protests, receives medical care, or visits another person.
The camera does not know whether you are dangerous. It records you first and leaves that question for someone else.
Flock reports more than 12,000 customers, connections to more than 4,800 agencies, and 20 billion plate reads a month. These are company figures, not an independent census. Observations are not unique people or vehicles.
Flock does not sell only to police. Its customers include homeowners associations, apartment complexes, retailers, schools, health-care facilities, places of worship, and other businesses. Flock’s evidence policy says customers “may choose to share their data with law enforcement.”
A town may approve twenty cameras, an HOA two, and a retailer one parking lot. Each purchase looks local. Their value compounds nationally.
Who owns the view
The word “ownership” obscures as much as it clarifies.
Under Flock’s current standard terms, the customer owns “Customer Data,” including captured images, audio, video, and associated metadata. Flock retains title to its hardware, software, algorithms, data models, and outputs it defines as “Flock Property.” Customers receive limited platform access. They may download their data during the contractual retention period, but Flock controls the delivery method. The standard terms also grant Flock an irrevocable, perpetual, worldwide license to use customer data to provide, support, and improve its products and services.
Some cities negotiate better language. Dunwoody, Georgia, obtained a 2026 agreement stating that Flock may not use city data to train or improve machine-learning models without written approval and may not use it for unrelated analytics or aggregation. That variation proves the point. “The customer owns the data” is not a complete description. The operative rights depend on the contract.
Flock’s standard terms provide the service “as is,” disclaim error-free results, and generally cap its aggregate liability at the fees paid during the previous twelve months. Customers are responsible for their users and legal compliance. When a search becomes an armed stop, the contract pushes operational risk toward the agency.
Flock’s default retention period is seven days, according to its LPR policy (updated June 30, 2026), its evidence policy, and a June 2026 blog post. Its privacy policy, last updated in August 2025, still says thirty days. The company says deletion is automated and permanent, run by an Amazon S3 lifecycle policy, and tested annually in a SOC 2 Type II audit. But the default is not a universal ceiling. The evidence policy allows a customer-specific period, and up to one year with approval from an elected official or governing body. Legal holds and applicable law can extend retention. Customers may download images and investigative summaries before deletion and keep those copies in their own systems. Flock offers a validator for images already downloaded beyond the original retention window. Its terms say Flock need not delete data it is obligated to retain, such as inter-agency audit log integrity records or metadata held for evidentiary authentication. The privacy policy also says data may remain on a camera until storage capacity is reached or seven days pass.
The honest description is narrower: seven days is Flock’s current default for the searchable cloud record unless a contract, law, preservation step, export, or separate system changes the practical result.
Drivers have no comparable control panel. They cannot opt out on public roads. Flock directs noncustomers seeking evidence to the customer. Access depends on public-records law, exemptions, retention, and knowing who operated the camera. Correcting a bad hot-list entry may require finding another state or federal agency before the next alert.
Five doors into one network
Public debate often collapses distinct forms of access into one question: Does an outside agency “have Flock”? The system has several doors.
Direct access means an authorized user logs into an agency account. One-to-one sharing means one customer grants another organization permission to search its data. Statewide or nationwide lookup lets an authorized user query many participating networks at once. Indirect access occurs when a local officer runs a search for an agency that cannot search directly. Hot-list access does not require a detective to reconstruct history at all. A plate or vehicle description is placed on a list, and a future camera match generates an alert.
There is also institutional access through regional intelligence organizations and fusion centers. A 2026 San Francisco audit found that the Western States Information Network had improperly searched city ALPR data on behalf of outside agencies nearly 300 times. Police said those queries concerned serious crimes and amounted to about 0.005 percent of searches. California law generally bars such out-of-state or federal access without a qualifying California warrant or court order.
This is why a company can truthfully make a narrow claim that it has no contract with ICE while its customers still assist immigration enforcement. Flock says it has no contractual relationship with any Department of Homeland Security agency, and that federal users will not be added to Statewide or Nationwide lookup. It acknowledges limited pilots with Customs and Border Protection and Homeland Security Investigations. In August 2025, CEO Garrett Langley admitted that some earlier public statements about federal relationships were inaccurate.
The side door remained. Denver audit logs showed more than 1,400 immigration-related searches of the city’s 111 cameras between June 2024 and April 2025. Many were made by police departments elsewhere that entered “ICE” or “immigration” as the reason. In November 2025, an Associated Press analysis of police disclosures found that, through Flock alone, Border Patrol for a time had access to at least 1,600 license plate readers across 22 states. The same analysis found that some counties reported looking up plates on behalf of Customs and Border Protection, even in California and Illinois, which ban sharing data with federal immigration authorities. A Flock spokesperson told the AP the company had “for now” paused its pilot programs with CBP and Homeland Security Investigations.
“We do not work with ICE” and “ICE can never benefit from this network” are different claims.
The log records the harm
Flock’s strongest governance defense is auditability. Searches are tied to individual users, require a stated reason, and produce an audit record. Agencies can apply role-based permissions. Hot-list hits are supposed to be verified by a human. Flock also offers an Audit Assistance feature, which it says helps agencies identify atypical activity.
Those controls have value. They have exposed abuse. They do not make abuse impossible.
In Orange City, Florida, officer Jarmarus Brown allegedly used plate readers to stalk his girlfriend and her family members more than 100 times over seven months, according to the Institute for Justice, which says he was arrested and charged in 2025. The same review has identified dozens of cases nationwide of officers allegedly abusing plate-reader data to monitor romantic interests, most of them since 2024. In Albany, Georgia, five officers were fired and arrested after investigators alleged they used plate-reader data for purposes unrelated to legitimate investigations. Flock says its audit records helped establish what happened.
The audit trail made some victims visible only after the search box was used.
Other cases show mission expansion rather than private obsession. In Johnson County, Texas, an officer searched a network of more than 83,000 Flock cameras, including in states where abortion is legal, for a woman who had self-administered an abortion. Sheriff Adam King and Flock said she was monitored because her family was worried about her safety and that she was never a criminal suspect. The Record reported that documents obtained by the Electronic Frontier Foundation show the “death investigation” that triggered the search began two weeks after the abortion, which undercuts the sheriff’s account. The Electronic Frontier Foundation wrote that the search may have run afoul of privacy laws in Washington and Illinois.
An Electronic Frontier Foundation analysis of ten months of nationwide audit data found more than fifty agencies running hundreds of searches connected to protests. The records do not prove that every search was improper. Crimes can occur at demonstrations. They do prove that political activity entered the query field.
Flock offers public portals where participating agencies can post policies and aggregate use. This is better than silence, but it is voluntary and not independent oversight. A portal may report searches or hits without identifying who was queried, which outside agency benefited, whether the stated reason was true, or what followed.
Audit logs deter only when users expect review, reviewers are independent, reasons are verified, and violations carry consequences. Otherwise they are surveillance receipts.
The case for Flock
The strongest defense of Flock is not hypothetical. License-plate readers can recover stolen cars, locate missing or endangered people, and provide leads in murders, kidnappings, robberies, and hit-and-runs. Columbia, Missouri, police reported that in 2025, when two children were taken from a motel, the Flock system found the car minutes after an Amber Alert, and the Highway Patrol located it and arrested the suspect, according to KOMU. Earlier research on ALPRs found increased stolen-vehicle recoveries and arrests for auto theft, though studies of crime prevention have found varied effectiveness. The National Policing Institute summarizes both the benefits and the limits.
Crime victims are not props in a privacy argument. A tool may help solve a murder and still be too broadly deployed. The relevant question is not whether Flock has ever produced a good outcome. It has. The question is whether benefits in specific cases justify collecting everyone first, sharing by default or confusing configuration, and relying on after-the-fact discipline.
Flock’s defenses should therefore be credited precisely. Seven-day default deletion reduces exposure compared with indefinite storage. Flock’s statement that its cameras do not use facial recognition, if accurate, reduces one form of identification. Role-based access and search logs make misconduct easier to reconstruct. Flock’s evidence policy says all stored data, including metadata, is encrypted at rest with AES-256. Local control can let a city impose warrant rules or prohibit external sharing.
Then the defenses must be tested.
San Francisco’s audit found searches that violated California law. Flock has said it would designate federal customers as a distinct “Federal” user category, and says it now requires a standardized offense type before a search can proceed. In Oshkosh, Wisconsin, the council rescinded a renewed contract less than twenty-four hours after its police department determined that the platform could create vehicle heat maps, contradicting what a Flock representative had told the council. Flock said its representative had understood the question as asking whether people can be tracked. The council voted unanimously to reverse itself.
Local control is only as real as local understanding.
A constitutional question still moving
Flock says its cameras capture point-in-time images of vehicles in areas visible to the public, where there is no reasonable expectation of privacy. In January 2026, a federal district judge granted Norfolk, Virginia summary judgment in a challenge to its network of 176 Flock cameras, finding that on the record in that case the plaintiffs were not subject to an unconstitutional search. The plaintiffs appealed, and the ACLU and the Electronic Frontier Foundation filed a brief in the Fourth Circuit on April 20, 2026.
The constitutional objection concerns aggregation. In Carpenter v. United States, the Supreme Court held that people retain an expectation of privacy in the whole of their physical movements recorded through cell-site data. On June 29, 2026, the Court extended that reasoning in Chatrie v. United States, holding that police acquisition of Google cellphone location history was a Fourth Amendment search. The Court noted, as it had in Carpenter, that this kind of tracking capacity “runs against everyone,” not just those “under investigation.”
Chatrie did not decide ALPRs. Flock says each camera read is a single event on a specific roadway and that its cameras do not continuously track a vehicle’s movements. Civil-liberties lawyers argue that a dense, searchable network can reveal the same protected mosaic by another technical route. The Supreme Court has not resolved that question.
The law is unsettled because scale changes the act. One officer seeing one plate is observation. Thousands of privately operated cameras retaining billions of time-stamped sightings create an institutional memory no patrol force could reproduce.
