If your school has its own contract with Khan Academy, that separate agreement governs how student data is handled and takes priority over the standard terms of service when it comes to student information.
This analysis describes what Khan Academy's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
Students accessing Khan Academy through a school may have stronger data protections than general users, depending on what the School Agreement says, but those terms are not publicly disclosed in this document.
Students and parents using Khan Academy through a school or district cannot fully assess their data rights from this document alone, as the applicable terms are determined by a separate School Agreement that is not publicly reproduced here. Families concerned about student data should ask their school or district for a copy of the Khan Academy School Agreement.
Cross-platform context
See how other platforms handle School Agreement Data Carve-Out and similar clauses.
Compare across platforms →Monitoring
Khan Academy has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 10 platforms.
"If you are accessing the Service through a school or district that has entered into a separate agreement with Khan Academy (a 'School Agreement'), the terms of that School Agreement will govern Khan Academy's use of student data, and in the event of a conflict between these Terms and the School Agreement, the School Agreement will control with respect to student data.— Excerpt from Khan Academy's Khan Academy Terms of Service
REGULATORY LANDSCAPE: This provision directly engages FERPA, enforced by the Department of Education, which requires schools to maintain control over student education records and limits what third-party vendors can do with that data. The School Agreement framework positions Khan Academy as a school official or legitimate educational interest vendor under FERPA, which restricts its ability to use student data for non-educational purposes. State student data privacy laws (including SOPIPA in California and similar statutes in other states) may impose additional restrictions. GOVERNANCE EXPOSURE: High for institutional customers. The carve-out creates a dual-track data governance model where the School Agreement controls student data, but the terms do not disclose the content of School Agreements to parents or students. This opacity may create challenges for parental rights requests under FERPA and state laws. Districts should ensure their School Agreement contains explicit restrictions on secondary uses of student data. JURISDICTION FLAGS: California's SOPIPA, New York's Education Law 2-d, and similar state statutes impose operator-level restrictions on student data that apply regardless of contractual terms. Districts in these states should verify that the School Agreement complies with applicable state requirements. EU schools using Khan Academy may also need to assess whether the School Agreement satisfies GDPR controller-processor requirements. CONTRACT AND VENDOR IMPLICATIONS: Procurement teams at school districts should request and review the full text of the School Agreement before deployment, as this document governs the actual data rights applicable to student users. Key provisions to review include data retention, secondary use restrictions, breach notification obligations, and data deletion rights. The conflict-of-laws provision giving the School Agreement priority is operationally significant and should be verified in the executed agreement. COMPLIANCE CONSIDERATIONS: Districts should maintain copies of executed School Agreements and conduct periodic reviews to ensure they align with current FERPA guidance and applicable state law. Data mapping should distinguish between student data governed by the School Agreement and general user data governed by the standard Privacy Policy. Breach notification timelines and obligations under the School Agreement should be confirmed and incorporated into incident response plans.
Full compliance analysis
Regulatory citations, enforcement risk, and due diligence action items.
Free: track 1 platform + weekly digest. Watcher: 10 platforms + same-day alerts. No credit card required.
Professional Governance Intelligence
Need to monitor specific governance provisions?
Professional includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.
Built from archived source documents, structured governance mappings, and historical version tracking.
Students accessing Khan Academy through a school may have stronger data protections than general users, depending on what the School Agreement says, but those terms are not publicly disclosed in this document.
Students and parents using Khan Academy through a school or district cannot fully assess their data rights from this document alone, as the applicable terms are determined by a separate School Agreement that is not publicly reproduced here. Families concerned about student data should ask their school or district for a copy of the Khan Academy School Agreement.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Khan Academy.