From the Public Safety edition of September 24, 2026
Flock CEO letter admits possible human search in camera images, contradicting website claims
Tech Brew · Independent technology journalism · United States (Senate Judiciary scrutiny; nationwide Flock network)
- Publisher
- Tech Brew
- Original publication
- September 24, 2026
- Source retrieved
- 2026-09-25
- Event date
- 2026-09-23
What happened
On Sept. 24, 2026, Tech Brew reported that Sen. Josh Hawley read a letter from Flock CEO Garrett Langley stating it is “possible to search for humans in images taken by Flock cameras,” which the outlet says contradicts Flock’s website claims that cameras do not use facial recognition and are not designed to search for people, scan faces, or track individuals. Flock declined to appear at the Sept. 23 Senate Crime subcommittee hearing. In a statement to Tech Brew, Flock said it is possible to search for the presence of people in images from non-license-plate-reader cameras using visible attributes such as shirt color or glasses, not a biometric template, and that searches related to race, skin tone, or ethnicity are blocked. PR manager Paris Lewbel said the company demonstrated the distinction for Hawley’s staff. Tech Brew frames this as the first time Flock itself admitted people-search capability. Witness Benn Jordan called Flock a canary in the coal mine for mass surveillance; ACLU’s Chad Marlow argued safeguards do not protect against misuse and that Flock’s story changes week to week.
Why it matters
Direct vendor-capability contradiction under Senate scrutiny for U.S. policing surveillance buyers—public-safety procurement honesty issue, not emergency services.
Evidence and measured results
Independent tech journalism quoting Hawley’s reading of a Langley letter plus on-record Flock clarification. Letter PDF not opened as primary; website claims characterized by the reporter.
Limitations and uncertainty
Short article; primary CEO letter not opened. Company clarification may materially narrow Hawley’s quote. No measured false-match rates for people search in this piece.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-25; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- A Senate-read CEO letter admits human search in Flock images while marketing still says cameras are not designed to search for people—creating disclosure and political risk.
- Stakeholders
- Police chief / sheriff
- City/county attorney
- Mayor / council
- Privacy advocates
- ALPR vendor executives
- Discovery questions
- Which of your Flock cameras can search for people presence?
- Do public FAQs still say no facial recognition / no people search?
- Are race/ethnicity query blocks enforced and auditable?
- Who owns the response to Senate/staff capability questions?
- Value hypothesis
- Bounded value is restoring statement-to-config honesty and narrowing person-search exposure—not crime-clearance marketing from this admission.
- Potential engagement
- 2–4 week Flock capability disclosure sprint: inventory, FAQ rewrite, council briefing, vendor attestation.
- Unsupported claims
- That Flock now admits classic biometric facial recognition
- Guaranteed effectiveness of race/ethnicity blocks
- Investigative ROI from people-search features
Pre-sales engineering
Role takeaway
- Fit
- Agencies with mixed Flock ALPR and non-ALPR cameras under congressional capability scrutiny.
- Architecture and integration
- Camera class inventory + people-presence feature flags + attribute query taxonomy + immutable search logs + public disclosure pack.
- Prerequisites
- Authoritative feature matrix from vendor
- Policy defining allowed attribute searches
- Audit export of people-related queries
- Constraints
- CEO declined to testify
- Letter vs PR clarification may diverge
- Nationwide sharing complicates local bans
- Security
- Treat people-presence search as high-sensitivity; monitor for blocked demographic queries and unauthorized person tracking patterns.
- Proof of value
- Config matches public disclosures
- No successful race/ethnicity queries in logs
- People-search uses require documented case purpose
Delivery
Role takeaway
- Work
- Inventory capabilities, update disclosures, brief oversight bodies, and retrain on people-search policy after the letter.
- Dependencies
- Written Flock clarification
- Counsel on FR legal definitions
- Communications capacity for hearing fallout
- Ownership
- Professional standards with CISO co-ownership of feature inventory.
- Skills and adoption
- Train users that ‘no FR’ marketing is insufficient if people-presence search exists; supervisors sample attribute queries.
- Governance checkpoints
- Disclosure FAQ updated
- Council notified
- Quarterly people-search audit
- Acceptance criteria
- Published capability statement signed by chief
- Feature flags documented
- Named owner for vendor attestation updates
- Risks
- Marketing lag after product changes
- Public sees any people search as FR
- Marlow-style critique that safeguards never stop misuse
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Agencies must inventory whether non-ALPR Flock cameras enable people-presence search, document biometric vs attribute modes, and align public FR statements with configured features.
Governance
Who approves, reviews and stays accountable for outcomes?
Congressional amplification of marketing-vs-capability gaps raises disclosure and RFP honesty expectations; self-policing narratives face skepticism.
Security and privacy
What data, permissions and controls need testing?
People-presence search expands beyond plate text into person tracking risk even without classic biometric templates; race/ethnicity blocks are vendor-asserted controls needing audit.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Officers and records staff need clear UI labels distinguishing plate search from people-presence search; PIOs need plain-language capability explainers for councils.
Procurement
What should contracts, pricing and exit terms secure?
Contracts should require accurate capability schedules, notice of people-search features, and audit rights when public marketing claims FR-free or no-people-search status.
Operating model
Which teams own the service once it runs?
Surveillance vendors’ public claims become operational controls that agencies must continuously reconcile with configured features under federal attention.
Publication history
- 2026-09-24Public Safety · Issue 184 resources
Stable resource ID: techbrew-flock-search-humans-20260924