Student data & privacy
Built to keep student data out of it.
The most common question we get from teachers — and the first thing a district asks — is "where does my students' information go?" The honest answer: nowhere, because the Teacher Pack is designed so it never needs a single student's name or record in the first place. Here's exactly how that works.
The wizard never asks about an individual student
When you build a Teacher Pack, the wizard asks for the categories of accommodations your class needs — not names, not cases, not records. The field is labeled in the tool itself: "Categories of students you accommodate (no names, no individual info)," and it asks you to describe the types of needs using patterns and percentages.
So the context baked into your skill reads like "a portion of the class needs sentence frames for language support" — never "Marcus has an IEP for…". Categorical context also happens to make better lessons: it works for the whole class and for next year's students, not just one child.
In everyday use, the skill strips names out for you
Even if you paste a real name into a prompt — "write a reteach plan for Marcus, who didn't get rounding" — the skill is instructed to replace it with a [Student] placeholder in whatever it produces. You fill real names back in inside your own systems, where they belong. The Pack's built-in rules are explicit about this:
- Never put a real student name in the output.
- Never repeat specific student details tied to an identifiable child — convert them to categorical language instead.
- Never invent student stories ("a student like Sarah with anxiety…") — always generalize to the need, not the person.
- Run a name-and-PII check before returning anything.
Serious situations go to a human, not a draft
If a prompt describes something safety-critical — suspected abuse or neglect, self-harm, an immediate risk, anything CPS-reportable — the skill is built to stop and point you to your counselor or admin rather than generate a document about it. A wizard-built skill is the wrong tool for those moments, and it says so.
Where your information actually lives
The skill we deliver runs inside your own Claude account — we're not in the middle of your day-to-day chats. On our side, the reference documents you upload (a district pacing guide, say) are deleted from storage about 90 days after your skill is built. We don't sell your data, we don't run ad trackers, and we don't use your uploads or answers to train any AI model. The full detail is in the privacy policy.
One thing to know: if you use the wizard's optional "draft this for me" AI helper, the text you typed into that field is sent to Anthropic's API to generate the suggestion. Since you never enter student PII into the wizard, that stays category-level too — and if you fill the wizard in by hand, nothing is sent anywhere.
The honest FERPA answer
The Teacher Pack is built with FERPA and state student-data laws in mind — the whole design goal is that student PII never has to enter the tool. But we want to be straight with you: this is a privacy-by-design product, not a legal certification, and we can't sign your district's data-privacy agreement on behalf of a decision that's yours to make. You (and your district) remain the steward of student records. What we can promise is that the tool is engineered to keep those records out of scope, and that we'll answer any specific question a privacy officer has.
For administrators vetting this
If you're reviewing KnackPack for a school or district and need specifics — our sub-processor list, data-retention details, or answers for a privacy review — email [email protected] and we'll get you what you need.