PUBLIC - This article does not require an IPVM subscription. Feel free to share.
Flock CEO Garrett Langley has spent months under pressure as documented cases of police misusing his company's license plate reader network have multiplied. In an Aug. 13 USA Today interview, he reached for an analogy to describe it:
It is, a cop checks his daughter's boyfriend's criminal record. It is, a cop checks ex-partner's location.
Both are instances of officers misusing law enforcement access for personal purposes, and that much is accurate. But placing them in the same sentence, as equivalent examples of the same underlying misconduct, works to excuse what documented Flock abuse actually looks like and obscure Flock's own role in enabling it. Cases of officers using Flock to stalk ex-partners have been surging: new arrests, terminations, and investigations are surfacing across multiple states, with fresh incidents reported nearly every day. A Georgia Bureau of Investigation (GBI) arrest of a police chief for stalking multiple individuals, a detective running 179 unauthorized searches on two women, an officer who ran 600 queries on an ex-partner and her teenage daughter — these are what the analogy was standing in for.
Executive Summary
Langley's analogy is a deliberate strategy: frame Flock misuse as one tile in a mosaic of police database abuse that long predates Flock. The two examples he chose do share a category — unauthorized personal use of law enforcement access. But the analogy massively understates the severity of what the documented cases show, and papers over Flock's own specific accountability failures that made the abuse possible at scale. Criminal records are largely public; Flock location data is not. Checking a boyfriend's record is often protective in motive; tracking an ex-partner across months is predatory and actionable in real time. Flock reconstructs a physical life in a way no static record can. Now, facing that surge, Flock is finally making its audit safeguards mandatory. But how well the new tools will work, and what abuse they will miss, remains an open question, particularly without a warrant requirement.
No Response from Flock
IPVM reached out to Flock for comment on Aug. 14, 2026, and did not receive an immediate response. This post will be updated if a response is received.
The Analogy and Its Argument
Langley's daughter-boyfriend comparison reflects an argument he has made across several outlets: that police systematically abuse their tools, and that Flock is simply the system now surfacing it. To Newsweek on Aug. 13, he said:
Police abuse was here 20 years ago, and we think that the problem is no one else is shining the light on what law enforcement does.
On TBPN the same day, he said:
Lo and behold, law enforcement abuses their power at times. And that's horrible, right?
The comparison does not hold against the conduct it was meant to represent.
The Access Distinction
Criminal records are largely public. Court filings, arrest histories, and conviction data are available through state court websites and commercial background check services accessible to any civilian. A cop checking his daughter's boyfriend's record through a law enforcement database is reaching something civilians can reach through slower channels. The privileged access adds speed; it does not add a capability that otherwise does not exist.
Flock location data is different in kind. Real-time vehicle tracking across a network of 120,000 cameras in 49 states is exclusively accessible through law enforcement credentials. No civilian equivalent exists. When an officer queries an ex-partner's vehicle, they access a capability the target cannot reach, cannot audit in real time, and cannot defend against. The two are not comparable in what the misuse actually enables.
The Intent Gap
The construction of Langley's analogy is as telling as its content. He did not reach for a neutral example. He chose the most emotionally sympathetic possible framing: a father, a daughter, protective instinct. He placed it first, then paired it with checking an ex-partner's location, presenting the two as the same category. They are not.
The documented Flock abuse cases are not protective in motive. A Georgia police chief was arrested for using the system to stalk and harass multiple individuals; he died by suicide before standing trial. A North Carolina officer tracked her boyfriend's ex-wife 31 times, including twice while off duty, entering fabricated justifications into the system to obscure the searches.
An Arizona officer resigned after using Flock to track his own wife and asking another department to assist. A Milwaukee officer ran 179 combined searches on a partner and a former partner over months; Flock's own systems did not detect it. The victim discovered the abuse through a third-party website. In another documented case, an officer ran 600 stalking queries on an ex-partner and her teenage daughter. A Washington Post investigation documented 50+ instances nationwide of officers misusing LPR, including 46 using Flock. About half the cases involved stalking former romantic partners.
Reconstructing a Life, Not a Record
A criminal records check produces a static document: prior arrests, convictions, outstanding warrants. It captures what happened to someone in the past. It does not tell you where they currently are or where they are heading.
Flock data is different in kind. Sustained queries on a target's vehicle can reconstruct where they sleep, where they worship, who they meet, and when they deviate from routine. That information is directly actionable in real time. The Milwaukee detective running 179 searches was not building a historical record. He was maintaining live surveillance on two women over months. A criminal records check has no equivalent capability.
Langley's own announcement made this distinction implicitly. Flock's blog noted that 90% of investigative searches happen within a week of a scan, framing the 7-day retention cut as a privacy advance with minimal investigative cost. That framing concedes that location data ages into actionability over time. A criminal record does not expire on a seven-day clock.
Flock's Own Accountability Gap
Flock LPR misuse has a specific structural remedy that other database abuses do not: warrant requirements would eliminate the personal stalking use case almost entirely, since no judge would authorize a search of an ex-partner's location. Flock's own chief attorney has publicly conceded that warrant requirements are likely inevitable as the company grows. Langley did not endorse them on Aug. 13.
Flock also did not simply inherit the accountability gap. Flock removed officer usernames from audit logs in coordination with the FBI, directly undermining the accountability function Langley now leads with publicly. The Milwaukee detective who ran 179 searches went undetected for months, surfacing only after the victim found evidence through a third-party website, not through Flock's own systems. Flock built this system to scale — 120,000 cameras, 6,000 law enforcement agencies, an $8.4 billion valuation. Mandatory safeguards that added friction to police adoption were not part of that growth plan. As the ACLU has noted, Flock's business model was built around expanding the network as fast as possible. The accountability tools exist now because the company was forced into them. Now Langley is blaming the police.
Conclusion
Langley's daughter-boyfriend analogy is a deflection dressed as an acknowledgment. He concedes police abuse exists, places Flock misuse in the broadest possible category of pre-existing misconduct, and reaches for the most sympathetic example available to represent it. What the analogy was actually standing in for: a police chief arrested for stalking multiple people, a detective running 179 unauthorized searches on two women while assigned to audit the very system he was abusing, an officer who ran 600 queries on an ex-partner and her teenage daughter. The gap between the framing and that record is not incidental. It is the same instinct that led Langley to once call his critics a terroristic organization. Then he blamed activists. Now he is blaming his own customers.