Trust & Student Data
Student Data Privacy, FERPA & COPPA
LessonDraft is built so schools never have to put student records into it. The safest student data is the data we never collect — and that's a design decision, not a promise.
The safest data is data we never collect
LessonDraft is data-light by design. Teachers enter a grade, subject, and topic — not class rosters, gradebooks, or student records. The cleanest way to protect student data under FERPA and COPPA is to keep it out of the tool in the first place, and that is exactly how LessonDraft is built.
No student accounts, no child data
Accounts are for teachers and adult staff. Students never sign up, never log in, and never enter personal information. Because we don't collect personal information from children, COPPA's child-data obligations don't get triggered by classroom use.
Describe students generically
For report card comments, IEP goal drafts, or parent emails, teachers describe a student's strengths and needs in general terms — no names, IDs, or identifying details are needed to get a useful first draft they then edit.
Your content isn't used to train AI
Generations are powered by Anthropic's Claude API under terms where submitted content is not used to train AI models. We store your generations in our database only to give you your own history — we never sell data, and we run no advertising or tracking cookies.
How LessonDraft maps to FERPA
FERPA protects student education records held by schools and districts. The most reliable way to stay compliant with any vendor is data minimization — sharing as little student information as possible. LessonDraft takes that to its logical end: it is designed so that education records are never entered into the product. Teachers generate from grade, subject, and topic, and describe students in general terms. There is no roster to upload, no gradebook to connect, and no student PII sitting in our system to expose.
For schools that require it, we're glad to put this in writing — contact us to request a data processing agreement.
Who processes your data
We use a small set of trusted, industry-standard subprocessors. We're transparent about all of them:
See our Privacy Policy for full detail on collection, retention, and deletion.
Frequently asked questions
Is LessonDraft FERPA compliant?
FERPA governs the schools and districts that hold student education records, and the vendors that handle them on a school's behalf. LessonDraft is designed so that student education records are never entered into the tool: teachers work from grade, subject, and topic, and describe students generically. By minimizing the data collected, LessonDraft supports schools in meeting their FERPA obligations rather than creating new exposure. Schools that require a written agreement can contact us.
Does LessonDraft comply with COPPA?
COPPA applies to operators that knowingly collect personal information from children under 13. LessonDraft accounts are for teachers and adult staff only — students do not create accounts or submit personal information — so classroom use does not involve collecting child data.
Do teachers need to upload student rosters or grades?
No. LessonDraft never requires class rosters, gradebooks, or student records. That data-light design is intentional and is the core of our student-data privacy posture.
Does LessonDraft sell student or teacher data?
No. We do not sell personal data, we do not use advertising or tracking cookies, and we do not use your generated content to train AI models.
Can our district sign a data processing agreement?
Yes — reach out and we'll work with your district. Because LessonDraft is data-light by design, agreements are straightforward.
Bringing LessonDraft to your school?
See how data-light design makes school-wide rollout simple — free for every teacher, with no student data to manage.
LessonDraft for Schools & Districts