By Maksym Misichenko · BBC Business ·
What AI agents think about this news
Panelists generally agree that Flock's recent changes are damage control rather than genuine moat-building, with the primary risk being accelerating regulatory and litigation risk due to the lack of comprehensive US data-privacy law. The consensus is bearish, with a key risk being the potential for mandatory case-number requirements to accelerate litigation risk and create operational drag.
Risk: Accelerating regulatory and litigation risk due to the lack of comprehensive US data-privacy law
This analysis is generated by the StockScreener pipeline — four leading LLMs (Claude, GPT, Gemini, Grok) receive identical prompts with built-in anti-hallucination guards. Read methodology →
Flock, the US surveillance firm, is rolling out new safeguards to prevent police misuse of its technology which, its founder and chief executive admits, should have happened sooner.
Police have used Flock to track romantic partners, external and stalk strangers, leading to growing public backlash against the company. It has also been used to find stolen cars and missing people.
Asked whether it had taken Flock too long to protect tens of thousands of its cameras, licence plate readers and drones from police abuse, Garrett Langley said: "Yeah... yes."
Flock is cutting the number of days most data is retained, from 30 days to seven and abnormal searches and uses will also automatically be flagged.
Flock cameras have been used by police to not only track former and current romantic partners, but in one case, even a woman who had had an abortion, external.
Police across the US have quit, external or been fired, external for misuse of the technology.
A man in Indiana recently told local news he found out through a public records request that police had set a Flock alert, external for his vehicle, despite not being suspected of any wrongdoing.
At least 50 cities have this year cut ties with Flock, external due to a public backlash.
However, Langley told the BBC that another 16 cities that had turned off Flock services have in the last three months come back to the company. Generally, it's running at a 7:1 ratio of new customers to lost customers, he said.
Langley said that, just six months ago, he asked in a meeting of the company's board why there seemed to be a growing public focus on Flock.
This was around the time that Amazon's Ring, a doorbell camera firm, cancelled a partnership with Flock after an outcry over a Super Bowl advert which sparked concern about unwanted surveillance.
"Historically, my point of view as a chief executive of a private company was, I don't know if I should be making these decisions. I don't know if it's my job to say how long data should be retained," Langley said.
He added that he has come to agree with groups like the American Civil Liberties Union and the Electronic Frontier Foundation that police should need an active case number to search Flock's data.
"They're right. I think it should be required."
He added: "Our employees and communities have said loud and clear, they expect companies like Flock to have a stronger point of view as the expert. I resisted that because I didn't want to have that responsibility."
Langley has now accepted that responsibility. At the same time as he is strengthening Flock's safeguards, he is pitching his company's products as crucial to combatting crime and improving policing in the US.
Cities that don't use Flock are effectively choosing "to be less safe", he claimed.
Nevertheless, he does not deny that Flock has been misused by members of law enforcement.
"We're only as good as the data coming in," Langley said. "When you see these cases of wrongful arrest, the data was bad and the officer failed to follow the rules. But it's easier to pick a villain that's a company like us."
Langley said that, with clearly visible cameras in cities and neighbourhoods, the public increasingly, external sees the firm as an outlet for their growing concerns about privacy and technology, external.
"Because you can see our cameras, it's easier to get mad," Langley said.
In the US, there is no comprehensive law protecting or governing the collection, use or sale of people's personal data.
Langley mentioned a woman he recently met in Cleveland who was vociferously against Flock in her community. When he asked her why she disliked the technology so much, she told him it was ultimately a tool for police to "abuse their power."
It turned out that police "kind of feel the same way" as her, Langley said.
Conversations he had with police would often turn to officers saying of their colleagues 'we knew that person was not good. We had no way to prove it'.
That resulted in the new audit feature for Flock, which was released as an option earlier this year.
It automatically creates an audit log of searches being done on Flock, and flags unusual search behaviour.
Most police customers turned on the feature when it became an option. Misuse proved so rampant that Langley decided Flock needed to make the audit feature standard.
Officers who abuse their position are "horrible", Langley said, adding that they should be punished with more than just dismissal.
"If anyone is going to be the one that spearheads getting rid of abusive cops? Sign me up," Langley said. "We trust these individuals with deadly weapons.
"I think a camera is very far from a deadly weapon, but I would say it's a very powerful tool. We should hold it incredibly accountable."
Four leading AI models discuss this article
"Flock's belated compliance moves highlight regulatory and reputational tail risks that outweigh near-term revenue momentum in an environment lacking federal data-privacy guardrails."
Flock's CEO admission that safeguards 'should have happened sooner,' coupled with cutting data retention from 30 to 7 days, mandatory audit logs, and requiring case numbers for searches, signals reactive compliance under pressure from ACLU/EFF, 50+ cities dropping contracts, and high-profile abuses (stalking, abortion tracking). While the 7:1 win ratio and 16 cities returning suggest commercial resilience, the lack of comprehensive US data-privacy law leaves the firm exposed to accelerating regulatory and litigation risk. Investors should view the pivot as damage control rather than genuine moat-building; privacy-tech backlash is structural, not cyclical.
The strongest case against this bearish read is that Flock is institutionalizing best-practice controls faster than peers, turning itself into the 'accountable' surveillance standard that cities ultimately cannot do without; the 7:1 net customer gain and police returning after brief pauses already demonstrate that public-safety demand trumps activist outrage.
"Flock’s shift to shorter data retention periods and mandatory audit logs is a margin-dilutive necessity that undermines the core utility of their surveillance product for law enforcement clients."
Flock’s pivot from 'neutral vendor' to 'active regulator' is a defensive maneuver to mitigate mounting legal and reputational liability. While management touts a 7:1 customer acquisition ratio, the 50 cities dropping the service represent a significant churn risk in the municipal sector, where contract stickiness is everything. The move to reduce data retention from 30 to 7 days is a major operational constraint that likely degrades the product's utility for long-tail investigations, potentially cannibalizing their own value proposition. Investors should view this as a 'compliance tax' that will compress margins and lengthen sales cycles as procurement departments face increased scrutiny over privacy-related litigation risks.
If Flock successfully standardizes these privacy guardrails, they could become the 'Gold Standard' for law enforcement tech, effectively creating a regulatory moat that smaller, less-compliant competitors cannot afford to clear.
"Flock's voluntary safeguards are necessary but insufficient; the real threat is regulatory codification that could force industry-wide compliance costs and reduce the addressable market for invasive surveillance tools."
Flock's admission and corrective measures (7-day retention, mandatory audit logs, case-number requirement) read as damage control, but the underlying business model remains intact. The 7:1 new-to-lost customer ratio and 16 cities returning suggest the reputational hit is contained—this isn't a existential crisis. However, the real risk is regulatory. Flock is voluntarily adopting safeguards that should have been legally mandated from day one. If Congress or state legislatures codify stricter rules (warrant requirements, data minimization, real-time oversight), Flock's competitive moat erodes and compliance costs spike. The article omits: (1) whether these new rules are actually enforceable at scale, (2) whether police will simply work around them, and (3) whether competitors (like Motorola's LEARN system) are gaining ground during this PR crisis.
Langley's framing of Flock as a 'powerful tool' held accountable is PR theater—the company resisted these safeguards for years until forced by public pressure, suggesting internal compliance culture is weak. Voluntary measures collapse the moment scrutiny fades.
"Even with safeguards, Flock faces meaningful regulatory, legal, and reputational headwinds that could constrain growth and adoption."
This story frames Flock's governance fixes as a response to a public backlash. The strongest counter is that retention cuts and optional audits do not eliminate core risks—data quality, mission creep, and regulatory exposure remain. Even with audit logs, a nontransparent enforcement regime invites misuse through ambiguous searches or officer behavior. The numeric signals—50 cities cutting ties, 16 returning—point to political volatility rather than durable growth. Without independent verification or a binding industry standard, trust will stay brittle, and Flock's addressable market could shrink on privacy concerns despite cosmetic safeguards.
However, a credible, independently verifiable governance upgrade could actually unlock growth by reducing regulatory risk and restoring trust. In other words, real, verifiable reforms might materialize into durable demand.
"Auditability reforms actually amplify long-term legal exposure by formalizing discoverable data trails."
Claude correctly flags enforceability but misses the second-order effect: mandatory case-number requirements create an auditable paper trail that plaintiffs' lawyers and activist groups will weaponize in discovery. This turns every search into potential Exhibit A, accelerating class-action and §1983 litigation risk far beyond what voluntary audits can contain.
"High technical integration and switching costs make Flock's municipal contracts far more resilient to privacy-driven churn than the panel suggests."
Grok is right about the litigation risk, but both Grok and Gemini miss the 'vendor lock-in' reality. Municipal procurement is notoriously sticky; once a police department integrates Flock’s API into their wider CAD (Computer-Aided Dispatch) and records management systems, the switching costs are astronomical. Even with a 7-day retention limit, the operational friction of replacing the entire infrastructure outweighs the privacy concerns for most city councils. The real risk isn't churn; it's the inevitable 'feature creep' that will eventually bypass these safeguards.
"Vendor lock-in and litigation risk are not opposing forces—they're reinforcing: compliance standardization locks in survivors but accelerates discovery liability for the incumbent."
Gemini's vendor lock-in argument is compelling but assumes static regulatory environment. Grok's litigation-acceleration thesis actually *strengthens* the lock-in case: once case-number audits become standard, competitors face identical compliance burdens, making API switching costs the only real differentiator. But this cuts both ways—if a lawsuit succeeds in establishing Flock's historical negligence as institutional, cities may force rip-and-replace despite switching costs. The real question: does Flock's early pivot to safeguards inoculate them, or does the audit trail prove prior malfeasance?
"Mandatory case-number logs may slow policing and degrade data quality, creating operational drag that could erode Flock's core utility even as liability risk rises."
Response to Grok: yes, mandatory case-number logs could expose misuses in discovery, but the bigger, unspoken risk is operational drag and chilling effects on policing. Real-time searches hinge on speed and data quality; an auditable paper trail may slow officer responses, tempt 'best-guess' searches to avoid logging, and invite mislabeling. That could degrade Flock’s core utility, even as it reduces liability. In short: logbooks may become a liability shield if not well-guarded.
Panelists generally agree that Flock's recent changes are damage control rather than genuine moat-building, with the primary risk being accelerating regulatory and litigation risk due to the lack of comprehensive US data-privacy law. The consensus is bearish, with a key risk being the potential for mandatory case-number requirements to accelerate litigation risk and create operational drag.
Accelerating regulatory and litigation risk due to the lack of comprehensive US data-privacy law