School and district agreements
Updated October 2, 2026
National protections, local requirements
The platform baseline prohibits student-data sales, targeted advertising, commercial profiling, and unrelated AI training. State and district requirements add protections. Each class has a school, district, state, authorization reference, retention instructions, and review date. Selecting a state does not automatically implement every state law.
Before real student use
The school and operator must establish the permitted educational purpose, record categories, authorized users, school control, disclosure limits, provider restrictions, retention and return/deletion process, incident contacts and deadlines, and applicable parental rights. Review actual provider contracts and security practices. A class code is not approval.
Agreement review process
Contact Kendrick Broadus at support@masteritrail.com to coordinate the school’s required agreement through an approved secure channel. The platform owner records the agreement reference in School privacy settings and related evidence in Privacy administration. No pre-signed state agreement, SDPC membership, district approval, or privacy certification is claimed.
Under-13 release requirements
School-managed provisioning is gated on school authorization, published operator contacts, current provider-review evidence, and documented manual verification of direct notice and consent. The operator must establish the actual identity-verification procedure, signed permissions, purpose-bound retention, and provider obligations. Consent can be withdrawn to block access. Recording a design review alone does not enable enrollment.