Flock Safety Offers Employees Incentives to Depart
Flock Safety is encouraging its workforce to leave by launching a voluntary separation program on September 18, as reported by Wired, which obtained an internal email regarding the initiative. Employees interested in this opportunity must apply by October 2. The company expects to accept the majority of applicants, with many set to finalize their departure by October 29. Wired noted that the company did not respond immediately to requests for comment.
The buyout initiative doesn’t automatically signal financial trouble for Flock, but it does provide a mechanism for the company to downsize amid increasing public scrutiny.
Last month, I covered in a piece for Blaze News that various cities had already begun terminating their contracts with Flock, sometimes opting to replace its cameras with those from competing brands. This new development raises further questions about what will happen to the existing cameras and the data they collect once Flock exits these locations.
Local Cameras, Wider Data Access Concerns
Take Boston, for example. Residents there might be particularly wary of official claims about data handling.
According to a report from Ars Technica on September 15, city officials indicated that Flock had allowed nationwide access to data during the early phase of a pilot program in 2025, despite having a contract in place that prohibited such sharing. The city’s surveillance report cited vendor error as the cause, stating that access was revoked once the issue was identified.
Although Boston has moved away from Flock, it’s currently testing other surveillance systems. The cancellation of a contract doesn’t inherently mean fewer cameras will be monitoring the area. Switching suppliers might resolve the immediate contractual challenges, but it doesn’t necessarily enhance the community’s privacy protections.
There are also pressing concerns about the management and oversight of these surveillance searches. For example, an investigation by the Electronic Frontier Foundation revealed unprofessional log entries, including casual terms like “LOL” and “idk,” in places meant to clarify the rationale behind searches. The San Diego County sheriff’s department has claimed these searches were linked to ongoing investigations, but these irregularities complicate accountability. Reviewers ought to be able to justify their search actions clearly, rather than relying on vague acronyms.
Inadequate Search Controls
Flock has announced a new requirement for agencies to select a mandatory offense category when conducting searches. Agencies are encouraged to provide written explanations when they choose “Other.” Flock is touting this update as a means to enhance consistency in audits. But it raises further questions: if an officer opts for a specific crime category, who confirms its relevance to a given investigation? How regularly does the agency review such access? What occurs when a search lacks adequate justification?
These are all crucial inquiries that should be addressed in local councils before any surveillance contracts are renewed. Residents shouldn’t need to be experts in public records to ascertain whether adequate controls exist for the systems they are funding through their taxes.
I understand the necessity of functional investigative tools. However, I think it’s essential for officials to elucidate these constraints and the enforcement mechanisms that accompany them. It’s not enough to assert that access is limited if no one can demonstrate that those limits are being adhered to.
As Flock’s employees ponder their futures, the general public faces a more extended challenge: holding elected officials accountable for the surveillance systems they’ve acquired and whatever replaces a canceled Flock contract.
