From the Public Safety edition of October 7, 2026
Chicago police ran 23,000+ Flock searches in three months without a Flock contract, via an MOU and paid access through CDW-G, outside local oversight rules
Chicago Police Department / Office of Public Safety Administration (reported by FOX 32 Chicago) · Municipal policing / ALPR data access · Chicago, Illinois, United States
- Publisher
- FOX 32 Chicago
- Original publication
- Oct. 7, 2026, 6:56 AM CDT
- Source retrieved
- 2026-10-08
What happened
FOX 32 reported that Flock audit logs obtained after months of requests show Chicago police ran more than 23,000 searches of the Flock Safety network from May through July 2026, for reasons including traffic stops, robberies, welfare checks and homicides, even though Chicago has no active contract with Flock. The cameras searched are privately owned or belong to other agencies that share access. The city said a memorandum of understanding signed by OEMC and OPSA lets CPD log in to Flock's portal to view data shared by other municipalities and private entities; access was initially free, and OPSA now pays for it through a CDW-G service contract. FOX 32 notes that without a direct contract there are no local rules or oversight requirements governing how officers search, access or retain the data. Questions about internal authorization and arrests were referred back to CPD.
Why it matters
Shows that a city without a procurement decision can still be a heavy ALPR user through MOUs and reseller contracts, which bypasses the council and policy review that contract votes trigger.
Evidence and measured results
Investigative local TV reporting based on CPD Flock audit logs obtained through records requests, plus written responses from the city. The logs themselves were not published in full; arrest outcomes and per-search justification quality were not reported.
Limitations and uncertainty
Single-outlet report; audit logs not public; no data on outcomes or misuse; CPD internal oversight not described. Search counts are for May-July 2026 only.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-08; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Police can search large private and multi-agency ALPR networks through MOUs or reseller subscriptions that escape contract review and local rules.
- Stakeholders
- Office of Public Safety Administration
- CPD command staff
- City Council public safety committee
- Inspector general or police oversight body
- Procurement office
- Discovery questions
- Which MOUs or reseller subscriptions give officers access to vendor-hosted camera networks?
- Who issues and revokes portal accounts?
- Are search reasons and case numbers required and audited?
- Does any local ordinance cover data the city queries but does not own?
- Value hypothesis
- An inventory and policy for non-contract data access can close an oversight gap before misuse cases surface.
- Potential engagement
- Surveillance data-access inventory, policy drafting for shared-network searches, and an audit-log review of a sample period.
- Unsupported claims
- That CPD searches were improper
- Crime-solving value of the searches
- That Flock accessed city data
- That a contract would have prevented the access
Pre-sales engineering
Role takeaway
- Fit
- Relevant to any agency with vendor-portal access to shared ALPR or camera networks, contracted or not.
- Architecture and integration
- Vendor-hosted portal with per-user accounts querying cameras owned by private parties and other agencies; integration of Flock alerts noted in statements of work.
- Prerequisites
- Account inventory
- Audit-log export from the vendor
- Written search policy
- Records of MOUs and reseller agreements
- Constraints
- City does not control camera owners' sharing settings
- Illinois state ALPR and data-sharing laws
- Vendor controls log format
- Private owners' retention practices
- Security
- Require MFA and named accounts, mandatory reason and case fields, periodic log exports and anomaly review for high-volume or off-hours searching.
- Proof of value
- Reconcile account list with active personnel
- Measure share of searches with a case number and valid reason
- Identify searches outside approved purposes
- Verify no federal immigration-related sharing occurs through shared networks
Delivery
Role takeaway
- Work
- Inventory non-contract data access, write a shared-network search policy, and stand up recurring audit-log review.
- Dependencies
- Vendor cooperation on log exports
- CPD and OPSA records
- Council direction
- Legal review of MOUs
- Ownership
- Office of Public Safety Administration with CPD, under City Council oversight.
- Skills and adoption
- Officers need training on required search fields; auditors need log-analysis capacity.
- Governance checkpoints
- Inventory reported to council
- Policy adoption
- First quarterly audit report
- Annual review of MOUs and reseller access
- Acceptance criteria
- Proposed: 100% of portal accounts mapped to named, active personnel
- Proposed: searches without reason or case number fall below 5% within two quarters
- Proposed: quarterly audit report published
- Proposed: all MOUs and reseller access listed in a public surveillance inventory
- Risks
- Access continues without rules
- Vendor log limits hinder audits
- Political backlash if misuse is later found
- Shared networks expose data to other agencies
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?
Access runs through Flock's hosted portal and aggregates data from private and other-agency cameras, so Chicago does not control camera placement, retention or the network it queries.
Governance
Who approves, reviews and stays accountable for outcomes?
An MOU plus a reseller service contract created paid access without a Flock contract vote, leaving no local search, access or retention rules.
Security and privacy
What data, permissions and controls need testing?
Thousands of searches of private-camera data with no city-specific audit standard; the city says Flock gets no access to city cameras.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Officer-level portal accounts mean training and accountability depend on CPD internal practice, which the city declined to describe.
Procurement
What should contracts, pricing and exit terms secure?
Reseller vehicles such as CDW-G can carry surveillance data access that never appears as a vendor contract, so procurement inventories should include data-access subscriptions.
Operating model
Which teams own the service once it runs?
City leaders now face whether to set rules for police access to privately owned networks they do not buy.
Publication history
- 2026-10-07Public Safety · Issue 316 resources
Stable resource ID: chicago-pd-23000-flock-searches-no-contract-20261007