From the Public Safety edition of October 18, 2026
Shelton, Wash., police audit of 2.67 million Flock network entries finds 943 outside-agency immigration-linked searches under former sharing settings and none after restrictions
Shelton Police Department (Washington) · Policing / ALPR network-sharing audit and access controls · Shelton, Washington, United States
- Publisher
- Shelton-Mason County Journal
- Original publication
- Oct 15, 2026
- Source retrieved
- 2026-10-19
What happened
Shelton police reviewed about 2.67 million Flock network-audit entries from April 2025 to July 28, 2026 and identified 943 outside-agency searches with a strong immigration-related connection plus 1,952 entries referencing HSI or an immigration agency without establishing purpose; all immigration-linked searches occurred in 2025 under former nationwide-sharing settings and none were attributed to Shelton personnel. The audit stresses an entry means Shelton’s network was in the searched pool, not that its cameras returned data. After restricting access to authorized Washington agencies, requiring command approval and two-year audit-record retention, 2026 entries showed no immigration-related searches and a 96 percent drop in network activity between October and November 2025.
Why it matters
Unlike outright bans covered elsewhere tonight, Shelton models a measurable control path: self-audit, restrict sharing, require stated purpose and approval, and publish results. It also shows what network-audit logs can and cannot prove, which matters for every agency answering council questions about federal access to plate data.
Evidence and measured results
Opened the local newspaper article quoting the SPD audit report The audit report itself was not opened; earlier broadcast coverage of the same audit was seen in discovery but is not relied on here.
Limitations and uncertainty
Department self-audit reported by local press; audit report not opened; cannot show whether Shelton data was actually returned; small 12-camera network.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-19; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Agencies cannot answer whether outside or federal users searched their ALPR network and whether current safeguards prevent it.
- Stakeholders
- Police chief
- City council
- City attorney
- Records or audit unit
- Community advocates
- Discovery questions
- When did you last audit outside-agency searches of your ALPR network?
- What sharing settings were active historically?
- Do your logs show data returned or only search inclusion?
- What approvals are required for outside requests?
- Value hypothesis
- A documented audit and control review gives councils evidence to keep, restrict or end ALPR with a defensible record.
- Potential engagement
- 4-week ALPR network-sharing audit and safeguards report ahead of contract renewal.
- Unsupported claims
- That Shelton data was given to immigration authorities
- That restrictions eliminate all misuse
- That ALPR improves clearance rates
Pre-sales engineering
Role takeaway
- Fit
- Agencies with Flock or similar networks that previously enabled broad sharing.
- Architecture and integration
- Export vendor network-audit logs, classify search reasons, correlate with sharing-setting history, and report by period.
- Prerequisites
- Vendor audit log export
- Sharing-setting change history
- Classification rules for search reasons
- Constraints
- Logs may not show results returned
- State law limits (e.g., Washington Driver Privacy Act)
- Vendor-controlled network configuration
- Security
- Restrict sharing to vetted in-state agencies, require purpose and approval per request, and retain audit records two years.
- Proof of value
- Proposed: reproduce classification on a sample month and compare with manual review
- Proposed: demonstrate that out-of-state queries are blocked
- Proposed: request vendor evidence of result-returned logging
Delivery
Role takeaway
- Work
- Run historical and ongoing audits, configure sharing restrictions, set approval workflow and publish findings.
- Dependencies
- Vendor cooperation
- Analyst capacity
- Legal review
- Ownership
- Command officer for approvals; records/audit unit for periodic audits
- Skills and adoption
- Train staff on required justification fields and review of vague entries.
- Governance checkpoints
- Pre-renewal council review
- Quarterly audit report
- Annual sharing-list recertification
- Acceptance criteria
- Proposed: quarterly audits published within 30 days of quarter end
- Proposed: blank or vague justifications under 1% of entries
- Proposed: zero out-of-state access in each audit
- Risks
- Audit misread as proof of data disclosure
- Vendor setting changes outside agency control
- Audit fatigue in small departments
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?
Network-sharing settings are the main exposure surface; audit design must distinguish search inclusion from data returned or images viewed, which requires vendor logs beyond search-pool membership.
Governance
Who approves, reviews and stays accountable for outcomes?
Controls adopted: out-of-state access eliminated, Washington-only sharing for lawful purposes, ban on immigration enforcement use (also required by the state Driver Privacy Act since March 30), command-officer approval with requester and purpose, audit log retained two years.
Security and privacy
What data, permissions and controls need testing?
Searches with vague justifications and some protest, political or abortion-related language were found among outside users; retention of ordinary plate data is not stated in this article.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Running a 2.67-million-entry review requires analyst capacity smaller agencies may lack.
Procurement
What should contracts, pricing and exit terms secure?
The council will review the Flock contract before March renewal; interpretation: renewal terms should require exportable logs showing data returned and images viewed.
Operating model
Which teams own the service once it runs?
Police command approves outside requests; department frames transparency as proactive self-examination.
Publication history
- 2026-10-18Public Safety · Issue 407 resources
Stable resource ID: shelton-flock-audit-immigration-searches-safeguards-20261015