Hub

Compliance

The two questions every district asks before the demo: what does it report, and how does it handle our data.

Direct answer
Edves covers ESSA accountability reporting and operates under FERPA, COPPA, PPRA and state student data privacy requirements.

ESSA subgroup reporting is generated continuously from operational data rather than compiled annually. Student data is not used to train general-purpose AI models, the district retains ownership, and full export is available at any time including at termination.

Reporting

  • ESSA reporting — achievement, growth, graduation, English learner progress and school quality indicators, disaggregated by subgroup and available year-round rather than in a summer export.

Privacy

  • FERPA & student data privacy — school official status, field-level role scoping, audit logging, retention configuration, COPPA consent workflows, state data privacy agreements, and the specific contractual position on AI model training.

The question worth asking first

A vendor that talks only about FERPA has described the least restrictive layer. State student privacy statutes are frequently more demanding, and many states and consortia maintain a standard data privacy agreement they expect vendors to sign without amendment. Ask about that agreement before you ask about features — it filters more vendors than any other single question.

Related

AI in education sets out an adoption sequence that survives a privacy review. Choosing school software lists the privacy questions to put to any vendor, including this one.

See it run on your own standards.

A 20-minute walkthrough using your state’s standards, your evaluation framework and your reporting requirements.

Schedule a demo

Keep reading