From the Public Safety edition of September 21, 2026
EFF analysis of Flock ALPR logs finds unserious search justifications including LMAO and idk
Electronic Frontier Foundation · Civil liberties / independent research · United States (multi-jurisdiction ALPR network audits)
- Publisher
- Electronic Frontier Foundation Deeplinks
- Original publication
- September 14, 2026
- Source retrieved
- 2026-09-22
What happened
EFF’s review of Flock Safety ALPR network-audit logs documents officers nationwide entering unserious free-text search reasons—including “LMAO,” “LOL,” “idk,” “Hehe,” insults, and keyboard mashing—when accessing vehicle location histories. Examples include a Goshen, Ind., officer searching 6,474 ALPR networks / 82,413 cameras with reason “idk,” Priceville, Ala., running 1,954 “TBD” searches, and more than 30 agencies totaling over 6,300 “TBD” searches. Departments contacted often responded with counseling, policy tweaks, or claims that searches were still “legitimate.” EFF argues Flock’s late-2025 shift from free-text reasons to dropdown offense categories reduces transparency and may hide improper purpose behind uniform labels, and urges warrants plus deletion deadlines because ALPR location search typically lacks judicial probable-cause gates.
Why it matters
Directly relevant to U.S. local/state policing procurement and oversight of ALPR networks used for criminal investigations, traffic enforcement, and multi-agency sharing—core public-safety (not fire/EMS) operations. Transferable to courts/prosecutors who rely on ALPR-derived movement histories.
Evidence and measured results
Public-records analysis of Flock network-audit spreadsheets naming specific agencies and reason strings; agency comment responses summarized; no independent recidivism or clearance-rate evaluation of ALPR effectiveness. Quantitative examples are audit-log observations, not a census of all agencies.
Limitations and uncertainty
EFF is an advocacy organization; analysis emphasizes misuse examples and does not estimate the share of all Flock searches that are frivolous. Agency comments asserting legitimacy were not independently re-audited here. Dropdown redesign effects are interpretive.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-22; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Cities deployed ALPR networks for serious crime but cannot defend frivolous purpose fields when auditors or journalists pull network logs.
- Stakeholders
- Police chief / professional standards
- City/county attorney
- City council / privacy board
- Records / transparency office
- IT / vendor manager
- Discovery questions
- Are ALPR purpose fields mandatory and case-linked?
- Who samples search reasons monthly?
- What happens when reason is TBD/idk/LOL?
- Do outside agencies query your cameras without your review?
- Value hypothesis
- Bounded value is demonstrable, auditable ALPR access discipline—not proven crime reduction from this EFF analysis.
- Potential engagement
- 4–6 week ALPR accountability diagnostic: sample logs, map policy gaps, and design case-linked purpose controls with council reporting.
- Unsupported claims
- That ALPR is ineffective for serious crime
- Guaranteed lawsuit avoidance
- That dropdown menus alone fix misuse
Pre-sales engineering
Role takeaway
- Fit
- Investigative ALPR query systems needing enforceable purpose, case linkage, and exportable audits—not autonomous tracking.
- Architecture and integration
- ALPR SaaS → mandatory purpose+case ID gate → immutable search log → SIEM anomaly alerts → professional-standards review queue; no warrantless bulk export to personal devices.
- Prerequisites
- Written ALPR use policy
- Case-management ID validation
- Audit-log retention schedule
- Multi-agency access agreements
- Constraints
- Vendor-controlled UX (dropdown redesign)
- Phone-app mobile querying
- Cross-network searches spanning thousands of cameras
- Security
- Least-privilege roles; encrypt logs; prohibit personal/romantic queries; monitor high-fanout network searches.
- Proof of value
- Sampled nonsense-reason rate declines after controls
- 100% of audited queries have case IDs
- Outside-agency queries routed through authorized channels
Delivery
Role takeaway
- Work
- Policy rewrite, training, monthly log sampling, vendor configuration changes, and public oversight reporting.
- Dependencies
- Vendor audit export
- CAD/RMS case IDs
- Union/discipline procedures
- Council transparency cadence
- Ownership
- Professional standards commander with IT security co-owner for logging controls.
- Skills and adoption
- Officers need purpose-articulation training; auditors need spreadsheet/query review skills; counsel needs ALPR statute literacy.
- Governance checkpoints
- Pre-expansion policy sign-off
- First 30-day audit sample
- Quarterly multi-agency access review
- Acceptance criteria
- Zero accepted TBD/idk/LOL reasons in monthly sample
- Published retention and sharing rules
- Documented response playbook for misuse
- Risks
- Dropdown labels masking improper purpose
- Self-audit capture
- Labor limits on historical discipline
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?
ALPR platforms need mandatory, auditable purpose fields tied to case numbers; free-text or one-click dropdown without corroborating case linkage is insufficient. Prefer architectures that log immutable purpose+case ID, block nonsense strings, and support external auditor export.
Governance
Who approves, reviews and stays accountable for outcomes?
Self-policing via internal review missed frivolous reasons across many agencies; governance should require routine third-party or inspector-general sampling of ALPR justifications, public retention/sharing policies, and legislative warrant/deletion floors.
Security and privacy
What data, permissions and controls need testing?
Unjustified ALPR queries expose continuous location histories of non-suspect drivers; weak purpose logging undermines Privacy Act–style and state ALPR statutes that require documented law-enforcement purpose.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Officers need usable mobile UX that still forces meaningful purpose entry; auditors need time and skills to sample large multi-agency spreadsheets. Training must cover ALPR civil-liberties limits, not only product features.
Procurement
What should contracts, pricing and exit terms secure?
Contracts should require exportable justification logs, configurable mandatory fields, and audit support—not only camera density SLAs. Evaluate vendor UX changes (free-text→dropdown) for transparency regressions before renewal.
Operating model
Which teams own the service once it runs?
ALPR programs need ongoing professional-standards sampling comparable to CJIS misuse monitoring; relying on officers to self-justify without oversight recreates the documented culture of unserious reasons.
Publication history
- 2026-09-21Public Safety · Issue 154 resources
Stable resource ID: eff-flock-alpr-lmao-search-reasons-20260914