From the Public Safety edition of October 23, 2026
Quincy, Mass., deactivates Flock plate readers and moves to a city-owned Axis Communications and OdinEye system, keeping 14-day data deletion
City of Quincy and Quincy Police Department (Massachusetts) · Policing / ALPR · Quincy, Massachusetts, U.S.
- Publisher
- City of Quincy
- Original publication
- Oct. 23, 2026, 12:59 PM (city news release)
- Source retrieved
- 2026-10-24
- Event date
- 2026-10-23
What happened
Mayor Tom Koch and Police Chief Mark Kennedy announced on Oct. 23 that the police department has deactivated its Flock Safety ALPR system and will move to Axis Communications cameras integrated with OdinEye software, which the city says will let the department keep sole ownership of the data. Existing policies remain: searches only for active criminal cases, limited users and deletion of all data within 14 days. The mayor called it a good-faith balance between investigative value and residents’ concerns about Flock; both officials said the cameras capture plates and vehicles, not faces. WCVB’s report of the announcement carries a version of the mayor’s quote that also cites City Councilors’ concerns and says at least 18 Massachusetts municipalities have quit Flock.
Why it matters
Resolves a follow-up from earlier editions and shows the most common response to ALPR backlash: change vendor and ownership model rather than end plate reading.
Evidence and measured results
Opened the city news release (primary) and the WCVB report of the same announcement for context.
Limitations and uncertainty
Government announcement, not an evaluation; no cost, timeline, effectiveness data or independent audit; residents’ groups’ response not reported in the release.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-24; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- A police department wants to keep plate reading while answering resident concerns about a vendor-run network.
- Stakeholders
- Mayor and police chief
- City Council
- City IT
- Residents’ groups
- Discovery questions
- Who will host and administer the new system?
- How is 14-day deletion enforced and verified?
- Will any data be shared outside the city?
- Value hypothesis
- A city-owned system with verified deletion and logged searches may address ownership concerns, if audits are published.
- Potential engagement
- Four-to-six week replacement options review comparing ownership, retention enforcement and sharing controls.
- Unsupported claims
- That city ownership resolves privacy objections
- Cost savings
- Improved investigative outcomes
Pre-sales engineering
Role takeaway
- Fit
- Cities replacing vendor-network ALPR with agency-owned systems.
- Architecture and integration
- Agency-owned cameras feed locally administered software with role-based search and automated deletion.
- Prerequisites
- Hosting capacity
- Access-control design
- Written ALPR policy
- Constraints
- Release gives no technical details
- Massachusetts legal context
- Old-system data deletion must be confirmed
- Security
- Enforce deletion technically, log all searches with case numbers and restrict administrator access.
- Proof of value
- Proposed: verify automated 14-day deletion
- Proposed: test that every search is logged with a case reference
Delivery
Role takeaway
- Work
- Replace cameras, deploy software, carry over policy and decommission Flock.
- Dependencies
- Procurement
- Network and hosting
- Policy update
- Ownership
- Quincy Police Department
- Skills and adoption
- Train users and auditors on the new system and policy.
- Governance checkpoints
- Confirmation of Flock data deletion
- Go-live policy review
- First audit report
- Acceptance criteria
- Proposed: no data retained beyond 14 days in sampled audit
- Proposed: published audit within six months of go-live
- Risks
- Perceived as vendor swap only
- Undisclosed cost
- Transition gaps in coverage
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Shift from a vendor-hosted network to city-owned cameras and software; system integration and hosting details are not given.
Governance
Who approves, reviews and stays accountable for outcomes?
Use limits (active cases, limited users, 14-day deletion) are department policy, not ordinance.
Security and privacy
What data, permissions and controls need testing?
City claims sole data ownership under the new system; no audit results or sharing rules are published in the release.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Not addressed.
Procurement
What should contracts, pricing and exit terms secure?
Cost, contract terms and timing of the Axis/OdinEye transition are not disclosed.
Operating model
Which teams own the service once it runs?
Executive decision in response to a nonbinding council resolution; council role in the replacement is not described.
Publication history
- 2026-10-23Public Safety · Issue 459 resources
Stable resource ID: quincy-ma-deactivates-flock-moves-to-city-owned-axis-odineye-alpr-20261023