From the Public Safety edition of September 25, 2026
Franklin County NC fires detective and stops Flock after private-citizen tracking audit
WRAL · Independent local journalism · Franklin County, North Carolina, United States
- Publisher
- WRAL
- Original publication
- September 25, 2026
- Source retrieved
- 2026-09-26
- Event date
- 2026-09-25
What happened
On Sept. 25, 2026, WRAL reported that the Franklin County (NC) Sheriff’s Office stopped using Flock surveillance cameras after an internal audit found Detective Janet Leonard used the system to “track every movement of a single, private citizen.” Sheriff Kevin White said the audit revealed a stream of highly unusual activity that led to an immediate investigation and an alarming discovery; he called the conduct unacceptable, unconstitutional, and a complete violation of privacy by someone whose career should have been dedicated to protecting the public. Leonard was fired; the investigation was forwarded to the district attorney, with prosecution status unknown at publication. The office had used the cameras for nearly a decade. UNC School of Government professor Jeff Welty said reports of Flock misuse are becoming more public and that large information access creates misuse risk needing regulation and policies. Leonard declined comment; WRAL asked when the investigation began and what process will decide whether cameras return.
Why it matters
Concrete U.S. sheriff-office ALPR accountability action—firing plus program stop after personal tracking—core policing/oversight, not fire/EMS.
Evidence and measured results
Same-day local TV/news report quoting sheriff release and Welty. Companion ABC11 opened for indefinite-suspension and past-use review detail but WRAL is the primary citation.
Limitations and uncertainty
Local journalism of a sheriff release; target citizen unnamed; DA charging decision pending; no measured crime-impact data from the stop.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-26; 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 sheriff’s ALPR estate enabled personal tracking of a private citizen until an audit triggered firing and a program stop.
- Stakeholders
- Sheriff / command staff
- County attorney / DA
- County commissioners
- Professional standards / IA
- Privacy-focused residents
- Discovery questions
- How quickly would unusual ALPR query streams surface today?
- Who can suspend the entire camera estate?
- Are past-use reviews possible from immutable logs?
- What return-to-service gates exist after a misuse event?
- Value hypothesis
- Bounded value is detecting and stopping personal-tracking misuse and documenting DA-ready evidence—not maximizing ALPR coverage.
- Potential engagement
- 3–5 week ALPR misuse-response readiness: anomaly rules, suspend playbook, public-comms pack, return-to-service checklist.
- Unsupported claims
- That stopping Flock permanently ends surveillance risk
- Guaranteed criminal prosecution of the detective
- Crime-clearance gains from this article
Pre-sales engineering
Role takeaway
- Fit
- Sheriff ALPR/SaaS estates needing anomaly detection, lockout, and program-level suspend after personal-tracking audits.
- Architecture and integration
- ALPR SaaS audit export → anomaly detection → IdP revoke → evidence vault → optional estate suspend flag.
- Prerequisites
- Per-user authentication
- Immutable query logs
- Suspend/decommission runbook
- DA evidence export path
- Constraints
- Legacy decade-long deployments
- Limited public detail on victim identity
- DA charging timeline outside IT control
- Security
- Treat personal-tracking queries as insider-threat events; preserve chain-of-custody for criminal referral.
- Proof of value
- MTTD for unusual personal-query streams
- Successful credential revoke in drill
- Program suspend exercised without data loss for active cases
Delivery
Role takeaway
- Work
- Execute stop, preserve logs, brief elected officials, define return-to-service gates, and support DA referral.
- Dependencies
- Vendor log export
- Counsel / DA coordination
- Public information officer
- Ownership
- Sheriff with professional-standards co-owner; IT owns log integrity.
- Skills and adoption
- Train supervisors to escalate unusual query streams; train PIO on privacy-preserving disclosure.
- Governance checkpoints
- Program offline confirmation
- Weekly DA-status check
- Return-to-service board decision
- Acceptance criteria
- Named audit owner
- Documented return gates
- Preserved audit package for DA
- Risks
- Silent camera reactivation
- Incomplete historical review
- Public trust loss if stop is temporary theater
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 deployments need anomaly detection on query streams, rapid lockout, and a documented path to suspend the estate when personal tracking appears—not only after-the-fact termination.
Governance
Who approves, reviews and stays accountable for outcomes?
Audit-to-fire-to-DA referral plus program stop shows personnel consequences and temporary decommission as credible responses when purpose limitation fails.
Security and privacy
What data, permissions and controls need testing?
Nearly decade-long camera use did not prevent personal movement tracking; privacy harm is operational, not hypothetical.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
IA/professional standards need capacity for rapid audit triage; PIO needs privacy-safe messaging when targets cannot be named.
Procurement
What should contracts, pricing and exit terms secure?
Renewals should require misuse anomaly tooling, estate-suspend controls, and contractual cooperation on DA evidence exports.
Operating model
Which teams own the service once it runs?
ALPR operations must treat program stop as an available control when purpose limitation fails, not only individual discipline.
Publication history
- 2026-09-25Public Safety · Issue 194 resources
Stable resource ID: wral-franklin-flock-fired-suspend-20260925