// playbook 03 · trust

Passing a district privacy review without stalling your pilot

For founders and product leads

Most edtech pilots don't stall in the classroom. They stall in a district inbox, waiting for someone to approve a data privacy agreement. This playbook is how we help teams get ready before that email arrives.

1. What reviewers actually ask

District reviewers usually want to know three things: what student data you collect, where it goes, and who can see it. If you answer those clearly on one page, most of the follow-up questions go away.

CHECKLIST
  • A one-page data map: every field, why you need it, how long you keep it
  • A plain statement on whether student data trains any AI model
  • A signature-ready data privacy agreement for your target states

2. Build your data map first

[Body copy to be written.]

3. FERPA, COPPA and state laws

[Body copy to be written.]

4. AI-specific questions

[Body copy to be written.]

Want us to work through this with you?A working session with our team, tailored to your product.
Book a session