← Back to EasyEdForm

Privacy, Data Handling & FERPA Alignment

Status: independent teacher tool — not yet under a district-executed data privacy agreement

This page is written for school administrators, IT/data-privacy reviewers, and anyone evaluating EasyEdForm for use with student records. It explains exactly what the tool does with data, what it never does, and what would need to happen before any formal district integration (ECATS, PowerSchool, Google Classroom).

What EasyEdForm is — and isn't

EasyEdForm is a drafting aid that helps a teacher turn spoken or typed notes into well-structured, measurable language for Section 504 Plan and IEP documentation, aligned to the sections NC DPI's ECATS system and OCR/IDEA reviews expect. It is not a system of record: nothing drafted here is official until a human — the IEP or 504 team — reviews it and enters it into ECATS. It currently has no live connection to ECATS, PowerSchool, or Google Classroom.

Data we collect vs. never collect

✅ What is sent to draft a form

  • A student token or initials only (typed by the teacher — the tool never asks for or accepts a legal name, DOB, or address)
  • The teacher's spoken/typed notes about needs, accommodations, and services
  • The current in-progress draft text of the form fields, so the assistant has context

🚫 What is never collected

  • Legal student name, date of birth, address, or student ID number
  • Any login, account, or persistent user profile
  • Any data written to a database — EasyEdForm has none
  • Any audio recording saved to disk (speech is transcribed in the browser and discarded)

How the AI drafting works

When a teacher speaks or types a note, the note and the token/initials are sent over an encrypted (HTTPS/TLS) connection to a language model to draft form language. Depending on availability, this is one of: Anthropic Claude, OpenAI, or Google Gemini. Speech is converted to audio replies using ElevenLabs or OpenAI's text-to-speech. Each of these is a standard API call — none of them are given a name, are told this is student data, or receive anything beyond the token and the note text.

These providers' standard API terms generally exclude API inputs from being used to train their models, but terms vary by account tier — a free-tier key can carry different data-use terms than a billed one. Every AI provider used by EasyEdForm is on a paid, billed account. Before any formal district approval, each subprocessor's data-use terms will be reconfirmed in writing, and any provider whose tier doesn't meet that bar will be removed.

Data retention & storage

Security measures

FERPA alignment

FERPA compliance is ultimately the school district's obligation, and it depends on the district maintaining "direct control" over any vendor handling education records under a signed agreement. EasyEdForm is built to minimize risk in the meantime — no legal names, no persistent storage, no third-party sharing beyond the drafting AI call described above — but it does not yet have a signed data privacy agreement with any district, and should be treated as a personal productivity aid until one is in place, not an approved district system.

Path to formal North Carolina district approval

To move from "personal teacher tool" to an approved, integrated system (ECATS, PowerSchool, Google Classroom), North Carolina districts generally require:

None of these have been executed yet. This page will be updated as that changes.

Contact

Questions about data handling or interest in a formal data privacy agreement: EasyEdForm — [contact email to be added]