A contract dispute over campus cameras
Elgin Community College in Illinois tried to have Flock Safety cameras removed from its campus after raising concerns about data sharing, security and access to the footage. According to reporting summarized by The Verge, Flock declined the request and the disagreement escalated into a physical back-and-forth over cameras the college had attempted to cover.
The episode is a narrow dispute involving one school and one surveillance-camera provider, but it illustrates a broader issue for organizations adopting connected security systems: ending a service can be more complicated than deciding not to use the data it generates.
Elgin Community College had six Flock cameras installed in April 2025. The school said the purpose was to enhance the safety and security of students. By September, however, the administration had become concerned about reports that Flock was sharing data with Customs and Border Patrol, about whether camera feeds were properly secured, and about access to the data by law enforcement and company employees.
The effort to remove the cameras
College President Peggy Heinrich said the institution asked Flock in October 2025 to remove the equipment. Flock rejected the request, according to Heinrich, on the basis that it had not violated the contract.
The college contacted the company again in December, according to the account. It offered to pay for the remaining five months of the contract while again requesting removal of the cameras. The school said it received no response to that request.
That left the college with hardware on its property that it no longer wanted operating. Staff began covering the cameras with black trash bags and zip ties to prevent them from capturing footage, Heinrich said. But workers in an unmarked vehicle, whom she assumed were associated with Flock, repeatedly removed the coverings when they came to service the equipment.
The reported sequence is notable because it moves the disagreement beyond billing or software access. A school that wished to stop collection of footage found itself trying to block the physical devices, while the provider continued to maintain them. The cameras became the visible focus of an unresolved question: who determines whether an installed surveillance system remains active when the customer wants it shut down?
Data access was at the center
Flock Safety’s systems are associated with camera networks and license-plate recognition. The college’s concerns, as described in the report, were not limited to the presence of cameras. They included how data could be shared, how securely feeds were handled, and how access might be used by law enforcement or company personnel.
Those concerns matter because surveillance systems do not end at the lens. They also involve storage, search, access controls, data-sharing arrangements and the rules governing how footage is used. Institutions considering such technology may focus first on installation and safety goals, yet the operational terms governing data and equipment can become just as consequential later.
The case also underscores the importance of contract terms. Flock’s stated position, as relayed by the college, was that it had not violated its agreement. The college’s position was that it wanted the cameras removed, even after offering to pay the balance of the contract. The supplied reporting does not establish the contract’s full terms or resolve the parties’ competing interpretations. It does show how a disagreement over those terms can affect a campus in practical ways.
Why the case matters beyond one campus
Educational institutions are often expected to balance security, privacy and community trust. A decision to install cameras can be presented as a safety measure; a later decision to remove them can reflect concern about the system’s wider consequences. Elgin’s experience suggests that governance should account for both stages before a system is deployed.
Questions worth settling in advance include who controls activation and removal of the devices, whether a customer can require a service to stop collecting data before a contract expires, and what happens to equipment during a dispute. Clear answers could reduce the risk that an organization which no longer wants surveillance operating is left improvising with physical covers.
The case also demonstrates why transparency is important when institutions use technology that affects large groups of people. Students, staff and visitors may reasonably care not only about whether cameras are present, but also about who can access the resulting information and under what conditions it can be shared.
For Elgin Community College, the conflict began with a request to remove six cameras intended for campus safety. It developed into a dispute about contract obligations, physical control of the devices and the handling of surveillance data. Whatever the eventual resolution, the episode offers a concrete warning for organizations: procurement decisions for connected safety systems should include a credible plan for withdrawal, oversight and control.
This article is based on reporting by The Verge. Read the original article.
Originally published on theverge.com
