
Florida’s attorney general has asked a court for an emergency injunction that would stop OpenAI from developing new versions of ChatGPT, as part of a lawsuit over harm to children. If you run a K-12 district, a charter network, a private school or an edtech company, this matters now: a ruling on the ChatGPT Edu K-12 schools Florida injunction request could arrive before most schools have checked their safety settings or data agreements. You don’t need to panic or rip anything out. But get your settings, contracts and backup plan in order this week, before a judge decides for you.
What’s new: the ChatGPT Edu K-12 schools Florida injunction request
The Florida attorney general’s office has already sued OpenAI over harm to children. It now seeks emergency relief, and the request is unusual. Most consumer-protection injunctions target a specific feature, ad or disclosure. This one asks the court to stop OpenAI from developing new ChatGPT versions while the case proceeds. It targets OpenAI’s product roadmap, so a narrow fix to one feature would not satisfy it.
Emergency injunctions are hard to win. A court usually wants a likely win on the merits, irreparable harm, and a balance of hardships that favors the state. Even if a judge grants some relief, it will probably be narrower than the request: added safeguards for minors or age-verification commitments rather than a full development freeze. No ruling has been issued, and we won’t guess how the judge will lean. For schools, the point is that the outcome is uncertain and the timing is out of their control.
The request also reaches schools that never signed up for ChatGPT. Several popular classroom tools run partly on OpenAI models. Khanmigo was built with OpenAI. MagicSchool uses a mix of large language model providers. OpenAI’s own education products include ChatGPT Edu and the teacher-focused ChatGPT for Teachers. If court orders freeze or tie up OpenAI’s release schedule, the effects will spread to those tools too.
Why it matters for AI student safety policy in 2026
- Service continuity risk is real, even though a shutdown is unlikely. A development freeze would not switch off existing models. It could delay safety updates, new features and model upgrades that vendors have promised.
- Your vendors have vendors. Your contract may be with MagicSchool or Khan Academy, but the underlying model may belong to OpenAI. Your district AI compliance checklist must cover those subprocessors, not just the company that invoices you.
- Other states are watching. If Florida gets any relief, expect other attorneys general to copy the approach. A district that documents its safeguards now will be better positioned when a parent, board member or state regulator asks questions.
- COPPA and FERPA exposure rises when a lawsuit makes the news. Parents who ignored your AI rollout will start reading privacy notices. If students under 13 use a tool without proper COPPA consent, or student records are shared outside FERPA’s school-official exception, you’re exposed.
- Edtech businesses face a sales conversation now. Procurement teams will ask which model you run on and what you’ll do if that provider is restricted. “We’ll figure it out” loses deals.
- Documented safety settings are a liability shield. A dated screenshot of your content filters, age restrictions and data-retention settings is worth more than any policy PDF sitting in a shared drive.
How to use it today: a school district AI compliance checklist
Here is the sequence we’d follow if we ran technology for a district or an edtech company this week. Each step produces something you can file, show a board, or hand to legal counsel.
-
Inventory every AI tool that touches students or student data. Include teacher-only tools, because teachers paste student work into them. Record the model provider behind each one. Use this template in a shared sheet:
tool_name,vendor,underlying_model_provider,users(students/teachers/staff),min_student_age,signed_DPA(Y/N),DPA_date,COPPA_consent_method,FERPA_school_official(Y/N),data_retention_days,trains_on_our_data(Y/N),backup_tool ChatGPT Edu,OpenAI,OpenAI,teachers+staff,N/A,Y,2026-01-15,N/A,Y,30,N,Gemini for Education Khanmigo,Khan Academy,OpenAI,students+teachers,13,Y,2025-08-20,school consent,Y,TBD,N,MagicSchool MagicSchool,MagicSchool AI,multiple,students+teachers,TBD,Y,2025-09-01,school consent,Y,TBD,N,KhanmigoReplace the example rows with your own data. Every “TBD” is a question to send the vendor.
-
Send every vendor a continuity and data questionnaire. Ask for written answers, not a phone call:
Subject: Student data and service continuity questions - [District Name] Hello [Vendor], Given the pending litigation between the State of Florida and OpenAI, please confirm in writing by [date]: 1. Which large language model provider(s) power the features our students and staff use? 2. If your primary model provider were restricted by court order, what is your fallback, and how long would a switchover take? 3. Is any student data (prompts, outputs, uploaded files) used to train or improve models, by you or any subprocessor? 4. What is the retention period for student prompts and outputs, and can we set it to zero or delete on request? 5. List all subprocessors that receive student data. 6. How do you verify age and obtain COPPA consent for users under 13? 7. What content filters are enforced for minors, and can we audit flagged conversations? Thank you, [Name, Title] -
Lock down ChatGPT Edu and ChatGPT for Teachers workspace settings. In the admin console, check who can access the workspace, whether third-party GPTs and apps are allowed, whether sharing links and memory are on, and how data retention is configured. OpenAI says Edu and enterprise workspace data is not used for training by default; confirm that in your own agreement, not a marketing page. If you use SSO, restrict access to staff domains unless a signed agreement specifically covers student use. Take dated screenshots of every setting.
-
Deploy a guardrail system prompt on any custom GPT or classroom assistant. It won’t stop a determined student, but it sets defaults and shows reasonable care:
You are a classroom learning assistant for students in grades [X-Y] at [School]. Rules you must follow at all times: - Help students learn; do not complete graded assignments outright. Explain steps and ask guiding questions instead. - Never ask for or store personal information (full name, address, phone, birthday, photos, passwords). - If a student mentions self-harm, abuse, danger, or a crisis, stop the lesson, respond with care, and tell them to talk to a trusted adult or school counselor right away. In the US they can call or text 988 at any time. - Do not role-play romantic, violent, or adult scenarios. - Do not give medical, legal, or mental health diagnoses. - If unsure whether a request is appropriate, decline politely and suggest asking the teacher. -
Write a one-page AI student safety policy addendum. Boards approve short documents faster. Start with this outline:
AI STUDENT SAFETY ADDENDUM (2026-27) 1. Approved tools: [list from inventory]. All others prohibited for student use. 2. Age rules: students under 13 use only tools with verified school-authorized COPPA consent. 3. Data: no student PII entered into non-approved tools. Approved tools must have signed DPAs with no-training clauses. 4. Supervision: student-facing AI use occurs in teacher-supervised settings; flagged conversations reviewed within [48] hours. 5. Continuity: each approved tool has a designated backup (see inventory). Switchover owner: [name]. 6. Review: this addendum is reviewed after any material court ruling or regulatory action affecting an approved vendor. -
Pick and test a backup tool now. Don’t wait for a ruling to discover your fallback needs a three-month procurement cycle. Choose a backup on a different model provider and run one class period on it this month so teachers have seen it before they’re forced to use it.
-
Set up a monitoring alert. Assign one person to track the case docket and news. A free Google Alert on “Florida attorney general OpenAI lawsuit” plus “injunction” is enough. When a ruling lands, this playbook tells you what to review.
How it compares: MagicSchool vs Khanmigo vs ChatGPT Edu vs Gemini
Most schools want to know which tool carries the least risk if OpenAI is restricted. The table below is a planning snapshot. Vendor details change often, so confirm each row against your own contract.
| Tool | Primary audience | Model dependency on OpenAI | Student-facing option | Best role in a backup plan |
|---|---|---|---|---|
| ChatGPT Edu / ChatGPT for Teachers | Staff, teachers, higher ed | Direct (it is OpenAI) | Limited for K-12; depends on your agreement | Primary teacher productivity tool; needs a backup |
| Khanmigo | K-12 students and teachers | High (built with OpenAI models) | Yes, with guardrails for learning | Student tutoring; don’t pair it with ChatGPT as the only backup |
| MagicSchool | K-12 teachers, with student tools | Partial (uses multiple providers) | Yes (student rooms) | Good diversified backup for teacher workflows |
| Gemini for Education | Google Workspace for Education schools | None (Google models) | Yes, under Workspace for Education terms | Strongest independent fallback if you’re already on Google |
Our view: a district running ChatGPT for teachers and Khanmigo for students has most of its AI capability on one model provider. Adding a backup from a different provider, such as Gemini for Education or MagicSchool configured on a non-OpenAI model, is the simplest way to reduce that concentration. If you sell edtech, multi-provider support is now a selling point.
What’s next
First, watch the ruling on the emergency request. Expect OpenAI to argue that a development freeze is far too broad and that its existing teen protections, such as age prediction and parental controls, already address the state’s concerns. The likeliest outcomes, in rough order, are a denial, a narrow order requiring specific safeguards for minors, or a negotiated agreement. A full development freeze would be the most surprising result and would almost certainly be appealed immediately.
Second, watch for copycat action. State attorneys general have grown more aggressive on minors’ online safety, and any lawsuit that gains traction becomes a template for other states. Also watch for updated Federal Trade Commission guidance on COPPA as it applies to AI chat tools, and for state student-privacy laws that add AI-specific requirements. Each adds a line item to your compliance checklist.
Third, watch how vendors respond. We expect edtech companies to advertise multi-provider support, offer stronger contract language on retention and training, and publish third-party safety audits. Districts with the inventory and questionnaire from this guide can compare those claims quickly. Districts without them will take vendors at their word.
Frequently Asked Questions
Will ChatGPT Edu stop working in schools if Florida wins the injunction?
Almost certainly not immediately. The request targets development of new ChatGPT versions, not the operation of existing ones. The bigger practical risks are delayed updates and shifting vendor roadmaps, which is why a tested backup tool is worth setting up now.
Does the Florida attorney general’s OpenAI lawsuit apply to schools outside Florida?
A state court order against OpenAI can affect its products everywhere, because the company doesn’t build a separate ChatGPT for each state. Non-Florida schools aren’t parties to the case, but they are exposed to whatever the ruling does to the product.
How do COPPA and FERPA apply to AI tools in the classroom?
COPPA covers online services that collect personal information from children under 13. Schools can sometimes consent on parents’ behalf, but only for educational purposes. FERPA governs student education records, and vendors generally must qualify as “school officials” under a written agreement. In practice, that means a signed data privacy agreement, no training on student data, and clear retention limits.
MagicSchool vs Khanmigo: which is safer right now?
Both are built for K-12 and include classroom guardrails. The difference that matters for this lawsuit is model dependency: Khanmigo leans heavily on OpenAI, while MagicSchool uses multiple providers. Neither is automatically “safer.” Choose based on your signed agreements and on which tool complements your primary vendor rather than duplicating its risk.
What should an edtech company tell school customers this week?
Send a short continuity statement before customers ask. Name your model providers, describe your fallback plan and switchover time, confirm your no-training and retention terms, and link to your latest safety documentation. Answering early builds trust and shortens renewal conversations.
Is a written AI student safety policy really necessary in 2026?
Yes. When regulators, parents or lawyers ask what you did to protect students, a board-approved addendum, dated settings screenshots and signed vendor responses are your answer. Without them, you’re relying on memory and goodwill, and neither holds up in a lawsuit.
Go deeper than this article
This article covers the essentials. Our premium eguide library gives you the full step-by-step playbooks — prompts, workflows, and copy-paste recipes you can put to work today.