Methodology

How We Vet AI Tools

Every assessment follows the same five-step research methodology. Here is exactly what we look at, how we reach our verdicts, and what those verdicts do — and don't — mean.

Important context: No AI tool can be "FERPA certified." FERPA applies to schools, not vendors. As former U.S. Department of Education officials have stated, there is no such thing as a FERPA seal of approval. Our assessments evaluate whether a tool can be used in a FERPA-compliant manner with proper district configuration, agreements, and controls. Compliance responsibility always remains with the district.
Step 1
Privacy policy review

We read the vendor's full privacy policy for clauses relevant to K-12 student data. Generic consumer policies are common — we look specifically for education-specific terms that address the requirements schools actually face.

Step 2
SDPC agreement status check

The Student Data Privacy Consortium (SDPC) maintains a registry of vendors who have signed standardized Data Privacy Agreements. A vendor who has signed with the SDPC has made specific, auditable commitments on student data handling. We check the SDPC registry directly for every tool.

Step 3
DPA availability and terms

A Data Processing Agreement is the legal contract establishing school control over student data. We assess whether a district-friendly DPA exists and whether its key terms are reasonable.

Step 4
District admin controls

Compliance on paper only holds if the district can manage it in practice. We evaluate what tools districts have to configure, monitor, and audit AI tool usage.

Step 5
Public record and Common Sense Media

We cross-reference Common Sense Media privacy ratings, any documented data incidents or enforcement actions, and public reporting on the vendor's privacy track record.

Verdicts
What our verdicts mean

Every assessment produces one of three verdicts. These are research findings, not legal certifications.

✓ Suitable

The tool has the compliance infrastructure to support appropriate district use. A DPA is available, data practices are transparent, and district controls exist. A signed DPA is still required.

⚠ Conditional

The tool can be used appropriately, but only under specific conditions — specific versions, specific configuration, or restricted use cases. Read the full assessment before proceeding.

✗ Not Appropriate

The tool creates FERPA or COPPA exposure that cannot be mitigated through configuration alone. Avoid using with any student data.

Sources
Where we look

⚠ Research only — not legal advice

K12SafeList assessments are independent research findings. They do not constitute legal advice, FERPA certification, or any guarantee of compliance. Privacy policies and product terms change frequently. Always verify current documentation directly with the vendor before procurement decisions. Consult your district's legal counsel for guidance specific to your jurisdiction.

Browse the tool directory →