Documented Incident

LegislationPrivacyData SharingInvestigationsWest Virginia

West Virginia House committee sets Friday deadline for Flock Safety to answer written questions

Members of the West Virginia House Committee on Government Organization sent Flock Safety a letter dated Oct. 5, 2026, giving the company until Friday to supply written answers to 19 questions first posed in an Aug. 14, 2026 letter, and said they may turn to subpoenas or compelled testimony if the answers are not satisfactory. Flock's chief legal officer, Dan Haley, replied with a 10-page letter on Sept. 1 that addressed the five question categories broadly; lawmakers wrote on Sept. 3 that many responses were insufficient, particularly regarding unauthorized access to raw video footage. Flock offered to brief the committee, but the lawmakers said a closed-door briefing is not an acceptable substitute for public written answers. Delegate Tristan Leavitt, R-Kanawha, said legislation on the technology will be introduced in the 2027 session, which begins in January.

Why this matters

The exchange tests whether a state legislature can obtain detailed, public answers from a surveillance vendor before writing rules governing its use, and the committee's stated willingness to consider subpoenas could set a template for oversight efforts elsewhere.

Key facts

Timeline

Sources

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

More from West Virginia

Everything we have documented in West Virginia, or search every West Virginia 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 October 10, 2026. Corrections: blockflock@bytebunny.io. See all documented incidents or search the full article archive.