· via Hacker News – Front Page (hnrss.org)
Plymouth police chief unplugs Flock cameras after vendor ignores contract cancellation
Plymouth's council voted unanimously to cancel its Flock surveillance contract, but after the vendor stayed silent for over a week, Police Chief Eric Fadden pulled the plugs himself.

What happened
Plymouth's city council voted unanimously in September 2026 to end its contract with Flock, and the city notified the surveillance vendor of the decision right away. According to Tom's Hardware, citing The Drive, more than a week passed with no reply and no sign that the company intended to collect its cameras, which remained in place across the city.
Faced with hardware it had voted out but could not get removed, Plymouth Police Chief Eric Fadden resolved the standoff in the most direct way available: he unplugged the devices, cutting their power so they could no longer operate.
How the situation escalated
The reported sequence is simple and, for anyone who has dealt with vendor relationships, familiar up to a point. A governing body votes to exit a contract. Notice goes out. Then silence. What is unusual is the ending — a police chief going around town disconnecting power cords because the counterparty would not act.
The reporting leaves several questions open: how many cameras were involved, what the contract said about equipment removal, whether Flock ever formally acknowledged the cancellation, and whether the company has responded since the story was published on November 1. Tom's Hardware situates the incident within wider privacy disputes that have followed Flock's surveillance technology, though the report does not detail them.
Hardware outlives the contract
Vendor lock-in is usually told as a software story — export formats, proprietary APIs, subscriptions that renew by default. This case is about equipment mounted on public infrastructure, which raises a different set of questions:
- Who controls a device after a contract ends — the city whose poles it hangs on, or the vendor that installed it?
- Does data collection stop when the agreement is terminated, or only when the hardware is actually powered down or taken away?
- Who is responsible for uninstalling, on what timeline, and who pays for it?
The reporting does not answer these questions for Plymouth, and that gap is itself part of the story. Absent a responsive vendor or an enforceable removal clause, the city's only lever appears to have been physical: pull the plug and make the council's decision real on the street.
Why it matters
For civic technology buyers, the episode is a reminder that exit terms matter as much as deployment terms. Plymouth did everything procedurally correct — a unanimous vote and prompt notice — yet its decision had no practical effect until someone intervened by hand. Contracts for surveillance and networked IoT systems should specify removal deadlines, confirmed data deletion, and remedies the buyer can execute without the vendor's cooperation.
It also shows the leverage that hardware gives a supplier. A city can stop paying an invoice the day a contract lapses, but it cannot un-mount a camera with paperwork. Buyers evaluating camera networks, sensor grids, or any vendor-operated equipment in public spaces may want to negotiate the exit before celebrating the installation — otherwise, as Plymouth demonstrated, enforcement can end up looking like an electrical chore.
- #surveillance
- #vendor-lock-in
- #privacy
- #procurement
- #public-sector