Documented Incident

Police MisuseCities RejectingLegislationPublic OppositionSouth Carolina

Upstate South Carolina agencies suspend or review Flock cameras after five employees fired for misuse

Five law enforcement employees across three Upstate South Carolina agencies were fired in recent months over alleged misuse of Flock Safety license plate reader systems, including officers accused of running searches on former partners and entering false justifications to disguise the queries. Greer suspended its Flock program for 90 days beginning Aug. 21, and the Oconee County Council advanced a "Protection from Mass Surveillance" ordinance on Aug. 18 to defund cameras on county roads, with a final public hearing set for Sept. 15. Residents addressed the Greenville City Council on Aug. 24 asking for removal of the city's cameras, while Pickens County Sheriff Tommy Blankenship publicly defended the technology and called for stricter guardrails. None of the fired employees has been criminally charged.

Why this matters

The cluster of firings shows ALPR audit logs can surface misuse but only after months of unauthorized searches, and the varied local responses — suspension, defunding proposals, or continued use with added policy — offer other communities a range of oversight models to weigh.

Key facts

Sources

This summary was written from the published reporting below and links to it; BlockFlockNow does not reproduce article text.

More from South Carolina

Everything we have documented in South Carolina, or search every South Carolina article in the archive.

About this record

BlockFlockNow documents reported incidents involving Flock Safety cameras and automated license plate readers: council votes, contract decisions, misuse by authorized users, lawsuits, audits, and community response. Every record is reviewed by a person before publication. New to the topic? Start with What is Flock?, find meetings near you, or learn how to request your town's camera records.

Updated September 21, 2026. Corrections: blockflock@bytebunny.io. See all documented incidents or search the full article archive.