FERPA, COPPA and AI in Schools: A Privacy Checklist

What schools should ask before adopting AI tools: student records under FERPA, children's privacy under COPPA, data use, retention, and vendor controls.

Short answer

FERPA, COPPA, and AI in schools: a privacy checklist

FERPA protects students' education records and COPPA protects personal information collected online from children under 13. Neither law bans AI, but both shape how a school can use it. Before adopting an AI tool, confirm what student information it collects, that the school keeps control of that information, that it is not used to improve public AI tools, how long it is kept, and that access is limited by role.

Use this page as part of a connected review: understand the purpose, consider the people affected, check the relevant safeguards, and follow the related routes for practical next steps.

Privacy review is often where school AI projects stall. Most of the delay comes from unclear answers: vendors that cannot say where conversations are stored, consumer accounts outside the school's control, or terms that allow data to be used for training. A consistent set of questions makes review faster and decisions easier to explain to families.

What FERPA and COPPA cover, in plain terms.

FERPA is a federal law that protects the privacy of student education records. In everyday terms, those records include much of what a school keeps about a student, such as grades, assignments, and attendance, and they can include work and messages that pass through school systems. When a school shares records with an outside service, it generally needs that service to work on the school's behalf, under the school's direction, and only for the agreed purpose.

COPPA covers online services that collect personal information from children under 13. It generally requires verifiable parental consent before that information is collected and limits how it can be used. Federal guidance describes when a school may provide consent for a tool used only for school purposes. Many states also have their own student privacy laws. This guide keeps the legal points general, so confirm the specifics with your privacy officer, legal counsel, or district and state guidance before making decisions.

Why AI tools raise new privacy questions.

Older classroom software often collected a fixed set of information: a roster, some scores, a few settings. AI tools are different because people type freely into them. A student might mention a family situation while asking for help with a personal essay. A teacher might paste part of a support plan while asking for help with accommodations. What a tool receives depends on what people choose to share, so a review needs to consider conversations as well as account details.

Uploaded files add another layer. Lesson materials, student writing samples, and meeting notes can all contain names and personal details. When reviewing a tool, ask about uploads specifically: where they are stored, whether they are kept after a conversation ends, whether they are used to improve the product, and who in the school can see them.

A privacy review in practice.

A common case: a middle school teacher asks to use an AI tool for feedback on student writing. A reviewer starts with a one-page sketch: what goes in (student essays, perhaps with names), where it goes (the vendor's storage), who can see it (the teacher and perhaps an instructional coach), and when it is deleted. The sketch shows which questions still need answers from the vendor.

The reviewer then compares the vendor's written answers with the data agreement and the public help pages. If one document says information is used only to provide the service and another suggests conversations help improve the product, that difference is worth raising. Clear, consistent answers in writing are a good sign. While the review runs, the teacher can take a safe step on their own: remove names from essays before using any tool that is not yet approved.

Ethos was built with this kind of review in mind, with school-controlled data, school sign-in, role permissions, audit trails, private cloud options, and alignment with FERPA, COPPA, GDPR, and SOC 2. Those controls can make the vendor questions in this guide quicker to answer. Schools should still run their own review and confirm the answers with their privacy reviewers.

Explaining privacy decisions to families.

Families rarely want legal language. They want to know which tool their child is using, what it can see, and who to call. A short note works well: the name of the tool, what students use it for, what information it receives, how long that information is kept, and a named contact at the school. Posting the same summary on the school website saves staff from answering the same questions one family at a time.

Keep that summary current. When a new tool is approved or an old one is retired, update the page and let families know. A steady, predictable habit of telling families what has changed builds more trust over time than any single announcement. Note when the page was last updated so families can see it is looked after.

Know what data is collected. List every type of information the tool receives: names, emails, class rosters, student work, chat conversations, and uploaded files.

Keep the school in control. Student data should be processed on the school's behalf, under the school's direction, with clear limits on use, disclosure, and retention.

Rule out training on student data. Confirm in writing whether student and staff content is used to improve the AI tool, and whether that can be turned off.

Limit access by role. Use school sign-in, role permissions, and audit trails so the right people see the right information and access can be reviewed.

Questions for every AI vendor:

What student data do you collect, and where is it stored?

Is any student or staff information used to improve the AI tool?

How long is data kept, and how is it deleted on request?

Do you support school sign-in, role permissions, and audit logs?

Documents to request:

A data privacy agreement aligned with FERPA, COPPA, and your state's student privacy law.

Security documentation, such as SOC 2 alignment or reports.

A plain-language summary you can share with families.

Inventory. List the AI tools already in use, including personal accounts teachers and students rely on.

Review. Run each tool through the same vendor questions and data agreement.

Configure. Turn on school sign-in, roles, and retention settings before launch.

Communicate. Tell families what is used, what data is involved, and who to contact with questions.

Use this checklist to structure privacy conversations with AI vendors. It is not legal advice; involve your legal counsel and privacy officer, and confirm requirements in your state.

Common questions

Quick answers to what schools and families ask most about this topic.

Does FERPA allow schools to use AI tools?

Yes. FERPA does not ban AI, but it governs how student education records are shared. Schools typically need the vendor to act on the school's behalf, under its direct control, and use student data only for the authorized purpose.

How does COPPA apply to AI in schools?

COPPA protects personal information collected online from children under 13. When an AI tool is used with younger students, schools should confirm the vendor's COPPA practices and how consent is handled for school use.

How does Ethos handle student privacy?

Ethos is designed around a FERPA-aligned, school-ready architecture and is aligned with COPPA, GDPR, and SOC 2. Schools get school-controlled data, school sign-in, role permissions, audit trails, and private cloud options.

What should a school ask an AI vendor about student data?

Ask in writing what data is collected, whether it is used to improve the AI tool, where it is stored, how long it is kept, who can access it, and how it is deleted when the contract ends.

Do parents need to consent before students use AI tools?

For children under 13, COPPA generally requires verifiable parental consent. FTC guidance lets schools consent on parents' behalf when a tool is used only for school purposes. Schools may still choose to notify families, so check district policy and state law.