Documented Incident

Data SharingAuditsPolice MisusePrivacyMassachusetts

Boston report: Flock shared city ALPR data with outside agencies despite contract ban

Boston's 2025 Surveillance Technology Report, obtained by WBUR ahead of its release to the City Council, says that within three days of launching a no-cost Flock Safety pilot on April 1, 2025, Boston Police discovered that outside law enforcement agencies could access the city's license plate and vehicle data — despite a contract that required data sharing to be turned off. The report attributes the exposure to an error by Flock, which secured the system after three days; it does not identify which agencies accessed the data or how many Massachusetts drivers were affected. The 156-day pilot used 45 cameras and ended Sept. 4, 2025, with data deleted and equipment removed within 30 days. BPD and city officials say they will not use Flock services going forward; Flock did not respond to WBUR's request for comment.

Why this matters

The episode tests whether contractual promises to disable data sharing can be verified in practice, a question facing every community that signs an ALPR agreement with sanctuary-style or immigration-related restrictions. It also highlights that Boston's council says it learned of subsequent ALPR pilots only after they began.

Key facts

Timeline

Sources

This summary was written from the published reporting below and links to it; BlockFlockNow does not reproduce article text.

More from Massachusetts

Everything we have documented in Massachusetts, or search every Massachusetts article in the archive.

About this record

BlockFlockNow documents reported incidents involving Flock Safety cameras and automated license plate readers: council votes, contract decisions, misuse by authorized users, lawsuits, audits, and community response. Every record is reviewed by a person before publication. New to the topic? Start with What is Flock?, find meetings near you, or learn how to request your town's camera records.

Updated September 18, 2026. Corrections: blockflock@bytebunny.io. See all documented incidents or search the full article archive.