From the Public Safety edition of October 18, 2026
Bloomington, Ind., council votes 7-0 to ban city ALPR use and access to other agencies’ ALPR data, and to bar cameras whose data is shared with third parties
Bloomington City Council (Indiana) · Policing / ALPR and surveillance camera ordinance · Bloomington, Indiana, United States
- Publisher
- Indiana Daily Student
- Original publication
- Oct 15, 2026 7:11 pm; updated Oct 16, 2026 10:27 pm
- Source retrieved
- 2026-10-19
- Event date
- 2026-10-14
What happened
On Oct. 14 the council voted 7-0 to bar city agencies from owning, operating or using ALPR cameras or records systems and from accessing ALPR data collected by other agencies, and to ban surveillance cameras whose data is shared with or searchable by third parties. The administration endorsed the ALPR ban but, in an Oct. 7 memo from the deputy mayor, police chief and corporation counsel, asked to drop the broad camera provisions over unintended effects on undercover and interview-room cameras and proposed a working group. A 5-2 amendment clarified that surveillance evidence cannot be withheld from the city in criminal investigations and exempted police body cameras. The mayor had announced in April that the city would not renew its Flock contract.
Why it matters
The ordinance goes beyond ending a vendor contract: it cuts off access to neighboring agencies’ ALPR data and reaches any camera system that shares data with vendors or other governments. That affects regional task forces, real-time crime center integrations and cloud video products that share by default.
Evidence and measured results
Opened the student newspaper report of the meeting, including the administration memo and amendment votes; the ordinance text was not opened. A separate local report (bloomingtonian.com) returned HTTP 403 on the previous run and was not used.
Limitations and uncertainty
Student newspaper account; ordinance text not reviewed; mayoral signature and implementation details not confirmed in this source; two councilmembers absent.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-19; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Cities passing broad surveillance restrictions need to know which existing systems and agreements fall within scope.
- Stakeholders
- City council
- Police chief
- Corporation counsel
- City IT director
- Regional task force partners
- Discovery questions
- Which camera systems store or share data outside city control?
- Does the department query other agencies’ ALPR data today?
- Which mutual-aid or task-force agreements involve shared video or plate data?
- What carve-outs does the ordinance allow?
- Value hypothesis
- A data-flow inventory reduces compliance risk and avoids accidental disruption of permitted systems such as body cameras and interview rooms.
- Potential engagement
- 3–4 week surveillance technology inventory and ordinance compliance mapping.
- Unsupported claims
- That the ban changes crime outcomes
- That Flock shared Bloomington data with federal agencies
- That all cloud cameras are prohibited
Pre-sales engineering
Role takeaway
- Fit
- Cities and counties with restrictive surveillance ordinances or pending bills.
- Architecture and integration
- Map each camera and video platform’s storage location, external query interfaces and sharing settings; flag systems searchable by vendors or agencies.
- Prerequisites
- Ordinance text
- System inventory
- Vendor documentation on sharing
- Constraints
- Indiana and local law
- Vendor default-sharing designs
- Regional investigation dependencies
- Security
- Disable external search and sharing where prohibited; retain logs proving no external access.
- Proof of value
- Proposed: produce a data-flow diagram per system
- Proposed: verify sharing disabled through vendor admin evidence
- Proposed: confirm body-camera carve-out configuration
Delivery
Role takeaway
- Work
- Inventory, classify, reconfigure or retire systems, amend agreements, and document compliance.
- Dependencies
- Final ordinance and mayoral action
- Vendor support
- Legal interpretation of scope
- Ownership
- Police chief and city IT director jointly, with corporation counsel advising
- Skills and adoption
- Brief investigators on loss of regional ALPR access and alternative lawful channels (warrants).
- Governance checkpoints
- Legal scope opinion
- Council report on compliance
- Annual surveillance inventory update
- Acceptance criteria
- Proposed: 100% of camera systems inventoried with data-flow classification within 90 days
- Proposed: documented disablement of all prohibited sharing
- Risks
- Over-broad interpretation disables needed systems
- Hidden vendor sharing paths
- Regional partners continue collecting data about residents
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?
Bans on third-party-shared camera data implicate cloud video platforms whose architecture routes data through vendor infrastructure; agencies need an inventory of which systems share or are searchable externally.
Governance
Who approves, reviews and stays accountable for outcomes?
Council and administration diverged on breadth: administration preferred policy development via a working group; council codified restrictions with body-camera and evidence-access carve-outs.
Security and privacy
What data, permissions and controls need testing?
Sponsors cited inaccurate matches and data sharing, including concerns about federal access to Flock data after opt-outs.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Investigators lose access to regional ALPR queries; workflow impact on case closures is not quantified.
Procurement
What should contracts, pricing and exit terms secure?
Future camera or video purchases must avoid vendor- or agency-shared data paths; four Flock security cameras remain but are described as not connected to Flock’s network.
Operating model
Which teams own the service once it runs?
Possible parking ALPR use deferred to a later discussion tied to a parking study.
Publication history
- 2026-10-18Public Safety · Issue 407 resources
Stable resource ID: bloomington-ind-alpr-ban-third-party-camera-limits-20261015