Student Data & FERPA
Effective November 4, 2026 · Last updated November 4, 2026
This page states plainly what the Service does with data, so a teacher, a principal, or a district technology office can check it without reading a contract. It is the student-data statement referenced by our Privacy Policy.
What we never collect
- Student names, initials, or email addresses
- Class rosters, seating charts, or student IDs
- Grades, scores, progress records, or assessment results
- Student writing, submissions, or drafts
- IEP, 504, or other special-education records
- Any other education record tied to an identifiable student
The Service has no student logins and no student-facing pages. There is no feature that asks for student information, and none of the generated handouts are keyed to a student.
What we do store
- Your account: name, email, password hash, and preferences.
- Your teaching context: class sections, their grade and level, lesson inputs, and the standards you select.
- Your content: the texts you upload, the plans written from them, and the handouts and PDFs rendered from those plans.
- Operational records: credit entries, job status, and support messages.
FERPA
FERPA governs education records maintained by a school or a party acting on its behalf. Because we do not receive student education records, we do not act as a school official and no education record is disclosed to us. If your district's process requires a written agreement before staff may use a tool, contact us and we will provide a data processing agreement or a signed copy of this statement.
COPPA and children
The Service is sold to adults. Children do not have accounts and do not interact with the Service, so we do not knowingly collect personal information from anyone under 13.
What teachers should not paste
Generated plans cite passages from the text you supply, and student writing is not needed for that. Do not paste student work, names, or identifying details into a lesson, a support ticket, or an upload. If you need a handout to refer to a specific student, use the student's own copy rather than a name.
Where the data lives
Content is stored on servers in the United States with our hosting provider. Text you supply is sent to our AI model gateway only to draft the plan you asked for. Email is delivered through our mail provider. Payment details are held by our payment processor, not by us.
Retention and deletion
Your content stays while your account is open. You can delete a lesson or a source text at any time; deleting an account removes your data from the live system, and it leaves backups within 30 days. Credit ledger entries remain while the account exists because they are the accounting record.
Security
HTTPS everywhere, hashed passwords, tenant-scoped queries, and restricted production access. We will notify you if a breach affects your data, as the law requires.
Questions a district usually asks
| Is student data collected? | No. There is no field, feature, or integration that stores it. |
|---|---|
| Do students create accounts? | No. Only teachers do. |
| Is data sold or used for advertising? | No. There are no advertising or analytics cookies. |
| Where is it hosted? | The United States. |
| Do you train models on our content? | No. We send text to a model provider to draft your plan; we do not train models ourselves. |
| Can we get a DPA? | Yes, on request: support@lessonplanfactory.com. |
| What happens when we leave? | We delete your account data on request; backups age out within 30 days. |
Contact
Student-data questions: support@lessonplanfactory.com. Lesson Plan Factory, West Virginia, United States.
← Back to Lesson Plan Factory