From the Google edition of November 10, 2026
Chicago Public Schools blocks Gemini, ChatGPT and Claude on student devices and network, citing FERPA, COPPA and SOPPA; response to Google's Search condition undecided
Chicago Public Schools (reported by CBS News Chicago) · K-12 education · Chicago, Illinois, United States
- Publisher
- CBS News Chicago
- Original publication
- November 10, 2026, 9:52 AM CST
- Source retrieved
- 2026-11-11
- Event date
- 2026-11-09
What happened
In a Nov. 9 statement, CPS said generative AI apps including Gemini, ChatGPT and Claude are blocked on CPS-issued devices and the CPS network for all students, to protect confidential student information and comply with FERPA, COPPA and Illinois SOPPA, and that it has no plan to add generative AI to student devices. CPS said it has not determined its response to Google's policy that schools disabling AI lose Search. CBS also reports an Alphabet spokesperson saying Search cannot be offered without AI, and that Google says 150 million students and teachers use Classroom worldwide.
Why it matters
The third-largest U.S. district has a firm no-generative-AI posture grounded in state student-privacy law, which puts it directly in the path of Google's Search condition. Its eventual choice will be a reference point for other Illinois districts under SOPPA.
Evidence and measured results
Opened full article. CPS position is quoted from its statement; the Google user figure is Google's own claim.
Limitations and uncertainty
Statement-level reporting; CPS gave no decision on Search. The article does not say whether AI Overviews currently appear for CPS students.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-10; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Districts blocking generative AI for privacy-law reasons may have to choose between Search and compliance posture.
- Stakeholders
- District CIO
- Privacy officer / general counsel
- Chief education officer
- Board
- Discovery questions
- Do current blocks cover AI features inside Search?
- Does the Google DPA cover AI Overviews and AI Mode?
- What would SOPPA require to accept AI in Search?
- Value hypothesis
- A documented compliance review reduces legal ambiguity before January; no cost or outcome claims are supported.
- Potential engagement
- A three-week SOPPA/FERPA review of Google AI surfaces with a decision memo.
- Unsupported claims
- That Google AI violates SOPPA
- That CPS will block Search
- Any student harm data
Pre-sales engineering
Role takeaway
- Fit
- Relevant to districts with network and device AI blocks and Google Workspace.
- Architecture and integration
- Network filter plus Admin console controls; Search AI may not be separable by filter.
- Prerequisites
- Filter rule inventory
- Student test accounts
- Copy of the Google data agreement
- Constraints
- State privacy law (SOPPA in Illinois)
- Google's January change
- Search AI tied to Search access
- Security
- Confirm logging and data-handling terms for AI features used by student accounts.
- Proof of value
- Test log of AI exposure behind current filters
- Agreement-to-feature coverage map
Delivery
Role takeaway
- Work
- Test exposure, map agreements and produce a decision memo.
- Dependencies
- Legal review capacity
- Google's final controls
- Ownership
- District CIO with privacy officer.
- Skills and adoption
- School tech staff need clear guidance on what is blocked and why.
- Governance checkpoints
- Legal sign-off
- Leadership decision before January
- Acceptance criteria
- Every AI surface mapped to an agreement clause or flagged as uncovered
- Decision memo delivered before January
- Risks
- Filters miss AI in Search
- Legal interpretation changes
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?
CPS blocks at both device and network level; if AI Overviews in Search count as generative AI under its policy, Search itself may need blocking or a filter layer.
Governance
Who approves, reviews and stays accountable for outcomes?
CPS frames the block as legal compliance, not preference, which raises the bar for re-enabling any AI surface: a SOPPA-compliant agreement and data review would be needed.
Security and privacy
What data, permissions and controls need testing?
Privacy laws cited: FERPA, COPPA and Illinois SOPPA. Districts should check whether AI features inside Search are covered by their existing Google data-privacy agreements.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Not addressed in the source.
Procurement
What should contracts, pricing and exit terms secure?
Illinois SOPPA requires written data-sharing agreements with operators; any AI-in-Search acceptance may need agreement review.
Operating model
Which teams own the service once it runs?
Network-level blocking makes the central IT team the enforcement point for AI policy.
Publication history
- 2026-11-10Google · Issue 135 resources
Stable resource ID: cbs-chicago-cps-blocks-gemini-chatgpt-claude-students-search-response-pending-20261110