Oconee County’s Flock camera ban: what the records show

What this investigation establishes

A county can stop buying a surveillance service without eliminating every way its officers can use surveillance information. That distinction is central to Oconee County’s 2026 Flock debate.

Council adopted Ordinance 2026-26 on September 15, 2026, by 4–1, with John Elliott opposed. The final minutes also record an amendment directing notice to remove county-funded cameras within 14 days and to cover or disable collection in the meantime without damaging them. Source: final minutes, PDF page 7.

Our review identifies six county payments totaling $55,000, conflicting camera counts, municipal search activity after the vote and a significant limit in the ordinance text: certain lawful use of information from another entity remains permitted. The records do not establish a complete removal inventory, lifetime cost, full sharing history or a direct local ICE data connection.

For residents concerned with both public safety and constitutional limits, the accountability question is practical: what did government purchase, who could access the data, and what changed after the vote? These records answer part of that question. They do not justify accusing an officer or municipality of violating the ordinance.

How Flock became a county issue

Automatic license-plate readers record vehicle observations that can be searched or compared with alerts. A vehicle’s appearance in a database is not proof that its occupants committed a crime. Nor is every camera or basic plate reader covered by the ordinance’s definition of a prohibited system.

County financial records establish a Flock payment by June 2022. Reporting places the sheriff’s deployment in that period, but an executed original agreement and installation records are needed to establish the exact start date and first deployed inventory. June 2022 check register, page 7; South Carolina Public Radio, September 16, 2026.

The sheriff has described investigative benefits. In a September 17, 2025 release, the office reported a stolen-vehicle alert on Highway 24 near Tokeena Crossroads and contact with Anderson County authorities. A September 22, 2026 release described Flock evidence from a June 20 incident. The latter release appeared after the ban, but describes earlier evidence; publication date alone does not establish post-ban collection. Sheriff’s September 2025 release; Sheriff’s September 2026 release.

Council’s August deliberations set public-safety arguments alongside privacy and constitutional objections. Those objections were participants’ positions, not a court ruling that every Flock use was unlawful. August 18 minutes, page 4.

Timeline: payment records, votes and later disclosures

A request to preserve or produce records is not evidence that the requested action was completed. A vote directing removal is not a signed removal certificate.

What the ban covers — and the access it leaves open

The September 15 amended packet contains a 32-page version of Ordinance 2026-26. Its final signature and adoption-date fields are blank. We use that meeting-packet text to explain the provisions and the final minutes to establish passage and the floor amendment. A signed, consolidated enrolled copy remains worth obtaining. Packet, PDF pages 19–50.

The text regulates county funds, county contracts, county property and rights-of-way within county authority. It also makes participating government entities ineligible for specified discretionary county funding. That funding condition is not a criminal penalty and does not mean all municipal funding automatically ends.

Its definition is capability-based, not limited to the Flock brand. It combines routine collection of linkable information with listed capabilities such as searchable movement histories or availability to external networks. Basic plate-character reading and exact matching against a lawful hotlist do not, by themselves, meet the listed capability test. Limited exclusions cover certain premises cameras, nonidentifying traffic uses and particularized investigative or emergency circumstances. Sections 2-501–2-503, packet pp. 23–32.

The crucial limit: Section 2-501(f) preserves a constitutional officer’s operational decision to search, request, receive, analyze or use lawfully available information from another entity’s system. Ordinary use of county offices, personnel or computers does not alone become prohibited system support. Section 2-516 separately preserves specified lawful information uses, subject to limits on the jurisdiction’s ownership, funding, operation or contribution of local surveillance data. Section 2-501(e)–(f), p. 23; Section 2-516, p. 41.

The text also disclaims control over municipal or SCDOT rights-of-way where the county lacks authority and protects payments unconditionally required by law or specified binding obligations. Therefore, “county ban” is not evidence that every reader within county boundaries stopped, or that all outside-system searches became unlawful. Applying the provisions to a particular arrangement requires the final text, ownership, funding, location and configuration records.

Camera counts and locations: five, six, or a broader network?

Sources: FOX Carolina; sheriff portal; FITSNews; official vehicle-theft release.

These figures describe different scopes and dates. Adding them without reconciling ownership and duplicates would manufacture certainty. We found no complete, verified installation-and-removal map in the materials reviewed. The historical highway reference is included because the sheriff published it; it is not a map of currently operating cameras.

The decisive records would be an asset list with camera identifiers, owner and funding source; installation authorizations; vendor account inventory; disablement dates; and removal confirmations. A county-owned pole, a municipal subscription and a private camera sharing data may involve different responsibilities.

Taxpayer costs: $55,000 in identified county payments

The county’s check registers provide stronger evidence of actual listed payments than an estimate obtained by multiplying a reported camera count by a reported annual rate.

The first five entries use the county’s data-processing account; the $350 entry uses equipment maintenance. The vendor identifier shown is 86133. An account label does not establish the number of devices purchased or the exact service period.

What remains unresolved: executed contracts and amendments; individual invoices; renewal dates and escalators; grants or other funding sources; 2026 payments; refunds, credits and termination costs; and spending by municipalities or private owners. This review is not a complete reconciliation of the county ledger.

Reported rates conflict: FITSNews described $3,000 per sheriff camera annually, while Public Radio reported $5,000. Neither estimate should replace the payment table or an invoice. FITSNews, August 25; Public Radio, September 16.

A September 18 WRDW report, carrying FOX Carolina reporting, described a procurement termination notice covering an initial four cameras plus a fifth, with a $500 removal charge per camera. That is a reported $2,500 charge, not a verified payment in our subtotal. We have not independently obtained the executed notice, final invoice or proof of payment. WRDW, September 18.

Municipal systems: separate the towns and the evidence

Municipal boundaries do not answer whether a department owns a reader, can search another agency’s data or remains eligible for discretionary county funding. Each question requires its own evidence.

For additional context, Salem’s mayor/council and police chief supplied August 31 letters denying ownership, leasing, maintenance or vendor contracts. The police response also denied requesting related searches or entries from other agencies during the requested period. Packet, pp. 289–290.

Seneca’s response deserves precision. Chief Casey Bowling offered agreements, monthly audit records, invoices/funding records and sharing correspondence. For unredacted organization/network logs, the city sought written assurances restricting county use and further disclosure, with an opportunity to redact and county-paid redaction costs. The letter invokes a law-enforcement exemption. It documents a proposed production arrangement, not proof that records were delivered, and this article does not adjudicate the exemption’s legal validity. September 10 email.

No reviewed final administrative determination establishes that a named municipality violated the ordinance. Continued searching alone would not resolve that question given the ordinance’s information-use provisions.

What is retained, and what the portals actually disclose

The sheriff, Seneca and Westminster portals each displayed 30-day retention when inspected October 14. Their descriptions focus on vehicle and plate information and say the system is not facial recognition. That describes the presented Flock deployment, not every technology the ordinance addresses. Sheriff portal; Seneca portal; Westminster portal.

Do not confuse a retention rule for routine vehicle observations with retention of exported case evidence, query/audit logs, a legal hold or a copy held elsewhere. The sheriff portal says access requires a valid reason and describes access records as stored indefinitely. The agency’s controlling policy and vendor agreement are needed to resolve those distinct record categories.

Flock’s September 2026 privacy announcement describes a seven-day default for new law-enforcement customers. It should not be substituted for the 30-day settings displayed by these local portals. Vendor announcements describe product policy; local settings and contracts establish local implementation. Flock’s privacy update.

The portals’ headline metrics are rolling windows. Camera counts, searches, vehicle detections and hotlist hits are different measures. A hit is not a conviction, and a search is not a newly installed camera.

Outside-agency access: the missing direction of the data

The sheriff portal’s three exported search rows were dated September 14–15 in UTC. The last was 02:35 UTC on September 15, or 10:35 p.m. Eastern on September 14: all three preceded the September 15 evening vote. The rows therefore do not prove post-ban sheriff searching. Sheriff portal, public search export inspected October 14.

Two rows show large values in a field named networkCount: 1,005 and 989; another shows 1. Those are export fields, not local camera totals. Without the vendor’s data dictionary and full logs, they do not identify the agencies involved or prove which outside agency could access Oconee observations.

There are at least three separate questions: what Oconee personnel searched elsewhere; who could search locally collected data; and whether someone asked another agency to run a search. A public outward-search list cannot answer all three.

The missing evidence is the historical sharing roster, changes to permissions and nationwide/statewide lookup settings, organization and network audit exports, cross-agency requests and the applicable agreements. Current public portal descriptions do not establish the full historical sharing configuration. They also do not establish that all sharing ended when a camera was removed.

Search controls and the audit trail Council requested

The inspected portals describe purpose restrictions, including prohibitions on personal use, harassment and immigration enforcement. Those published restrictions are relevant evidence of stated rules; they are not proof that every user complied.

FITSNews reported a sheriff’s process in which captains review searches monthly and seek a supplemental explanation within three days when the case or vehicle connection is unclear. We treat that as the sheriff’s reported practice, not an independently audited finding. The written policy, completed reviews, exception follow-ups and corrective-action records would show how the process operated. August 25 report.

On August 26, Council unanimously sought preservation of organization/network audit logs for the account’s life, sharing and configuration history, user permissions, hotlists and alerts, and written clarification of retention and exportability after termination. It also sought monthly audits, financial records and related correspondence. Special-meeting minutes, pp. 3–5.

That specificity matters: a short public CSV is not the complete audit. Seneca’s public export obscures user identifiers and does not supply the same reason/case fields shown in the sheriff’s export. It cannot independently resolve the justification for each search. This investigation does not republish personal search targets or infer misconduct from redactions.

Federal agencies and ICE: what is documented, what is not

There is a documented local ICE program, but no demonstrated ALPR connection in the records reviewed. The sheriff’s August 29, 2025 announcement describes a detention-center Warrant Service Officer arrangement under 287(g). It does not establish that ICE had a Flock login, received an Oconee plate-search export or queried an Oconee camera. Sheriff’s official announcement; our separate ICE / 287(g) records guide. Read the full ICE / 287(g) investigation for the signed agreement, reported activity, costs and oversight requirements.

At the national vendor level, Flock says it has no ICE contract and describes federal sharing as an agency-controlled choice with default-off settings. The same vendor account acknowledges Homeland Security Investigations and Customs and Border Protection pilots that ended in 2025, and an earlier FBI pilot. HSI is part of ICE, so a general “no ICE contract” statement must not be expanded into a claim that Flock never had any federal or ICE-component involvement. These are vendor disclosures about national programs, not proof of Oconee participation. Flock’s account of ICE, federal sharing and pilots.

The three local portals’ stated prohibition on immigration enforcement is relevant, but cannot by itself prove the absence of an indirect request, an earlier setting or an unauthorized use. Equally, the existence of 287(g), a large networkCount value or a national pilot cannot prove such use occurred locally.

The accurate finding is limited: we did not find a reviewed local record establishing direct ICE access or a specific ICE search of Oconee data. To resolve the question, obtain dated agency-sharing lists, federal access approvals, audit events, exports and correspondence concerning ICE, HSI, CBP or other federal requests. No finding of unlawful federal access is made here.

The records still worth requesting

These are proposed, focused reporting requests. Worth Fighting has not submitted them for this publication, and no response deadline is being represented as missed.

For practical instructions and the correct office, use the Oconee FOIA guide. A custodian may hold responsive records that were not located in this review. Nonpublication is not concealment, and a lawful redaction is not proof of improper conduct.

Methodology and documents reviewed

Last verified: October 14, 2026 (Eastern time). This is a public-document investigation, not a forensic audit, an on-site camera survey or a determination of legal liability. No new interviews or records requests were conducted. Official statements and reported responses are linked where used.

Council documents: August 18, August 26 special, September 1 and September 15 minutes; September 15 amended backup packet. Important packet locators: ordinance text pp. 19–50; constitutional-officer information-use provision p. 23; capability definition p. 29; savings/limits p. 41; unsigned adoption fields p. 50; Seneca response pp. 287–288; Salem letters pp. 289–290; Walhalla letter p. 291. Page numbers refer to PDF pages, not the ordinance’s internal numbering. Scanned municipal letters were read visually.

Financial documents: county registers for June 2022, August 2023, June 2024, July 2025 and September 2025. We identified six FLOCK SAFETY entries and added their face amounts. We did not review every month or reconcile invoices, bank clearances, credits or all related payees.

Public systems: sheriff, Seneca and Westminster Flock transparency pages and their public search CSV exports, inspected October 14. Each page displayed that date as its update date. Our count compares exported timestamps with the September 15 evening vote; the sheriff’s UTC timestamps were checked against Eastern time. These rolling exports are partial disclosures, not complete historical logs.

Other material: the sheriff’s two investigative releases and WSO announcement; Flock’s federal-sharing and privacy statements; attributed reporting from FOX Carolina/WRDW, South Carolina Public Radio and FITSNews. Vendor statements are identified as such.

Conflicts resolved or preserved: the final minutes record 4–1, despite a Public Radio account describing the final vote as unanimous. Walhalla’s actual letter takes precedence over a general report grouping it with camera users. The five-versus-six sheriff camera count and conflicting annual prices remain unresolved. Missing contracts and a signed final ordinance are explicitly identified.

Update policy: this first edition is dated October 14, 2026. Material new records or corrections should be accompanied by the original source and date. See our corrections policy or contact Worth Fighting.

Frequently asked questions

Did Oconee County ban Flock cameras in 2026?

Council adopted Ordinance 2026-26 on September 15, 2026, by 4–1, with John Elliott opposed. The measure restricts prohibited surveillance systems through county resources, property and discretionary funding. The meeting-packet text preserves specified lawful uses of information from other entities; it does not establish that every ALPR inside the county stopped operating.

How many Flock cameras did the sheriff use?

Contemporary reporting described five sheriff cameras. The sheriff’s public portal displayed six on October 14, 2026. These are different dated records, not a reconciled inventory. Removal confirmations, serial-number inventories and contracts are still needed to establish the final physical count.

How much did Oconee County pay Flock?

Six identified county check-register payments from June 2022 through September 2025 total $55,000. That is a partial documented subtotal, not the lifetime program cost. The reviewed records do not resolve all invoices, renewals, credits, municipal spending or termination charges.

Are municipal ALPR systems still being used?

Seneca and Westminster public portal exports contained searches after the September 15 vote, through October 7, 2026. Their portals each displayed four cameras. That supports continued system use, not proof that every camera was active. Walhalla’s September 8 letter reported no listed ALPR agreements, searches, funding or sharing correspondence. West Union remains unverified.

Does the evidence prove that ICE accessed Oconee Flock data?

No local record reviewed establishes direct ICE access or a particular ICE query of Oconee data. That is a limit of this review, not proof that access never occurred. The detention-center 287(g) program is separately documented and is not itself evidence of an ALPR data-sharing connection.

Does a 30-day retention rule mean all information disappears?

The three inspected local portals state 30-day vehicle-data retention. That does not establish how separately exported evidence, audit logs, legal holds or copies received by another agency are retained. Those questions require the applicable policies, agreements and preservation records.

Continue through the Oconee record

Return to Investigations & Public Records or the Oconee County hub. Related coverage: ICE / 287(g), school board and parental rights, Republican resources, Council votes, public-records library and meetings and public comment.

Next investigation: government transparency and public records

Our six-agency Oconee transparency scorecard examines meeting access, public-records procedures, fees, contracts, budgets and disclosure records. Its 14 criteria separate verified evidence from partial or unverified findings. Last verified October 14, 2026.

Next investigation: economic-development incentives and taxpayer commitments

Read the Oconee County economic-development incentives investigation for company promises, verified outcomes, tax-credit and grant terms, public land and infrastructure spending, and the records needed to complete the accounting. Last verified October 15, 2026.

Follow county spending from approval to payment

Read the Oconee County spending and procurement investigation for major contracts, consultants, outside legal bills, competing bids, sole-source explanations, renewals and documented accounting-control weaknesses. Contract authorizations and actual payments are reported separately. Last verified October 15, 2026.

Follow road repairs, paving priorities and maintenance costs

Read the Oconee County road repairs and paving investigation for the 31-road tentative paving list, competing bids, road and bridge budgets, selected payments, road-acceptance decisions, and the records needed to verify completion. Last verified October 15, 2026.

Follow subdivision approvals and infrastructure costs

Read the Oconee County growth and development investigation for the 2026 subdivision moratorium, Armstrong Road utility votes, proposed road warranties, timeline, primary documents and unresolved infrastructure costs. Last verified October 16, 2026.