This section of the white paper does not provide legal advice, and nothing in it should be read as a completed compliance determination. Every mechanism described is a proposed approach, offered for review by qualified counsel and the relevant regulators before any pilot handling real student or family data proceeds.
FERPA
FERPA governs both halves of the initiative, in different directions. K–12 School Contact is designed around FERPA’s district-defined, opt-out directory-information framework. Higher-education College and University Contact treat the adult student as the default rights-holder, consistent with FERPA’s transfer of rights at eighteen or postsecondary enrollment.
COPPA
COPPA is proposed to be addressed in K–12 through a front-end tokenization pattern, so vendors receive a scoped token rather than a student’s actual identity or record — offered as a mitigation pattern requiring review against COPPA’s specific verifiable-parental-consent requirements, not a claim of current compliance.
IDEA, Section 504, ADA, and State Law
A national student-identity system will necessarily touch special-education status and accommodation records for some students, and this paper flags that IDEA, Section 504, and the ADA apply and have not yet been reviewed against the proposed architecture. State student-privacy laws vary and are often stricter than federal law, so any national architecture must accommodate the strictest applicable state requirement in a given jurisdiction — a significant open design question. See our FAQ for more.