Flock Exposed - Unauthorized Activation
Features or data access turned on, expanded, or restored without local board authorization - Flock, Motorola, and other surveillance vendors.
Compiled September 15, 2026, expanded September 16, 2026 - all items sourced to published reporting, company materials, litigation filings, or official government findings. Scope: this page covers documented cases of a vendor turning on, expanding, or restoring a feature or data-sharing capability without local board authorization, on equipment the town already knew it had - and a vendor's ability to remotely control that equipment regardless of what a local contract says. For cases of surveillance hardware physically installed without authorization, see the companion page "Unauthorized Installations." This document is not limited to Flock - Motorola Solutions is included below.
Mountain View, California - a "nationwide" search feature turned on without permission
The city of Mountain View found that from August to November 2024, federal agencies searched Mountain View's camera data using Flock's "nationwide" search feature - a feature Flock activated without Mountain View Police Department's permission. This led Silicon Valley cities including Mountain View and Santa Clara to ban Flock outright.
Source: State of Surveillance, "Silicon Valley Just Banned Flock Safety," 2026
Boston, Massachusetts - nationwide data sharing enabled during a pilot, without city approval
Reporting confirmed that Flock enabled nationwide data sharing during a pilot program the prior year, without Boston's approval - meaning the data-sharing scope was expanded by Flock's own action, not by any decision Boston's government made.
Source: Boston Globe, September 14, 2026
Menominee, Michigan - cameras switched on before any council vote
City leaders in Menominee voted unanimously to cancel their Flock arrangement after cameras were reportedly activated without city council approval. Local officials said they did not know where the collected information was going or how the system had been turned on before receiving formal authorization.
Source: Newsweek; Techdirt, August 13, 2026
Pflugerville, Texas - hundreds of agencies with access nobody approved
A public records request in Pflugerville, Texas revealed that nearly 380 unauthorized agencies had access to Pflugerville's Flock system and residents' personal information, well beyond those the city itself had approved. The city shut down and covered its 28 cameras before its council meeting and ultimately cut ties with Flock.
Source: CBS Austin, 2026
Littleton, Massachusetts - cameras switched back on after the town voted to shut them down
Officials in the town of Littleton, Massachusetts voted in May to shut down six Flock cameras on public roads. Police then discovered Flock had restored power to the cameras without notifying the town - proof that a local vote to disable the system is not the same as the system actually being disabled, since the switch is not in the town's hands.
Source: Boston Globe, "Littleton shut down Flock surveillance cameras on public roads. Without telling the town, Flock turned them back on," August 6, 2026; Techdirt, "Flock (Again!) Activates A Camera System A Town Had Voted To Shut Down," August 13, 2026
Flock has stated, in its own words, that it can shut cameras off remotely at any time
In a dispute where a town wanted cameras removed, Flock stated that the cameras could be remotely deactivated at any time and that they were not operating during the period they remained installed. This is a direct company admission that operational control of installed hardware rests with Flock, centrally, not with the town where the camera physically sits - and the same remote switch that turns equipment off necessarily means the company can turn capabilities on the same way.
Source: Wikipedia (Flock Safety), citing reporting on a camera-removal dispute
Motorola Solutions - license plate data allegedly routed to federal agencies beyond what Illinois authorized
A proposed class action, Rojas et al. v. Motorola Solutions, Inc., filed May 27, 2026, alleges Motorola "actively" shared driver location data captured through its Automated License Plate Reader (Vigilant) system with federal agencies - including Customs and Border Protection, IRS Criminal Investigation, the U.S. Marshals Service, the Bureau of Indian Affairs, and the U.S. Secret Service. Ron's home state of Illinois separately bars ALPR data sharing for immigration enforcement - this suit alleges Motorola's own system moved data to exactly the kind of federal agencies local boards were told would not have access.
Source: Rojas et al. v. Motorola Solutions, Inc. class action complaint, filed May 27, 2026; this is a legal allegation, not yet a court finding
Motorola Solutions - a second suit says an April 2026 audit caught the same pattern under California law
A related class action alleges the same Motorola/Vigilant data pipeline sent license plate data to CBP, IRS Criminal Investigation, the U.S. Marshals Service, the Bureau of Indian Affairs, and the Secret Service in violation of a California law that restricts ALPR data sharing to state and local law enforcement only, excluding federal agencies. The suit states an April 2026 audit is what revealed the prohibited data pipeline had been operating. This is the closest documented parallel to Flock's own "nationwide search enabled without permission" pattern, applied to a competing vendor.
Source: Class Action U, reporting on Motorola Solutions ALPR privacy class action, 2026; complaint allegations, not a court ruling
Palo Alto, California - plate data searchable nationwide without the city ever being told
Palo Alto discovered that its camera data was appearing in search results run by law enforcement agencies in Mississippi, Illinois, and dozens of other states, even though the city had never authorized nationwide sharing. Flock Safety had quietly enabled a national lookup feature that made Palo Alto's data discoverable by outside agencies without notifying the city at all.
Source: Palo Alto Ledger, "All 50 states searched Palo Alto plate data without city knowing," 2026
Ventura County, California - a feature the Sheriff's Office had turned off three years earlier reactivated itself, generating 364,000 unauthorized accesses
The Ventura County Sheriff's Office had disabled Flock's "National Lookup" feature back in June 2023 specifically to comply with a California law barring local agencies from sharing ALPR data with out-of-state and federal law enforcement. A subsequent audit found that from February 19 to March 19, 2025, out-of-state agencies queried the county's data more than 364,000 times despite that feature having been switched off years earlier - the sheriff's office said it did not know the reactivation had happened until the audit uncovered it.
Source: CBS News Los Angeles, "Flock license plate readers shared data with out-of-state agencies, Ventura County audit finds," 2026; edhat.com, "Oxnard police suspend Flock license-plate readers; Ventura agencies tighten controls after out-of-state access," 2026
Oxnard, California - the identical reactivation problem hit the city next door, forcing a full camera shutdown
Just south of Ventura County's discovery, the Oxnard Police Department found that despite setting its own system's access to "California only," a "vendor-based issue" had silently re-enabled a nationwide query feature, giving outside agencies access without the department's knowledge or approval. Oxnard responded by suspending all 19 of its fixed Flock cameras on February 27, 2026, and Ventura-area agencies added daily verification checks afterward to catch any future silent reactivation before it could run for weeks undetected again.
Source: City of Oxnard Police Department news release, February 27, 2026; edhat.com, "Oxnard police suspend Flock license-plate readers; Ventura agencies tighten controls after out-of-state access," 2026; TechTimes, "Flock Safety Crosses 100,000 Cameras as 53 Cities Cancel Over Unauthorized Federal Data Access," June 29, 2026
Eugene, Oregon - a camera kept tracking vehicles for weeks after the city ordered a citywide pause
Eugene ordered a citywide pause on its Flock license plate readers in October 2025, but data later showed a Flock camera continued tracking vehicles for several weeks after that order, operating despite the pause. Eugene Police Chief Chris Skinner confirmed the camera had been turned on after the city ordered the cameras shut down, and said the inadvertent activation is what led him to terminate the city's contract with Flock entirely; Eugene had physically removed most of its cameras by mid-December 2025.
Source: KLCC, "Eugene Police confirms Flock camera was turned on after city ordered the cameras to be shut down," December 9, 2025; KLCC, "Data shows Flock tracked Eugene vehicles weeks after the city asked it to stop," December 8, 2025; Lookout Eugene-Springfield, "Flock activated camera during 'pause,' chief says, pushing city to axe contract"
Renton, Washington - police reactivated cameras without telling even their own city council
Renton Police reactivated the city's Flock cameras in April 2026 without issuing any community notice - and without notifying the city council either, according to Councilmember Kim-Khanh Van, which further eroded public trust in the department. The city council responded by voting 4 to 3 on May 4, 2026 to pause the program again, and months later, still without confidence the cameras would stay off on their own, voted 6 to 1 to physically cover them as an added safeguard.
Source: KING 5, "Renton City Council votes to physically cover Flock cameras, first policy in western U.S."; Renton Reporter, "Renton suspends Flock cameras again after public outcry," May 12, 2026
Note on Axon and other vendors:
A focused search on September 15, 2026 did not turn up a specific, well-sourced case of Axon (or its Fusus real-time-crime-center product) activating a feature without a board's knowledge, comparable to the Flock and Motorola items above. One Axon/Fusus example that surfaced - Asheville, North Carolina's access to Buncombe County's 1,800-camera network - was in fact approved by a 4-1 city council vote on January 24, 2026, after a council member pulled it off the consent agenda for discussion; it is included here only as a contrast, not as an unauthorized-activation example. This is flagged as an open research item rather than filled with a weaker or unverified claim.
Questions to Ask Your Town
Does our contract explicitly prohibit the vendor from remotely activating, expanding, or restoring any camera or data-sharing feature without written board approval first?
Who at our department or town receives automatic notice any time the vendor pushes a remote software or feature change to our system?
Has our system's current data-sharing scope - in-state only versus nationwide - been independently audited recently, rather than taken on the vendor's word?
If our board votes to disable a feature or shut cameras off, what written confirmation do we get that it will not be silently reactivated later, and who checks?
Would our board require a public report any time a vendor turns a town-owned camera or data-sharing feature on, off, or back on?
This page will be updated as more factual sources become available.