Independent commentary
The Dispatch Room
Education
Commentary

Your Child’s Classroom Shouldn’t Be an AI Testing Ground

Microsoft's new school privacy agreement is a welcome step. Parents still deserve to know which tools it covers—and why their children need them.

Editorial illustration of a classroom tablet casting circuit-shaped shadows across a notebook
The Dispatch Room illustration
The big picture

Microsoft's new school privacy agreement is a welcome step. Parents still deserve to know which tools it covers—and why their children need them.

A school asking a child to use an AI tool ought to have a better explanation than everybody else is doing it. Parents deserve to know what the tool teaches, what it collects and who takes responsibility when it gets something wrong. None of those questions should be treated as an obstacle to progress.

On September 9, Microsoft, the American Federation of Teachers and the United Federation of Teachers announced a National AI Safety & Privacy Standard. Their announcement describes protections for student and educator information, human oversight and clearer explanations for families. Districts can incorporate the safeguards into their Microsoft agreements.

That is a welcome development. Conservatives do not need to dislike every decision a teachers union makes, and companies should receive credit when they agree to meaningful restrictions. Protecting children is more important than maintaining a perfectly predictable partisan reaction.

But the announcement should begin a school board's questioning, not end it.

Read the scope before celebrating the promise

The published standard applies to defined educational AI products and participating arrangements. It specifically excludes general-purpose productivity, search and other tools not primarily designed for education, even when schools use them. Parents therefore should not assume every application on a school-issued device falls under this agreement.

The document prohibits using covered data for model training, with a tightly limited safety and security exception. It distinguishes de-identified operational information from covered data and restricts its uses. Those details matter more than a slogan promising that student information is safe.

This is a contractual framework, not a new nationwide law automatically governing every classroom chatbot. A district needs to explain which products are covered by its actual agreements. Saying a vendor supports student privacy is no substitute for showing families the terms that apply to their children.

Nor does identifying limits in this standard prove that an excluded product is unsafe. It means that product's protections have to be evaluated separately. Schools should be capable of making that distinction in plain English.

A privacy agreement cannot prove educational value

Even a well-protected tool has to justify taking up a student's time. A school could safeguard every piece of information and still assign software that adds little to the lesson or encourages a child to skip the work of thinking.

Before approving an AI product, administrators should describe the problem it solves and how they will know whether it helped. Does it support a specific skill? Can the teacher see how the student reached an answer? Is there a reason the same lesson cannot be taught effectively without it?

There may be good answers. A teacher might use AI to prepare practice materials, while retaining responsibility for checking them. That is a different decision from requiring a young student to have an extended conversation with a chatbot. School policy should reflect the difference rather than treating every use as equally beneficial or equally dangerous.

For families, the practical questions are straightforward: what information leaves the school, who can access it, how long is it kept, and what alternative is available if they object? Parents should receive answers before an assignment requires a new account, not after their child has already started using it.

Local control should mean that a school board can demand those answers, publish its reasoning and walk away from a product that fails to earn its place. Taxpayer-funded classrooms do not owe technology companies a customer base. They owe children an education.

Microsoft and the unions have offered a framework worth examining. The next obligation belongs to the adults buying and assigning the tools. If they cannot explain the safeguards and the educational purpose clearly, they have more homework to do before putting AI in front of students.

Discussion

Loading discussion…