PUBLIC - This article does not require an IPVM subscription. Feel free to share.
Privacy critics have long used Flock's name as their preferred expletive. Now the president of the country's largest police union has sent a similar message to Flock CEO Garrett Langley: a press release titled "Who the Flock Do You Think You Are?"
Fraternal Order of Police National President Patrick Yoes published the statement days after IPVM exclusively documented Langley's turn against his own police customers. The FOP, representing 382,000+ officers, quoted Langley's own prediction that officers would be arrested for abusing Flock, declaring it a breach of the trust the profession had placed in his company.
Executive Summary
The FOP statement is the institutional confirmation of a rupture IPVM documented first: one Langley brought on himself. The accountability changes he announced were defensible. Mandatory safeguards, reduced data retention, automatic lockouts for abuse: a company can implement all of that while expressing support for the profession using its product. Langley chose instead to tour ten national outlets predicting mass officer arrests, demoting police from customers to bill-payers, and framing Flock as the institution finally holding law enforcement accountable. None of that was required. It was a choice. The FOP's rebuke is a direct consequence of it. The deeper problem is the pattern it reveals: when Flock faces criticism, Langley finds someone else to blame.
FOP's Public Rebuke
Yoes's central charge, directed at Langley personally, captures the contradiction at the core of Flock's August: a company cannot build a business on police trust and then declare those same officers the problem when public criticism of its product follows. The FOP statement started by quoting Langley's own Vanity Fair prediction back at him:
You will see over the next six months a dramatic increase in officers being arrested or fired for abusing Flock, because we are forcing our customers to do it now.
Yoes did not leave the reversal implicit. He reached back to April, when in Yoes' words, Langley "argued that society already entrusts police officers with enormous responsibilities, including the authority to use force, and questioned why those same officers should not be trusted with license plate reader technology." Those four months had not been quiet ones for Flock: the company was already embattled, in part because Langley had called privacy advocates "terroristic" and accused opponents of wanting to "normalize lawlessness", statements that generated their own backlash and drew national scrutiny. The response to that pressure was not to lower the temperature. It was to open a second front, pinning the blame on the law enforcement community that had defended him by touring ten national outlets to predict mass officer arrests.
The FOP also cited Langley's concession on a specific platform safeguard: "We got this one wrong. We should make it a requirement." That line was not an admission that Langley misjudged his turn against law enforcement. It was an acknowledgment of a technical shortcoming in Flock's product, that a particular safeguard should have been mandatory from the start. The FOP's point was different: that Flock itself has acknowledged failures in its own product, and the response to those failures should be fixing them, not redirecting blame onto officers.
Yoes closed with a call for mutual accountability:
Flock and law enforcement should be partners in public safety. Partnership requires mutual trust and accountability. Flock should focus on strengthening its technology, supporting sound policies, and rebuilding public confidence, not diminishing the profession that helped build its company.
IPVM Called This First
IPVM was the first, and to our knowledge the only, publication to document and analyze Langley's turn against law enforcement as a deliberate strategic shift. Our August 17 report aggregated Langley's statements across 10 interviews, showing a CEO who had repositioned law enforcement from partners to liabilities: demoting police as customers, dismissing the profession as biased and understaffed, and blaming officers for abuse that his own platform fostered. The FOP's August 21 statement responds directly to those same public statements, confirming what IPVM assessed as a fundamental rupture.
Police Support Was Existential to Flock
Flock's relationship with law enforcement was never purely commercial. Officers were advocates: they defended Flock at city councils, pushed back against privacy critics, and helped the company win sole-source contracts that competitors could not touch. Law enforcement veterans like Jamie Hudson, Flock's former Director of Product Consulting and Training, who departed Flock earlier in August 2026 without endorsing its mission on the way out, were hired specifically to translate that trust into institutional relationships. That function is now compromised.
An Unforced Error
Every accountability change Langley announced was defensible on the merits. Mandatory case codes, automatic lockouts for abnormal search behavior, reduced data retention from 30 days to seven: these are policies a company can implement, and defend, without declaring war on the profession using its product. There is a standard playbook for exactly this situation. Acknowledge isolated misuse. Emphasize that it is rare. Express support for the overwhelming majority of officers who use the system legitimately. Announce the new safeguards as a partnership with law enforcement, not a verdict against it. Companies navigate "bad apples" problems without burning the orchard every day.
Langley chose differently. Across ten national outlets: CNN, Bloomberg, Vanity Fair, Pirate Wires, Puck, SFGATE, TBPN, CBS News, Newsweek, and the Washington Post: he delivered a systematic indictment of law enforcement: calling officers abusers, predicting their mass arrest, calling on state regulators to criminally prosecute his own customers, and declaring to a national television audience that police "might pay the bills" but the community is Flock's real customer. He also described on camera, step by step, exactly how an officer would use Flock to stalk someone. None of those statements were required by any product update he made. They were a choice.
The FOP's rebuke is, in part, a consequence of that choice. Had Langley announced identical policy changes while maintaining the posture of a law enforcement partner, it is unlikely the country's largest police organization would have responded with a press release calling him out by name. The accountability measures were not the provocation. The ten-outlet media campaign portraying police as the threat Flock was built to contain was.
The Case for Langley
The FOP is not a neutral actor here. Its institutional interest is in protecting officers from accountability, including those who genuinely abused Flock. The documented cases of officers using the platform to track ex-partners across multiple days are real. The FOP's own statement concedes as much: "When an officer intentionally misuses technology, it should be addressed." Langley was addressing it. Readers who are skeptical of law enforcement will read the FOP's statement as exactly what it looks like: the police union protecting officers from consequences for genuine misconduct.
That reading has force. Where it falls short is on the business question. The FOP's objection is not that Flock should ignore abuse. It is that Langley announced his accountability push through a sustained national media campaign that cast the entire law enforcement profession as the threat. A CEO who wants to catch bad cops does not need to appear on ten national outlets predicting mass officer arrests. He needs a working abuse-detection system and a clear policy. Langley built the policy. He also built the media campaign, and those were two distinct choices.
The False Alert Problem Compounds It
Flock's mandatory AI abuse-detection system, Audit Assistance, is already generating false positives on legitimate police searches before its mandatory rollout is even complete. Well-connected law enforcement sources report officers conducting routine, authorized queries being flagged a dozen or twenty times per day. The system has no stated access to case files, dispatch logs, or shift assignments that would distinguish routine patrol from stalking; it infers intent from behavioral patterns alone.
In an ordinary vendor relationship, a wrongly flagged search triggers an administrative review, gets cleared, and the officer moves on. Under Langley's current public posture, the stakes are different. A CEO who has publicly declared he wants officers arrested and fired has made every false positive into a reputational event. An officer wrongly flagged has no visibility into the AI's criteria, no stated appeal mechanism, and a CEO on record predicting their arrest. The technical problem lands on top of the relational one.
Conclusion
Langley's pattern across 2026 is consistent: when Flock faces criticism, he finds someone else to hold responsible. Privacy advocates who raised concerns about his cameras were a "terroristic organization" trying to "normalize lawlessness." Officers who abused his platform became the systemic threat Flock was built to expose. Each pivot reframes his product's failures as someone else's character problem. The FOP's statement is the institutional response to that pattern, from the constituency that had been most loyal to him. Law enforcement defended Flock at city councils, pushed back against privacy critics, and helped him win contracts no competitor could touch. Langley repaid that loyalty by cheering their mass arrest on national television. Whether he can recalibrate his posture toward police before the damage to the company becomes permanent is the question the FOP's statement has forced into the open.