Flock Safety, the company behind one of the largest automated license plate reader networks in the United States, retains vehicle surveillance data for 30 days across roughly 90,000 cameras before automatic deletion. That rolling retention window, combined with the system’s reach across some 7,000 local networks, has drawn sharp scrutiny as federal immigration enforcement agencies seek access to the footage. The company recently paused cooperation with several federal agencies, but the scale of the data collection and the investigative exception built into its deletion policy raise questions about how much protection a 30-day limit actually provides.
How the 30-Day Deletion Policy Works
Flock Safety’s standard practice is to hold captured license plate images and associated metadata on a rolling 30-day cycle. After that period, the footage is automatically deleted, according to the company’s privacy and ethics FAQ adopted by cities such as Westfield, Indiana. The policy is framed as a privacy safeguard: data that is not flagged for a specific law enforcement purpose disappears without manual intervention, theoretically limiting how far back officers can look when combing through past vehicle sightings.
But the policy includes a significant carve-out. Data tied to a criminal investigation can be preserved beyond the 30-day window. The city of Everett, Washington, spells this out on its official Flock information page, noting that information automatically deletes after 30 days unless it pertains to an active criminal case. That exception is where the privacy promise gets complicated, because it means the effective shelf life of any individual record depends entirely on whether law enforcement decides to flag it, not on a uniform technical limit.
In practice, the system separates routine data from “evidence” based on user input. An officer who believes a captured plate might be relevant to a case can tag that data in the software, pulling it out of the standard deletion queue. From that point forward, the record is treated more like a traditional investigative file than a transient scan, even though it was collected in the same dragnet manner as every other passing car.
No independent audit has verified whether all 7,000 networks consistently follow the stated deletion timeline or apply the investigative exception narrowly. The available evidence comes from municipal policy pages and Flock’s own documentation rather than third-party compliance reviews. Cities adopting the system appear to rely on the company’s representations, and the public-facing transparency portals referenced by agencies like Everett offer limited visibility into backend data handling, retention overrides, or how often officers mark footage as case-related.
90,000 Cameras and the Federal Access Problem
The sheer size of Flock’s camera network is what transforms a local policing tool into a potential mass surveillance system. Audit logs and public records analyzed by the NOTICE Coalition and provided to The 74 show the company operates roughly 90,000 cameras across 7,000 networks nationally. That footprint means a single vehicle’s movements can be tracked across cities, counties, and states if the networks are interconnected or shared with outside partners, including federal agencies.
The federal access question became urgent when reporting revealed that local police departments were sharing Flock camera feeds with Immigration and Customs Enforcement during immigration enforcement operations. Some of these cameras sit near schools, a detail that drew particular alarm from civil liberties advocates concerned about surveillance chilling immigrant families’ willingness to send children to class. The NOTICE Coalition’s records suggest the data-sharing arrangements were not always disclosed to the communities where cameras were installed, leaving residents unaware that their daily commutes might be visible to immigration authorities.
For everyday drivers, the practical effect is straightforward: any trip past a Flock camera generates a timestamped record of where a vehicle was and when. Multiply that by 90,000 camera locations, and the system can reconstruct travel patterns for millions of people who are not suspected of any crime. The 30-day deletion window limits the historical depth of that record, but a month of location data is still enough to map commutes, identify regular stops, infer home and work addresses, and establish behavioral patterns such as religious attendance or medical visits.
Because the cameras are deployed by a patchwork of local agencies, the network’s reach is not always obvious. A driver might encounter Flock scanners in one city as part of a neighborhood crime-prevention program, then pass others in a neighboring jurisdiction that has agreed to share data more broadly. When those feeds are pooled, the result looks less like isolated neighborhood watch tools and more like a regional tracking grid whose scope residents never explicitly consented to.
Flock Pauses Federal Pilot Programs
Facing growing backlash, Flock Safety took the unusual step of pausing its pilot programs with the Department of Homeland Security, Customs and Border Protection, and Homeland Security Investigations. CEO Garrett Langley issued a public statement on the decision, framing it as a response to concerns about how the technology was being used in federal investigations, according to an Associated Press report. The company said it would review the partnerships and evaluate whether they aligned with its stated mission.
The pause is notable because it came from the company itself rather than from a court order or legislative mandate. That distinction matters. Flock’s business model depends on contracts with local police departments and municipalities, and a public backlash over federal immigration enforcement could threaten those relationships. By voluntarily stepping back from DHS, CBP, and HSI partnerships, the company signaled that commercial pressure and reputational risk can function as checks on surveillance expansion, at least temporarily.
Whether the pause holds is another question. Flock has not announced a permanent withdrawal from federal partnerships, and the underlying technology remains accessible to any local agency that already has a contract. Federal agents seeking license plate data could still request it through local police departments that maintain their own Flock subscriptions, which could route around the company’s pause. As long as local agencies can choose to share their feeds, the structural incentive for federal access has not changed even if the direct pipeline is temporarily closed.
The episode also underscores how much of the current oversight regime relies on voluntary corporate choices. In the absence of binding rules that limit how long data can be stored or which agencies can receive it, companies like Flock effectively set the guardrails for a nationwide surveillance infrastructure. A pause announced in response to public criticism can be reversed quietly later, and the cameras continue to generate a constant stream of location data.
The Investigative Exception as a Backdoor
Most of the public discussion around Flock’s retention policy focuses on the 30-day deletion timeline, but the investigative exception deserves equal attention. When data is flagged as relevant to a criminal case, it exits the automatic deletion cycle entirely. Neither Flock’s FAQ nor the municipal policy pages specify a maximum retention period for flagged data, how broadly “pertains to a criminal investigation” is defined, or who has authority to make that determination beyond general references to law enforcement use.
This gap creates a practical loophole. If a federal agency requests that local police flag certain license plates as part of an ongoing investigation, the associated data could be preserved far beyond 30 days. The policy then functions less as a hard privacy ceiling and more as a default that can be overridden at law enforcement’s discretion. For drivers whose plates happen to match a watch list, pass through an area of interest, or resemble a suspect vehicle, the promise of automatic deletion may not apply in any meaningful way.
Civil liberties organizations have long argued that retention exceptions in surveillance systems tend to expand over time. What begins as a narrow carve-out for serious criminal cases can gradually encompass broader categories of enforcement activity, especially when political pressure to use available tools collides with weak oversight. In that environment, the phrase “active investigation” risks becoming a catchall justification for keeping data that would otherwise be erased.
The lack of independent auditing makes it difficult for the public to assess how often the investigative exception is invoked or how long preserved records are actually kept. Without standardized reporting, residents cannot easily learn whether their local department primarily uses the system for specific, time-limited cases or regularly flags broad swaths of data for extended storage. That opacity, combined with the network’s national scale and the potential for federal piggybacking through local partners, means the true lifespan of a license plate scan may be far longer than 30 days for a significant number of vehicles.
As debates over automated license plate readers intensify, Flock’s 30-day deletion rule is likely to remain a central talking point for both the company and its critics. Yet the key questions go beyond a single number: who gets to override the default, under what standards, and with what external checks. Until those details are clarified and independently verified, the system’s privacy safeguards will rest largely on trust in the very institutions that stand to benefit most from keeping data longer and sharing it more widely.
More from Morning Overview
*This article was researched with the help of AI, with human editors creating the final content.
