Articles · Privacy · District leadership · AI in education
Student data privacy: what district leaders have to get right
A plain-language overview of FERPA, COPPA, and vendor agreements for district leaders, plus the AI-era questions to settle before a tool reaches students.
By Dr. William Hickman · 5 min read
A parent asks a principal a simple question: “What does this app know about my child, who can see it, and how long do you keep it?” In too many districts, nobody in the building can answer, and the honest reply is “I’ll find out.” That gap is where trust leaks out.
Student privacy used to be mostly about file cabinets. Now a single student can generate login times, every response to every check, the full revision history of every document, and, with AI tools, every prompt she typed and every reply she received. Most of that data serves real educational purposes. All of it needs a steward.
A note before we start. This is a general overview from a former superintendent, not legal advice. Federal rules change, state laws vary widely, and your district’s attorney and your state education agency have the final word. Use this to know which questions to bring them.
FERPA in plain English
The Family Educational Rights and Privacy Act protects the privacy of student education records at schools and districts that receive funding from the U.S. Department of Education. In broad terms, it gives parents the right to inspect and review their child’s education records, to ask the school to amend records they believe are inaccurate or misleading, and, with important exceptions, to consent before personally identifiable information from those records is disclosed. Those rights generally transfer to the student at age 18 or when the student enrolls in a postsecondary institution.
The exception that matters most for technology is often called the school official exception. In general, a district may share records with a vendor without parental consent when the vendor performs a service the district would otherwise use its own staff for, is under the district’s direct control with respect to the use and maintenance of the records, and uses the data only for the purposes the district authorized. Your annual FERPA notice should describe who counts as a school official and what counts as a legitimate educational interest. Ask counsel whether yours was written with today’s tools in mind.
Here is the AI angle. When a tool builds a running model of what a student knows, what she struggles with, and what help she asked for, that model may well be part of her education record. Families may ask to see it and to correct it. Plan for that request before it arrives.
COPPA in plain English
The Children’s Online Privacy Protection Act, enforced by the Federal Trade Commission, applies to commercial websites and online services directed to children under 13, or that know they are collecting personal information from children under 13. In general, it requires verifiable parental consent before that information is collected, along with notice and limits on how the data is used and kept.
Schools enter the picture because FTC guidance has allowed a school, in limited circumstances, to provide consent on parents’ behalf when a service is used solely for the school’s educational purpose and for no other commercial purpose. That is not a blank check. It does not cover advertising or building profiles for unrelated uses, and a district should decide who is authorized to give that consent and how parents are told. The FTC updated the COPPA rule in 2025, with companies required to comply by April 2026, adding protections that include limits on how long children’s data can be kept. Ask counsel how the update affects your consent practices.
One practical point: many general-purpose AI chatbots set 13 as their minimum age, and some require a parent’s permission for anyone under 18. Check a product’s terms before any teacher assigns it to students.
State law and the rest of the stack
Most states have added their own student data privacy laws, often restricting the sale of student data, targeted advertising, and profiling, and some require specific contract terms. Special education records carry additional confidentiality requirements under IDEA. The Protection of Pupil Rights Amendment governs certain surveys that ask students about sensitive topics. Breach notification rules vary by state. Your state education agency likely publishes guidance, so start there.
The vendor agreement is where privacy actually lives
Laws set the floor. Contracts decide what actually happens to a child’s data. Before any tool touches student information, the agreement should answer, in writing:
- Purpose. Data is used only to provide the service to the district, and for nothing else.
- No sale, no ads. No sale of student data and no targeted advertising.
- Model training. Whether student work, prompts, or recordings are used to train the vendor’s AI models. If a sales representative tells you “never,” ask for that sentence in the contract.
- Minimization. The tool collects only what it needs to do its job.
- Retention and deletion. How long data is kept, and how it is deleted or returned when the contract ends, with written confirmation.
- Subprocessors. Who else touches the data, and where it is stored.
- Security and breach notice. Basic safeguards, and how fast the district hears when something goes wrong.
- Access. How the vendor helps the district respond when a parent asks to see or correct a record.
Many districts use a standard data privacy agreement, often a state or consortium model, which saves time and raises the floor for everyone. Use one if you can.
The new data types AI creates
AI tools collect things older software never did: chat logs, reflection prompts, voice recordings of children reading, and analytics on who contributed what in a group. Each deserves a real decision, not a line buried in the acceptable-use policy.
Think about the reflection box. When a thirteen-year-old types “I don’t get any of this and I’m scared to ask” into a tutor’s prompt, that sentence is now data. Decide before deployment who can see it, how long it lives, and whether it ever leaves the building.
Then hold one more line. Data collected to help students learn is used for coaching, never for surveillance, and never to evaluate teachers. A dashboard a student understands works for her. One she finds frightening works on her.
Free tools are the biggest gap
Most AI arrives in schools through a teacher’s browser, not a purchase order. In a Gallup survey published in May 2026, only 18 percent of public school teachers said administrators had given them formal guidance on AI. So give teachers a simple rule while policy catches up: treat any tool whose data policy you cannot explain as a public space, and never put a student’s name, story, or private work into it. Then build an approval process light enough that teachers will actually use it.
What to do this week
- Inventory. List every tool that touches student data, including free ones, and mark which have a signed agreement.
- Name an owner. Assign a privacy lead and an oversight group that includes instruction, technology, and special education.
- Write the family paragraph for your five most-used tools: what each tool does, what it keeps, who can see it, and whom to contact. Translate it.
- Ask counsel two questions. Does our annual FERPA notice define school officials in a way that fits our current vendors? How do we handle COPPA consent for students under 13?
- Write the incident protocol: who is told, and how fast, when student data is exposed.
For how AI dashboards and learning agents should handle student data, see the chapter on the intelligence layer in The Intelligent Classroom.