Categories
News ordinances

How We Blocked Flock In Cambridge

Cambridge and Somerville and Boston, as a result of prior work by Digital Fourth, ACLU of MA and others, have “surveillance oversight ordinances” that put procedural hurdles in the way of police adoption of surveillance technologies.

Under these ordinances, for something like Flock Safety, city agencies are legally obliged to disclose to City Council that they are intending to deploy any surveillance technology. They must explain what the technology is; what will happen to the data from it (collection, retention, sharing, destruction); and whether they believe it will have a differential impact on any group within the City. That report must be presented at a public hearing, and the City Council is empowered to say yes or no to the technology.

In the context of this ordinance in Cambridge, unfortunately, a lot depends on who chairs the Public Safety Committee, and how close they are to the cops. We made very little headway in blocking surveillance technologies from January 2023 through to the summer of 2024, because the chair of Public Safety, Paul Toner, was the most powerful Councilor and was very tight with the cops. He waved through anything they asked for. He was very reluctant to schedule separate public hearings for new technologies. In February 2025, therefore, he made sure that Flock would be approved, and the three City Councilors with genuine concerns (including DSA-endorsed Jivan Sobrinho-Wheeler), weren’t able to prevail. We brought six people to give public testimony against it.

At the same time, we were fighting the City on a proposal to allow Cambridge PD to deploy drones. We worked closely with ACLU of MA, and Councilors were worried enough that Toner had to schedule a hearing. At the hearing, we focused on the fact that Cambridge PD hadn’t bothered to develop or disclose a policy on drone use, so whatever they were saying about how drones would or would not be used wasn’t binding. We recommended that Cambridge PD go and draft a policy, consult with us and with ACLU, and bring the policy back to City Council, whereupon City Council would consider whether the proposal to deploy drones was reasonable. Remarkably, City Council agreed, against Toner’s objections. It was a sign of things to come. Over a year later, Cambridge PD has not moved forward with that proposal.

In May through to June, things began to shift regarding Flock. Our national folks monitor surveillance, privacy and Fourth Amendment news very closely. The news broke that Flock had helped a Texas cop chase down a woman suspected of having an abortion. Councilor Sobrinho-Wheeler, responding to that news, filed a policy order for reconsideration of the Flock deployment, backed up by Nolan and Siddiqui. Because we were monitoring the agendas for City meetings in general, we saw that the Pole and Conduit Commission was proposing to approve the actual installation of Flock equipment. We saw an opening, and mobilized to get the Pole and Conduit Commission to delay approval of actual installation till after City Council had considered Sobrinho-Wheeler’s policy order.

Flock had to disclose to that Commission the exact locations where they planned to put in the cameras. That gave our advocacy lots of ammunition. Bad news kept flooding in for Flock Safety, and we made sure City Councilors, the City Manager and the Pole and Conduit Commission members had that information. Then, on July 8, a scandal that had been circulating around City Hall for around a year broke, and Paul Toner announced his future resignation, and was stripped of his committee chairmanships. Toner was replaced as chair of Public Safety by his vice-Chair Angie Wilson. She scheduled consideration of Sobrinho-Wheeler’s policy order for September. We organized speakers for that session. Toner still strenuously objected to revoking Flock’s contract, so it was agreed to suspend it, pending a review by the City Manager. We submitted for this hearing a thorough analysis of where the cameras were to be deployed, because Flock had had to disclose to the Pole and Conduit Commission exactly where they were planning to put them up; we made the argument that the ALPR cameras were heavily focused on East Cambridge in a way that would deeply and differentially affect the residents of public housing complexes in that area.

The review returned to the Council on December 9, and Wilson invited Gideon Epstein of ACLU of MA and Alex Marthews of Digital Fourth to provide expert testimony, like we had done in 2018-21 under Toner’s predecessor. Then, unexpectedly, at the start of the meeting, Cambridge PD and the City Manager’s office recommended revocation of the Flock contract. They had just found out that morning that Flock Safety was in breach of the contract terms. The City had suspended the contract and made very clear that no equipment was to be installed, but a Flock technician had gone ahead and reinstalled two cameras anyway. What with that, and our and ACLU’s expert testimony, and nine out of ten public testimonies being thoroughly opposed to Flock, the writing was finally on the wall. Public Safety Committee recommended revocation, and given the City Manager’s and the police’s posture, it was a given that the full Council would wave through the revocation.

The City Council still preserved, and the City Manager is even now trying to preserve, the underlying City approval for the use of ALPR in general, but now without a specific vendor in mind, and therefore without any specifics on where it would deploy or what the policies would be. The onus is now on the City/Cambridge PD to identify an ALPR vendor that won’t pose significant privacy issues.

Categories
cameras Mission News

Let’s Stop Cambridge From Getting Flocked Up

Recently, Cambridge residents have been receiving communications in their mailboxes that new “Flock Safety” cameras are being installed in their neighborhoods. 

Flock Safety (“Protect Your Community With 24/7 Coverage That Never Sleeps!”) is a surveillance company which produces and installs, among other products, cameras with automatic license plate reader (ALPR) capabilities. Flock is marketed as an all-encompassing “privacy solution […] boosting efficiency and reducing crime” for municipalities.

There are, however, serious privacy concerns with Flock’s systems. Despite months of denying contracts with federal agencies, Flock recently revealed that it has a contract with Customs and Border Patrol (CBP) and shares ALPR data without the consent of local officials. This week, it was also revealed that they had been sharing data with ICE, Homeland Security Investigations, the Secret Service and, for good measure, NCIS. Due to the company sharing data in violation of Illinois law, the state of Illinois recently terminated their contracts with Flock. After Evanston, IL, ordered Flock to shut down its use of ALPR cameras in the city, Flock reinstalled the cameras without permission, prompting Evanston to send a cease-and-desist letter. This week, Eugene, OR, also paused its Flock deployment as a result of privacy concerns.

As other states and municipalities reckon with Flock’s dishonest data sharing policies, Cambridge should take a long look at their own contract. This is the state of play in Greater Boston for now, as far as we know. The City of Boston launched a pilot contract with Flock in 2024, but has not yet, to our knowledge, proceeded to a full rollout. Flock cameras are appearing in Brookline and on the Watertown-Waltham line. Cambridge City Council, at the urging of Cambridge PD and embattled Councilor Paul Toner, approved Flock Safety for use in February 2025, and Flock opened an office in Boston in August 2025. Now, resistance is mounting in the Greater Boston Area due to concerns about data sharing, and Cambridge residents are being confronted with the implications of Flock in their own neighborhoods. 

So far, 16 Flock ALPR camera locations have been proposed in Cambridge (the blue pins):

The densest deployment is planned for East Cambridge, near the public housing at Newtowne Court, Washington Elms and Roosevelt Towers, as well as Kendall Square and MIT. The other proposed locations are on major thoroughfares into and out of Cambridge, including nearly all routes of travel between Cambridge and Boston. This raises the concern that it will become very difficult for local residents to move about without having their license plate information, and thereby in many cases their patterns of life, captured. 

Depending on the city’s contract with Flock relating to data retention, these residents’ patterns of movement may be visible to both the Cambridge Police Department and other agencies using Flock’s database. This is particularly concerning because Flock has developed an AI tool which reports suspicious vehicle movement patterns to local law enforcement. This is to say, artificial intelligence may have a hand in not only assisting police with searching networks for particular crimes or “hits,” but in deciding what is suspicious in the first place and flagging potentially innocent residents based on algorithmically determined criteria. Citizens should not be subject to the whims of an algorithm determined by a private company whose policies are not transparent or subject to the same rigorous checks that a government administration would be. Flock has given Cambridge no reason to trust in the idea that their algorithms are effective and unbiased, and has in fact provided more reason to suspect the contrary. 

There’s a further issue. The City of Cambridge Surveillance Use Policy directs the City to pay attention to whether any communities are being “disproportionately impacted” by the deployment of any surveillance technology, especially “low-income communities, communities of color, or any community that is marginalized in the City.” Based on the proposed camera locations, it’s obvious that the movement patterns of residents of Strawberry Hill and West Cambridge traveling, for instance, to Harvard Square, would not be as regularly captured as would the movements of East Cambridge residents. The City has not considered whether there are disproportionate impacts of this kind; the Council, in approving it, relied simply on a declaration by Cambridge PD that there weren’t any.

A key privacy practice is data minimization: Limiting data collection to the minimum required, and not retaining data for longer than it is required. Flock’s website discloses that the local law enforcement agencies that contract with them may store data themselves, but Flock itself stores all license plate data for 30 days. As a result, in accordance with their data sharing record, Flock data may be visible for a significant window to out-of-state law enforcement, Immigration and Customs Enforcement (ICE), CBP, the Department of Homeland Security, or other federal agencies, either through the pilot data-sharing scheme Flock now claims to have suspended, or through requests by federal agencies to local and state law enforcement who themselves have Flock contracts. 

Federal agencies may also have the opportunity to access Flock ALPR data through the Boston Regional Intelligence Center and through informal favors granted by local members of the Joint Terrorism Task force, which has recently been directed by Trump in a presidential memorandum to conduct investigations of groups which espouse “anti-fascist,” “anti-capitalist,” “anti-American” or “anti-Christian” viewpoints. The actions of the current federal administration make it even more urgent to protect the sensitive data of vulnerable Cambridge residents, including immigrants, politically active people, and those who express views that might be classified under these dangerously loose categories. Anything that requires the use of a car in certain areas of Cambridge has the possibility of being tracked. Whether residents choose to exercise their free speech by attending a protest, accessing reproductive care, or simply moving about, Flock’s license plate readers may be storing that data, exposing it to federal search, and potentially using it to draw conclusions about the vehicle driver’s future potential to commit crimes. For example, many vehicle going into and out of Cambridge Health Alliance’s Windsor Street Care Center, which offers reproductive healthcare services, would be in Flock’s databases.

Data stored is always data that may be used. Any data stored with Flock is not safe. Even if the City of Cambridge specifies that they do not want the ALPR data that they store to be accessed by federal law enforcement, there is no guarantee that Flock will successfully prohibit access by federal law enforcement to their own systems directly in the absence of the consent of the city of Cambridge, especially considering their recent record of lying to cities about their data sharing practices. What’s more, federal agencies can always subpoena Flock. 

We are currently advocating for Cambridge to terminate its arrangement with Flock, along with many other Cambridge residents, local advocacy groups, and MIT professors. As is all too common when it comes to local surveillance technology deployments, notifications on the proposed Flock camera deployments have been relatively under the radar, but progress has been made in the direction of an examination of Flock’s data sharing policies. Recently, all Cambridge city council members voted in favor of taking a second look at the deal with Flock that they approved in February, but it was specified that this review was not expected to result in abandoning the contract altogether.

During this meeting, Councilor Jivan Sobrinho-Wheeler called attention to the funding source for the Flock cameras being deployed in Cambridge. They would be paid for largely by the federal Urban Area Security Initiative (UASI) grant, meaning that Cambridge would technically only be leasing them. This system of funding would place very little control over Flock’s data storage systems in the hands of the Cambridge city council, and potentially open the door to more federal abuses of the type already being perpetrated by Flock in other states. The unexpected, and probably short-term termination of UASI funds by the Trump administration is not expected to change the City’s decision.

Approval of the specific locations for the cameras was included in an agenda for a recent Pole and Conduit committee meeting, but was later removed. The next committee meeting is scheduled for Thursday, October 23, 2025, but it is unclear whether or not Flock will be discussed. 

As the members of the Cambridge City Council and the committee make time for community feedback and consider recent developments with Flock, Cambridge residents have a vital opportunity to make their opinions heard. Cambridge residents should take advantage of their right to free speech by reaching out to their city council members on this topic, all of whom are up for re-election. As informed and engaged members of the community, Cambridge residents should not be willing to accept the creeping spread of civil rights violations associated with the surveillance state.

Note: This article was written with assistance from Digital Fourth volunteers Alex M., Alex T. and Julie B.

Categories
Mission News

Every Car, Everywhere: The DEA Tracks Where & When You Drive

alpr_cartoon

For who-knows-how-many years, the Drug Enforcement Administration has been using Automatic License Plate Recognition software to create a national database of the driving habits of ordinary citizens not suspected of a crime, according to documents obtained by the American Civil Liberties Union through the Freedom of Information Act. The documents describe the state of the surveillance effort as of 2009, leaving us wondering just how vast it could be today.

This vehicle tracking program originated near border crossings in the southwestern United States but has grown into a nation-wide project. It is a joint effort between the DEA and local, state, and federal law enforcement agencies throughout the United States. The surveillance program has been alluded to in Congressional testimony every once in a while through the years, but has yet to be fully understood. The documents released by the ACLU, despite being heavily redacted, shine some much-needed light on the interests and priorities of the DEA and federal law enforcement agencies in general. As of 2009, at least 100 license plate readers had been deployed in states like California, Arizona, New Mexico, Texas, Florida, Georgia, Nevada and New Jersey.

And we should be concerned. According to the ACLU:

These records . . . offer documentation that this program is a major DEA initiative that has the potential to track our movements around the country. With its jurisdiction and its finances, the federal government is uniquely positioned to create a centralized repository of all drivers’ movements across the country — and the DEA seems to be moving toward doing just that. If license plate readers continue to proliferate without restriction and the DEA holds license plate reader data for extended periods of time, the agency will soon possess a detailed and invasive depiction of our lives.

Categories
Mission News

Security Grifting At Work: Million-Dollar ALPR System In Vermont Solves Four (4) Crimes in 2013

one-hundred-dollar-bills-falling-through-air-loop

Vermont Public Radio does the spadework to find out whether automated license plate surveillance systems offer a reasonable return on investment:

“…Even with the millions of scans, the system has not led to many arrests or breakthroughs in major criminal investigations. […] They were helpful in solving fewer than five crimes in 2013. [Officer] Cram [of Winooski PD] says the federally-funded ALPR is a valuable tool, even though he doesn’t think the city would have put up $25,000 of its own money to buy one.

At a cost of “over $1 million” over five years, that works out at around $50,000 per crime solved. [Note: Initial calculations of $40,000 per crime solved were based on an inaccurate figure of five crimes solved.]

At a rate of $50,000 per crime, you could hire one part-time police officer, and I suspect that that part-time police officer would solve more than one crime per year. So what gives?

This is what gives, for ALPR, for surveillance cameras, and for military surplus equipment. Police departments count the cost of new surveillance equipment at zero, even when it’s not (taxpayers ultimately pay). It’s hard for police chiefs to turn down free, even if free offers only the most marginal prospect of reducing crime. But it says everything about the utility of this technology that, had the City of Winooski been asked to put up its own money, Officer Cram thought that they wouldn’t have done it. Oh – and I almost forgot to mention – as the article mentions, the entity charged with managing the data from this boondoggle is, naturally, the Vermont fusion center.

Meanwhile, only half of American roads are in good repair, and our public transportation is an international laughingstock. Americans’ median incomes are falling, and more and more of us are just a paycheck or two from disaster. We scrutinize every milligram of social spending to uncover with great fanfare a rate of fraud of $0.0073 per dollar spent, because we can’t abide any of them Cadillac-driving fur-coat-clad welfare queens. And yet somehow, funding for more surveillance, more militarization, and more war, is never-ending and never requires proper accounting or justification.

Categories
Mission News

Three Bills To Protect Privacy: We Need Calls. Now.

You pulled me over? But, why?
You pulled me over? But, why?

The powerful MA Senate Ways and Means Committee is voting on whether to approve three privacy-protecting bills. The ACLU is asking Massachusetts residents to call their legislators; do it today if you can!

The License Plate Privacy Act would limit the ability of law enforcement to track your movements around the state, by keeping an enormous database of time-stamped photos taken by automated license plate readers.

The Electronic Privacy Act would require a warrant, instead of a lowly administrative subpoena, in order for law enforcement to access your electronic files, giving them the same level of protection as paper files.

The Password Protection Act would prevent your boss or administrators at your school from snooping around your social media accounts.

The legislative session ends July 31. Now is the time to make your voices heard!

Categories
News

Boston PD Suspends ALPR Program After Massive Privacy Violation

Just before Christmas, Muckrock and the ACLU of Massachusetts brought out excellent articles based on a full year of Muckrock’s investigative reporting into Boston PD’s use of automated license plate recognition technology.

ALPR systems automatically photograph and store in a police database the license plates of any car an ALPR-equipped police vehicle passes. The car may be parked or driving. It could be on the Pike, in a driveway, or anywhere a camera can reach. The question was, what does the Boston PD do with the mountain of data once it has it?

Categories
Mission News

Microscope Monday: Analysis of Massachusetts’ proposed License Plate Privacy Act, H 3068 / S 1648

steampunk_microscope

One of the curious things about digitization is that it allows data to be circulated and shared almost effortlessly. New, cheap ways of sharing and storing data can turn data collection that was previously quite innocent into a serious threat to our ability to be free from government surveillance.

Historically, the law has recognized no constitutional issue with law enforcement collection of license plate numbers, because cars are normally out in public when the numbers are collected. But what happens if cop cars can collect every license plate from every car they pass, moving or parked; check the plate against a database of outstanding warrants; link them to GPS coordinates; and retain the records of which car was where forever, so that they can retrospectively construct a map of your movements?

Well, folks, that bright new day is here. The devices are called “automated license plate readers”, or ALPRs for short. And the ACLU of Massachusetts is supporting a bill that tries to grapple with their implications, and that received its first Joint Committee on Transportation hearing on May 16.