A college in Illinois tried to cancel its Flock contact and it refused

Elgin Community College spent months trying to get six Flock Safety cameras removed from its Illinois campus after administrators lost confidence in the system’s handling of surveillance data. The school eventually covered the devices itself to prevent them from recording, but the covers were repeatedly taken off by workers arriving in an unmarked vehicle. The dispute did not end until the agreement ran out in April, when Flock removed the cameras.

The cameras had been installed in April 2025. At the time, the college said the equipment was intended to strengthen security for students. The devices were Flock safety cameras, a type of networked camera associated with vehicle and license-plate monitoring. Their arrival reflected a familiar campus-security calculation: whether collecting more visual information can help institutions respond to possible threats and investigate incidents.

Within months, however, college leaders’ assessment had changed. By September 2025, the administration had raised concerns about reports that Flock data was being shared with Customs and Border Patrol. Officials were also troubled by the protection of camera feeds and by what they viewed as misuse of access by both law-enforcement users and Flock employees. Those concerns shifted the issue from the value of the cameras to control over the information they produced.

In October, the college asked Flock to take the equipment down. College President Peggy Heinrich said the company declined, maintaining that it had not breached the contract. The disagreement was therefore not simply over whether the cameras should remain useful to the school; it became a dispute over whether the customer could end their on-campus operation before the contract’s scheduled conclusion.

Elgin made another attempt in December, according to the Chicago Sun-Times. School officials offered to pay the balance for the five months left on the agreement while again asking for removal of the equipment. That proposal sought to separate payment from use: the college was willing to meet the remaining financial obligation but no longer wanted active cameras at its campus. The school said it did not receive a reply to that request.

With the cameras still in place, college employees began placing black garbage bags over them and fastening the coverings with zip ties. The purpose was practical: block the devices from gathering footage while the contractual dispute remained unresolved. Heinrich said the coverings did not stay in place. Workers who arrived in an unidentified vehicle, whom she believed were connected to Flock, repeatedly removed them during service visits.

That created an unusual physical standoff around infrastructure the college had sought to discontinue. Staff would obscure the cameras, and the coverings would later be removed; the cycle continued for a period, according to Heinrich. The episode illustrates how a disagreement over data governance can become a question of access to hardware on a customer’s property when a service provider and an institution interpret their responsibilities differently.

Flock’s position, as described by the college, was that it had complied with its contractual duties. Elgin’s position was driven by concerns about sharing, security, and improper access to surveillance data. The available account does not resolve the underlying contractual terms or independently establish the extent of the alleged access problems. It does show the competing priorities at stake: a vendor’s view of an ongoing agreement and a school’s decision that its privacy and security worries outweighed the original rationale for the cameras.

The immediate conflict ended when the contract expired in April and Flock took the six cameras away. What remains to watch is whether institutions that use connected surveillance systems will seek clearer cancellation provisions, removal procedures, and rules governing who can view or share the data. For colleges and other public-facing organizations, the case underscores that approving a security product is only one part of oversight; the terms for limiting or ending its use can matter just as much.

Source: The Verge