FERPA and the K-12 Data Processing Addendum: What CfT Protects
Claude for Teachers ships its own teacher terms and a K-12 Data Processing Addendum written to comply with FERPA. Here's what that actually protects when you hand Claude your class data.
Every teacher who has ever pasted a student roster into a general-purpose chatbot has taken a risk they probably didn't fully price. Consumer AI terms of service were written for consumers — not for a professional handling protected records about other people's children. That mismatch is exactly what Claude for Teachers is built to close. It runs on its own teacher terms, designed for K-12 privacy, and it protects student information under a K-12 Data Processing Addendum written to comply with FERPA.
This piece is a plain-language read of what that protection covers and what it doesn't. If you're going to hand Claude a folder of class data to plan instruction, you should understand the legal container it lands in — not because the fine print is thrilling, but because knowing the boundaries is what lets you use the tool confidently instead of nervously. The details live in Anthropic's support article on the K-12 addendum; this is the map to it.
Why consumer AI terms fail in a classroom
FERPA — the Family Educational Rights and Privacy Act — governs education records: the roster, the grades, the diagnostics, the notes that identify a specific student. When a teacher processes those records with a third-party tool, the tool becomes part of the school's data chain, and the terms it operates under matter legally, not just as a courtesy.
The problem with reaching for a general consumer product is that its terms assume you're processing your own information. A roster isn't yours; it's a set of protected records about minors, held in trust. Consumer terms typically say nothing useful about that scenario, and in some cases they reserve rights — to retain, to reuse, to train on inputs — that are flatly incompatible with a teacher's obligations. Claude for Teachers doesn't ask you to squint at generic terms and hope. It gives educators a purpose-built agreement.
The single most important line: Claude for Teachers data is not used for model training. What you share to plan a lesson doesn't become part of the model's future.
That "not used for training" commitment is the load-bearing promise underneath everything else. It's what makes the difference between a tool you can bring near real student records and a tool you can't.
What the teacher terms and the K-12 DPA actually do
Two documents work together. The teacher terms are the overall agreement built for K-12 use rather than consumer use. The K-12 Data Processing Addendum is the more specific instrument that governs student information, written to comply with FERPA. Think of the terms as the frame and the addendum as the part that speaks directly to protected records.
Here's how the pieces map to the questions teachers actually ask:
| Your question | What Claude for Teachers provides |
|---|---|
| Are these terms meant for classroom data? | Yes — its own teacher terms, built for K-12 privacy, not repurposed consumer terms |
| Will my class data train the model? | No — Claude for Teachers data is not used for model training |
| What governs student records specifically? | A K-12 Data Processing Addendum written to comply with FERPA |
| Who decides what gets shared? | You do — you control what's shared; nothing is synced without you |
| Who's allowed on the account? | Verified educators only, consistent with the 18-and-over policy |
| Where do I read the specifics? | Anthropic's support article on the addendum |
The value of a table like that isn't the individual cells — it's seeing that the guarantees line up with a teacher's real obligations rather than a vendor's convenience. FERPA compliance isn't a badge slapped on the marketing page; it's the design target the addendum was written against.
"Written to comply with FERPA" — read the words carefully
Precision matters here, so let's be precise. Anthropic describes the K-12 Data Processing Addendum as written to comply with FERPA. That is a statement about the instrument — the addendum is drafted to meet FERPA's requirements for how a third party handles education records on a school's behalf. It is not a claim that any particular teacher's use is automatically compliant regardless of what they do, and it doesn't discharge a district's own responsibilities.
FERPA compliance is a shared arrangement. The tool has to provide terms that make lawful processing possible; the educator and the institution still have to use the tool within their own policies. Claude for Teachers does its part by supplying an addendum built for the standard and a no-training commitment that keeps protected records out of the model's future. Your part is knowing what your school permits, and applying basic discretion about what you upload — which is exactly why this series also offers a teacher data-hygiene checklist. The legal container and the professional judgment work together; neither replaces the other.
It's also worth noting who this is for. The consumer-grade risk of "the AI learns from my inputs" is precisely the risk the training commitment removes. That single guarantee reframes the whole calculus. You're not feeding a system that improves itself on your students' data; you're using a processor that treats that data as protected and disposable.
What it protects — and what stays your job
Set expectations correctly and you'll trust the tool for the right reasons. Here's the honest division of labor:
- Protected by the terms and addendum: that your class data isn't used to train the model; that student records fall under a FERPA-oriented processing agreement; that the account is gated to verified adults; that the terms were authored for K-12 rather than borrowed from a consumer product.
- Still your responsibility: deciding what to upload in the first place; following your district's and state's privacy policies; getting whatever internal approvals your institution requires; and using discretion with the most sensitive fields — names paired with health, discipline, or family details.
- Structurally reduced by design: because Claude for Teachers is teacher-only and 18-plus, there's no student account and no unsupervised-minor channel to defend, which shrinks the privacy surface before any addendum is even invoked.
That middle bullet is not a loophole — it's the nature of FERPA. No vendor can make a school compliant on the school's behalf. What a vendor can do is provide terms that make compliant use possible and remove the worst default risk of consumer AI. Claude for Teachers does both.
How to actually put this to work
If you're an individual educator, the practical path is short. Get verified, which is what keeps the product on the protected teacher terms. Read the support article once so you know where the addendum lives. Then, before you upload anything identifiable, run the quick discipline of the data-hygiene checklist: share what the task needs, withhold what it doesn't, and remember that nothing you share becomes training data.
If you're evaluating this for a district rather than yourself, the individual teacher terms are your starting reference, but a schools-and-districts offering is described as coming soon; until then, districts can use Claude for Nonprofits. Either way, the FERPA-oriented addendum is the document your privacy officer will want to read first — so send them straight to the support article.
The headline to carry away: Claude for Teachers didn't bolt privacy on afterward. It started from the recognition that classroom data is different, wrote terms to match, and built the addendum to comply with the law that governs it. That's the difference between a tool you have to use carefully in spite of its terms, and one whose terms were written for the job.
Browse the AI tutoring skills that run inside this protected workflow, or explore more education agent skills built for the classroom.
Part of the Claude for Teachers series. Related: Built for Educators: The 18+, Teacher-Only Design · A Teacher's Data-Hygiene Checklist. Browse AI tutoring skills or more builder insights.