Your area Not set — showing everywhere
Issue · Cambridge, MA

ShotSpotter Surveillance Technology Use

Continued use of gunshot detection technology faces opposition over high false positive rates, privacy risks, racial disparities in placement, and conflicts with sanctuary city policies.

Overview

Cambridge's use of ShotSpotter acoustic sensors has generated repeated public opposition centered on accuracy, privacy, equity, and sanctuary-city compliance. After extensive comment on May 11 and May 18, 2026, the council adopted a policy order restricting data use and requiring further review.

Background

ShotSpotter acoustic gunshot detection technology entered Cambridge public debate through sustained resident opposition at city council meetings, with speakers highlighting its placement without prior council approval and its operation via a third-party contractor funded partly through federal grants.

Public comment on May 11, 2026, featured more than 20 speakers urging termination of the system on grounds that it failed the city's surveillance ordinance standards, produced an 82% false-positive rate, and risked data sharing with federal immigration authorities in conflict with sanctuary-city policies.

The same meeting recorded one speaker defending retention for quicker police response to shootings, setting up a clear divide that carried forward.

One week later on May 18, 2026, over two dozen additional speakers reiterated accuracy, privacy, equity, and data-ownership objections while referencing Policy Order 98 as the vehicle for removal; the police commissioner countered with claims of eleven undetected incidents over a decade and faster response times.

Council debate that evening included a failed motion to table the order (4-5), followed by adoption of the order restricting data use (5-2 with 2 present), which imposed limits on future deployment and required further review.

The sequence of public comment followed by formal consideration established a causal path from community pressure to policy restriction, with the adopted order now governing ShotSpotter operations pending scheduled follow-up discussion.

On June 22, 2026, the council took up a charter right review of amendments to a neighborhood safety plan post-ShotSpotter. After confirming satisfaction with changes from Sobrinho-Wheeler and Al-Zubi, the amended policy order was adopted.

On June 8, 2026, the council considered a policy order requiring completion of surveillance ordinance determinations before any future ShotSpotter vote and took up a separate policy order on neighborhood safety steps after discontinuation. The surveillance compliance order failed after a motion to call the question passed 7-1; the safety plan item was deferred by charter right.

How it unfolded
Multiple speakers urged ending ShotSpotter use, citing 82% false positives, racial disparities, privacy risks, lack of local contract control, and sanctuary-city conflicts; one speaker supported retention for faster response.
2026-05-11City Council
Over two dozen speakers opposed continued deployment on accuracy, privacy, equity, and data-sharing grounds and referenced Policy Order 98; after debate the council defeated a tabling motion 4-5 then adopted the order restricting data use 5-2 with 2 present.
2026-05-18City Council
Council considered policy order requiring City Council to complete required determinations under Section 2.128.060 C before any future vote on surveillance technology; motion to call the question passed 7-1 and the policy order failed 2-6 with one absent.
2026-06-08City Council
Council considered a policy order requesting a report on additional steps to maintain neighborhood safety following the end of ShotSpotter technology; amendments were offered and charter right was exercised by E. Denise Simmons, deferring final action.
2026-06-08City Council
Council conducted charter right review of amendments to neighborhood safety additions plan post-ShotSpotter and adopted the amended policy order by 8-0 roll call.
2026-06-22City Council
Arguments in favor
Enables faster police response times to gunshots.
city-council 2026-05-18
For
Has detected eleven incidents over ten years that would otherwise have gone unnoticed.
city-council 2026-05-18
For
Supports community safety needs in areas experiencing gun violence.
city-council 2026-05-18
For
Arguments against
Produces false-positive rates between 49% and 82%, leading to unnecessary policing.
city-council 2026-05-18
Against
Disproportionately affects Black and Brown neighborhoods without proven reduction in gun violence.
city-council 2026-05-11
Against
Enables constant audio recording and potential data sharing with ICE/DHS that conflicts with sanctuary-city status.
city-council 2026-05-18
Against
Operates without prior council vote and under a contract controlled by a private vendor with federal ties.
city-council 2026-05-11
Against
Key voices
“ShotSpotter fails the city's surveillance ordinance because it disproportionately surveils Black and Brown neighborhoods and has a high false positive rate.”
Gideon Epstein, ACLU policy counselcity-council 2026-05-11
“Cambridge has no direct contract, data can be shared with federal agencies conflicting with sanctuary city status, and the system enables constant audio surveillance.”
Gloria Korsmancity-council 2026-05-11
“ShotSpotter amounts to unfettered surveillance in Black and Brown neighborhoods with no FOIA accountability and DHS/ICE funding ties.”
Kayla Goodalecity-council 2026-05-18
What's next

Item returns at a future meeting.

ShotSpottergunshot detectionsurveillancefalse positives