{"resourceId":"bloomington-ind-alpr-ban-third-party-camera-limits-20261015","versions":[{"version":"external-296bb03a86ee1ab785af25ea554f36c47959986b41601237bb5f3e6554c67329","resource":{"id":"bloomington-ind-alpr-ban-third-party-camera-limits-20261015","title":"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","organization":"Bloomington City Council (Indiana)","sector":"Policing / ALPR and surveillance camera ordinance","geography":"Bloomington, Indiana, United States","publishedAt":"Oct 15, 2026 7:11 pm; updated Oct 16, 2026 10:27 pm","publicationDate":"2026-10-15","eventDate":"2026-10-14","sourceName":"Indiana Daily Student","sourceLabel":"Bloomington City Council bans Flock, all automated license plate reader technology","sourceUrl":"https://www.idsnews.com/article/2026/10/city-council-flock-ban-bloomington-license-plate-readers","evidenceClass":"independent-reporting","outcomeClass":"cautionary","topics":["governance-procurement","data-security","operating-model"],"finding":"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.","sledRelevance":"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":"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.","architectureImplications":"Interpretation: 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.","governanceImplications":"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.","securityPrivacyImplications":"Sponsors cited inaccurate matches and data sharing, including concerns about federal access to Flock data after opt-outs.","caveats":"Student newspaper account; ordinance text not reviewed; mayoral signature and implementation details not confirmed in this source; two councilmembers absent.","streamIds":["public-safety"],"roles":{"sales":"Sales framing: Bloomington shows bans now reach data access and cloud camera architecture, not just Flock contracts. The council barred city use of other agencies’ ALPR data and cameras whose data is shared with third parties. For police chiefs, city attorneys and IT leads in similar cities, the bounded offer is a surveillance technology inventory and ordinance-impact assessment. This evidence cannot support claims about crime effects of the ban or vendor misconduct.","engineering":"Engineering framing: the ordinance turns on whether data is shared with or searchable by third parties, which describes many cloud video products by default. Pre-sales should inventory every camera and video system, trace where footage is stored and who can query it, and identify regional data-sharing agreements. Proof should document data flows per system so the city can show compliance or plan replacements.","delivery":"Delivery framing: compliance work includes inventorying systems, disconnecting or reconfiguring third-party sharing, revising task-force agreements and documenting carve-outs such as body cameras. Dependencies are the ordinance text, vendor cooperation and legal interpretation. The police chief and city IT should jointly own implementation. Acceptance should be measured by a completed inventory, documented data flows and verified disconnection of prohibited sharing, with a short compliance report back to council."},"roleDetails":{"sales":{"customerProblem":"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"],"discoveryQuestions":["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?"],"valueHypothesis":"A data-flow inventory reduces compliance risk and avoids accidental disruption of permitted systems such as body cameras and interview rooms.","potentialEngagement":"3–4 week surveillance technology inventory and ordinance compliance mapping.","unsupportedClaims":["That the ban changes crime outcomes","That Flock shared Bloomington data with federal agencies","That all cloud cameras are prohibited"]},"engineering":{"fit":"Cities and counties with restrictive surveillance ordinances or pending bills.","architectureIntegration":"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.","proofOfValue":["Proposed: produce a data-flow diagram per system","Proposed: verify sharing disabled through vendor admin evidence","Proposed: confirm body-camera carve-out configuration"]},"delivery":{"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","skillsAdoption":"Brief investigators on loss of regional ALPR access and alternative lawful channels (warrants).","governanceCheckpoints":["Legal scope opinion","Council report on compliance","Annual surveillance inventory update"],"acceptanceCriteria":["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"]}},"retrievedAt":"2026-10-19T02:52:42Z","enrichedAt":"2026-10-19T03:00:30Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Investigators lose access to regional ALPR queries; workflow impact on case closures is not quantified.","procurementImplications":"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.","operatingModelImplications":"Possible parking ALPR use deferred to a later discussion tied to a parking study.","sourceVerification":{"openedUrl":"https://www.idsnews.com/article/2026/10/city-council-flock-ban-bloomington-license-plate-readers","referenceExcerpt":"the city is banned from accessing ALPR data obtained by other agencies","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}