THE QUICK TAKE
  • Milford's Board of Aldermen confirmed by NBC Connecticut and WTNH voted on October 5–6, 2026 to pause — not terminate — its Flock Condor camera program pending an independent committee review.
  • On the same night, South Windsor's Town Council voted to fully remove its Flock cameras, with Mayor Craig Zimmerman saying all data would be purged and devices removed within roughly 30 days, per WTNH.
  • A September 2026 incident in which a hacker collective physically removed a Flock ALPR camera and reportedly accessed over one million surveillance images, per Aviatrix AI research and Hoodline, helped accelerate the statewide backlash.

What Folks Are Saying: The Votes That Rattled the Hen House

Well, butter my biscuit and call it a city council meeting — Milford, Connecticut's Board of Aldermen went and voted on the night of October 5, 2026 to pump the brakes on its Flock Safety Condor camera program, according to both NBC Connecticut and WTNH News 8. The board chose to send the matter to an independent review committee rather than voting to keep or yank the cameras entirely — sort of like deciding not to shoot the dog or pet it, but locking it in the barn while you think it over.

According to WTNH, the Milford pause specifically targets Flock's Condor cameras — pan-tilt-zoom capable devices that Flock Safety describes as offering human-tracking and license plate reading functions — while existing border ALPR cameras were reportedly left running. That distinction matters about as much as the difference between a hunting dog and a lapdog when both are sleeping on your good couch.

On that very same October 5–6 night, WTNH also reported that the South Windsor Town Council voted to go a full step further and remove its Flock cameras altogether, with Mayor Craig Zimmerman stating that data would be purged and all cameras pulled down within approximately 30 days. Two towns, one night, both telling Flock Safety's gear to pack its bags — that ain't a coincidence, that's a stampede.

What We Actually Know: The Confirmed Civic Record

The Milford vote is confirmed independently by NBC Connecticut and WTNH News 8, two separate local TV news outlets with no affiliation with each other or with Flock Safety. The South Windsor removal vote is confirmed by WTNH via Yahoo News. These are not rumors floating around the feed store — these are documented civic actions.

The broader Connecticut municipal backlash is a matter of confirmed public record as well. According to Government Technology and WTNH, Windsor ended its Flock contract after a 5–4 council vote in July 2026, and Killingworth opted not to renew its own deal, making them the first two Connecticut towns to fully terminate Flock contracts. CT Mirror, a nonprofit state news outlet, has been tracking the statewide unease since at least August 2026.

Connecticut's legislature also passed a law in 2026 — confirmed by both CT Mirror and Government Technology — requiring that ALPR data be deleted after 21 days and prohibiting police from handing it over to federal law enforcement without a warrant. The law also limits interstate data sharing to Massachusetts, New York, and Rhode Island under specific conditions. That's the state putting up a fence around its hog pen, legally speaking.

The Breach That Broke the Fence Rail

Here's where things get uglier than a mud-caked boot at a Sunday service. According to Aviatrix AI threat research, corroborated by a Hoodline report citing CBS News New York, a hacker collective in September 2026 physically removed a Flock ALPR camera, exploited encryption keys stored on an unencrypted partition, and accessed more than one million surveillance images — subsequently sharing the material with 404 Media and WIRED. Aviatrix AI describes this as exposing what it calls critical security flaws in widely deployed surveillance infrastructure.

That was not the first time Flock Safety's camera network showed its underbelly. According to WFLX, a January 2026 incident involved live Flock Condor camera feeds being exposed to the open internet. Flock Safety, in an email obtained through a public records request per WFLX, attributed the exposure to a cellular carrier compatibility test and characterized it as — and this is the company's own phrasing — 'a limited, isolated configuration issue' that was corrected. Privacy researchers and municipal officials, for their part, cited it as evidence of something a good deal more systemic.

Security researchers also disclosed more than 50 vulnerabilities in Flock Safety cameras as of mid-2026, including hardcoded passwords and API key exposures, leading to 22 CVEs being published, according to SimeonOnSecurity. Flock Safety's initial response, per that report, disputed the severity of the findings — which is a little like arguing about whether the barn door was really that open after the horses are already halfway to Nashville.

What Remains Unverified: The Smoke Without a Full Fire Report

The full scope of the September 2026 physical camera hack — specifically how many jurisdictions had data exposed — has not been independently audited. The account rests primarily on materials the hacker collective shared with journalists. Aviatrix AI and Hoodline have reported on it, and CBS News New York covered the breach, but a comprehensive third-party forensic accounting of the damage has not been publicly released as of this writing.

Flock Safety's characterization of its data-sharing practices also remains in active dispute. According to Malwarebytes, Mountain View, California pulled its entire Flock ALPR network in February 2026 after discovering the company had been sharing city data with hundreds of law enforcement agencies — including federal ones — without the city's authorization. Flock Safety has not publicly reconciled that finding with its stated contractual commitments, and that gap remains an open sore.

Senator Chuck Schumer publicly demanded that Flock Safety delete personal data and fully disclose the extent of federal access to its camera network, per a Hoodline report published October 5, 2026. Whether Flock Safety has responded substantively to that demand is not confirmed in the available sourcing. The outcome of Milford's independent review committee is also entirely unknown at this stage.

Analysis: A Reckoning That Ain't Finished Cooking

This is analysis, not settled reporting: what's happening in Connecticut looks less like a few towns having second thoughts and more like a structural crisis of municipal trust in a surveillance vendor. When you've got a documented physical breach, a separate internet-exposure incident the company called 'isolated,' confirmed unauthorized federal data-sharing, 50-plus disclosed security vulnerabilities, a sitting U.S. Senator demanding answers, and now multiple town councils voting on the same night in the same state — that's not a weather pattern, that's a tornado warning.

The disagreements within communities are real and worth noting. Windsor's mayor, per Government Technology, acknowledged that the cameras are effective at solving crimes and recovering stolen vehicles — but concluded Flock could not guarantee resident data privacy. That tension — cameras that genuinely work versus a vendor that apparently can't lock its own barn — is the core dispute that different municipalities are resolving differently. Milford chose the middle road: pause and review. South Windsor chose the exit. Windsor and Killingworth already left.

The analytical question hanging over all of this like humidity in August: if Milford's independent review committee finds the concerns valid, does the pause become a permanent removal? And if it does, how many other Connecticut towns — or towns elsewhere in the country — are watching this process like a dog watching a screen door? That outcome remains genuinely unknown, and anyone telling you different is selling something.

Who is doing the hollering

These links show where the chatter came from. A link is attribution, not our endorsement or independent confirmation.

  1. Milford considers pausing more Flock cameras amid surveillance concerns; data breachNBC Connecticut · top tier
  2. Milford board decides to pause usage of Flock security camerasWTNH News 8 · top tier
  3. Milford's Board of Aldermen temporarily stops use of Flock security cameras, awaiting reviewWTNH News 8 · top tier
  4. South Windsor votes to remove Flock camerasWTNH / Yahoo News · top tier
  5. Flock cameras have CT up in arms as towns scramble to respondCT Mirror · specialist
  6. Why Two Connecticut Towns Are Removing License Plate CamerasGovernment Technology · specialist
  7. Some Connecticut towns opting to turn off automated license plate reader cameras amid privacy concernsWTNH News 8 · top tier
  8. Flock Safety Camera Breach Exposes Critical Flaws in Smart City Surveillance SecurityAviatrix AI Threat Research · specialist
  9. Schumer Demands Flock Safety Delete Personal DataHoodline · specialist
  10. Flock Safety exposed live police camera feeds in internet data breach, company saysWFLX / WPTV · top tier
  11. Flock cameras shared license plate data without permissionMalwarebytes · specialist
  12. Flock Safety Camera Vulnerabilities: 50+ Flaws FoundSimeonOnSecurity · specialist
Revision record

Last checked Oct 6, 2026, 9:07 AM EDT. Talk Around Town: The exact scope of the September 2026 physical camera hack — including how many jurisdictions' data was exposed — has not been independently audited and is based primarily on materials shared with media by the hacker collective. Flock Safety's characterization of its data-sharing policies conflicts with findings by multiple municipalities. Milford's pause is not a termination; the independent review committee's outcome is unknown.