Within roughly two and a half hours on September 9, a New Yorker investigation about Flock Safety had drawn 531 points and 443 comments on Hacker News. The developer-facing reason sits in the product architecture: about 130,000 road cameras, bought and governed by separate customers, feed software that Flock markets as a connected search network spanning 49 US states. A camera installed for one neighborhood can therefore become part of a national query surface, depending on its owner's sharing settings.
The investigation reports that around 40 percent of US law-enforcement agencies have contracts with Flock, whose cameras operate in every state except Alaska. It also describes a growing political backlash, including moves by the governors of Texas and Florida to freeze spending or remove readers from state highways. Flock's answer is that customers own the data, decide whether to share it and can review every search. Those facts can coexist. Local control is the mechanism through which a very large network is assembled.
A local camera can answer a distant query
Flock's product page spells out what connection means. Authorized users can search full, partial and temporary plates, or use a feature called Vehicle Signature when they have only a description. The system can connect sightings across jurisdictions. Flock FreeForm accepts natural-language searches and alerts, according to the company. Viewed through the product interface, the cameras form an index for finding a vehicle across participating locations.
Each record also contains enough context to make that index useful. Flock says its automated license-plate readers collect a plate image, vehicle characteristics, a date and time stamp, and a camera-location identifier. Its privacy page says the system does not collect biometric or facial-recognition data. That narrows what the sensor sees, but a plate observed at a known place and time can still reveal a vehicle's route when records are joined across cameras.
The company describes access as role-based and agency-controlled. Its law-enforcement access policy says sharing is optional, each user has an individual account, and every query records a user ID and time stamp. Searches must include an investigative reason. There is no public search box. Once an agency enables sharing, however, participating agencies may see the shared data under the rules that owner has configured. A pole marks where collection begins. The permission graph determines how far a search can travel.
This difference matters when officials call a deployment local. A city may own its records and still expose them to outside investigators. Another city may block that access or permit it only for selected offenses. Flock's August update says its new offense filters let an owner allow searches for a stolen vehicle or a missing person while blocking immigration-related queries. The reach of a search is therefore a setting that can change without moving or replacing any camera.
Seven-day retention leaves local exceptions
On August 13, Flock announced that it was reducing its recommended default retention period from 30 days to seven. The company said more than 90 percent of searches made without a complete plate happen within a week. Its accompanying Evidence Mode, planned to roll out in the following weeks, lets investigators preserve selected records in cold storage for an active case. The announcement presents shorter routine storage and case-specific preservation as the new model.
Existing customers do not automatically move to seven days. Flock said they would keep retention periods already approved under local policy, while customers that adopt the recommendation would receive Evidence Mode at no cost. The company's current privacy page consequently says data is deleted after a set period, often seven days, depending on local law. A claim that the whole network now deletes records after one week would skip that exception.
Evidence Mode adds another distinction. Routine data can expire quickly while chosen observations remain available for an investigation. That can be reasonable evidence handling, but it means retention cannot be audited from the default alone. A useful disclosure has to show the configured period, how often records are preserved, who can preserve them and when cold-stored evidence is finally deleted. Flock says more than 1,500 agencies have published Transparency Portals containing policies, retention periods, sharing partners and search activity. Its announcement urges agencies that have not published a portal to turn one on.
Misuse controls are still being rolled out
The August post also gives a dated view of Flock's abuse controls. The company said Audit Assistance, which flags abnormal behavior for an administrator, had been introduced 16 weeks earlier and voluntarily adopted by more than one-third of customers. Reviews using the feature had been associated with arrests of several officers accused of misusing the system. Flock plans to require Audit Assistance for every law-enforcement customer by the end of 2026. It also says it will automatically suspend access when activity meets its abnormal-behavior criteria.
Case codes follow a similar schedule. Flock introduced an optional requirement in July 2025 for officers to attach a case code to a search. It now plans to make case codes mandatory for law-enforcement searches by the end of this year. Emergency searches may bypass the field, but the system will flag them for administrator review. As of the company's August announcement, two basic controls, a reason tied to a case and automated detection of unusual behavior, were still on their way to universal enforcement.
Reported misuse makes the risk concrete. The New Yorker cites officers accused of using Flock to follow former partners, romantic interests and relatives. It also reports that a Texas sheriff's deputy searched a pool of more than 80,000 cameras in a case involving a woman who allegedly obtained medication for an abortion, and that immigration officers accessed Flock data with help from municipal departments. Flock's new audits may detect some improper queries, but a log records an action after a person has been searched.
Local control can produce opposite outcomes. A customer can deny sharing, choose a shorter retention period and review its users. The same discretion lets another customer retain data longer or share more broadly. Flock can set product defaults and suspend accounts, while rules governing an investigation still come from agencies and applicable law. Network governance is distributed even though the search software is centralized.
Camera removals cover only part of the map
The Texas and Florida actions target spending and physical placement. They do not, by themselves, erase the wider network. Flock says its readers are used by municipal police, businesses, neighborhoods, apartment complexes, schools and other public or private organizations. Removing cameras from a state highway leaves devices owned by those customers, subject to their own contracts and sharing choices.
For public buyers, the contract should expose the same details that determine the system's actual reach. That includes the live retention setting, every sharing partner, enabled offense filters and whether Audit Assistance already blocks suspicious activity. It should also state whether case codes are mandatory today, how emergency bypasses are reviewed, and what happens to preserved evidence when a case closes. Flock says its logs and Transparency Portals can reveal much of this information; publication and oversight still depend on the customer.
Camera maps remain useful because they show where observation occurs. Permission and audit records answer the harder question: who can turn those observations into a journey. The 130,000-camera figure measures physical scale, while Flock's 49-state product pitch measures connection. Neither number reveals how many cameras a typical search can reach, because that total varies with sharing decisions.
The next checkpoint is the end of 2026, when Flock says Audit Assistance and case codes will become mandatory for law-enforcement customers. Watch whether the company documents full adoption, how many older deployments move to seven-day retention, and whether the Texas and Florida restrictions reduce connected coverage. Until those figures are available, local ownership and national reach remain two separately documented properties of the same system.