Security1 distinct publisher3 min readPublished
Michael Fultz typed the word "investigation" into Flock's mandatory reason field and queried his ex-girlfriend's plate off duty. Brevard County named him Deputy of the Year the same day she wrote to complain.
The Watch · Security desk
Compiled by The WatchSomething wrong?How this is made
Flock's control against this is a text box. The system will not run a plate search until the user enters a reason [11]. Fultz entered "investigation" and filed the query as a general investigation [12]. The field records an assertion; it does not test one against a case number, a supervisor, or a duty roster.
The metadata around the query was more informative than the query's stated purpose. Fultz told investigators that all his Flock inquiries came from his agency-issued cell phone rather than his agency laptop, and he agreed that the timestamp meant he had entered the registration number before leaving for work [14]. Investigators separately established that he accessed Flock while off duty [13]. Device, hour, and repeat hits against a single plate were all in the log the whole time. None of it surfaced until a letter arrived.
The order of events is the finding. The complaint letter reached the sheriff's office on the day of the awards ceremony [6]. The letter opened the internal investigation, and the investigation is what led to the Flock logs [7]. The audit then showed Fultz had tracked her movements, which he had denied doing [9][10]. So the delay between the searches and their discovery was governed by his ex-girlfriend's decision to write to his employer, not by any review cycle at the agency or in the platform [18]. Hired in 2024, named Deputy of the Year in 2025 [4][5], Fultz had his search history read for the first time roughly a year into the job, and only because an outsider asked [19].
Credit the log for the one thing it did. Fultz offered investigators two alternative explanations, that he may have been demonstrating how Flock works and that he already had her location on Snapchat so a Flock query would have gained him nothing [15]. The retained query records made both accounts untenable [10]. That is evidentiary value in an administrative case, and it is not the same as detection.
The rest of the 43-page file argues the same point about supervision generally [2]. Investigators counted at least four traffic stops for speeding on a covered-tag motorcycle, one of them at 111 MPH, each ending when Fultz identified himself as law enforcement [16]. They also recorded that within 30 minutes of a direct order to keep his tags visible, he rode out of the sheriff's office parking lot [17]. The sexual misconduct, the racial slurs in texts, and the photographs posed as Hitler are why he resigned [1][21], and none of them were ever going to be caught by an ALPR access control.
For anyone running one of these networks, the reason string is a compliance artifact. The controls that would have flagged Fultz are pattern queries over data Flock already keeps: same plate, repeat lookups, off-shift hours, mobile device, no linked case. That is analyst time, not licence spend.
Ranked by verification strength, evidence, and original report placement.
Brevard County deputy sheriff Michael Fultz resigned from the force after an internal investigation detailed alleged sexual misconduct, racism, and abuse, including his use of Flock to stalk his ex-girlfriend.
News6 in Florida first reported the story, and 404 Media obtained a copy of the investigation and reported additional details about Fultz's use of Flock.
On the day of the Deputy of the Year ceremony, Fultz's ex-girlfriend sent a letter of complaint to the sheriff's office with a long list of complaints about his behavior.
Distinct publishers with included, body-backed reporting in this cluster.
1 article · August 27, 2026
Follow any of these and your For You feed starts watching them — no settings page required.
security
A man in a Vader helmet turned Flock's San Diego contract into a procurement problem1 distinct publisher
security
NPS Bought Flock. Internal Paper Says License Plate Reader; Public Statement Says Traffic Counts1 distinct publisher
security
Flock's CEO told cops the abortion-search story was 'entirely false.' The affidavit says otherwise1 distinct publisher
security
Three felonies for a few dollars of filament: Oviedo's decoy Flock camera sting1 distinct publisher
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
Primary internal investigation document, quoted at length
The reporting rests on an obtained 43-page administrative investigation, quoted directly on the Flock log audit, the reason-field entry, off-duty access, the subject's own denials, and the disciplinary outcome. That is unusually strong documentary grounding for a misuse story. It is discounted because a single publisher carries the cluster, no vendor or agency comment is present, and the volume and duration of Fultz's queries are never quantified.
Deployed ALPR systems with audit trails that agencies read reactively
The source documents four concrete real-world events across at least four agencies: the Brevard audit finding, an arrest in Charlotte, South Carolina, a firing after an audit surfaced 166 lookups, and one town suspending its Flock contract. That establishes live deployment and repeated post-hoc detection across jurisdictions. It falls short of high adoption measurement because the source gives no counts of agencies, cameras, queries, or audits performed.
Slightly overstated on the audit-timing inference, otherwise aligned
Nearly every assertion in the cluster is quoted from an obtained investigation, so the framing tracks the evidence closely. The modest positive gap comes from the derived implication that the log history had gone unread until the complaint arrived: the 2024 hire, 2025 complaint and 2025 audit are documented, but no source states that no earlier review occurred. The vendor-level implication that the reason field cannot be validated is also not tested against any statement from Flock.
Adversarial primary record plus a surveillance-accountability beat
The underlying document is an agency record produced under disciplinary pressure: the complainant is the subject's ex-partner with a direct stake, and Fultz's quoted denials are self-interested, which the article correctly presents as claims rather than findings. The publisher runs a sustained surveillance-accountability beat and is subscriber-funded, so the framing incentive favors systemic indictment of the platform. No commercial or promotional incentive is evident in the reporting, and the log audit provides an independent check on the complainant's account.
Strong document, single publisher, one unverified inference
Confidence is high on the factual spine because it is quoted from an obtained primary investigation with a corroborating log audit and a documented resignation. It is held below the top band because the cluster contains one publisher with no vendor or agency rebuttal, the comparison cases are summarized without their own sourcing, and the audit-timing inference remains unestablished.