{"resourceId":"nafaai-school-ai-privacy-standard-2026","versions":[{"version":"external-0f7ba3af5c24bc8dfb145808953ea3ebf21e019d27f09f5f9675e630644ef6d8","resource":{"id":"nafaai-school-ai-privacy-standard-2026","title":"School AI privacy agreement requires product-specific adoption and exception review","organization":"National Academy for AI Instruction; American Federation of Teachers; Microsoft","sector":"K–12 education","geography":"United States","publishedAt":"September 2026 version 1.0; announced September 9, 2026; signatures dated September 7","publicationDate":null,"eventDate":"2026-09-07","sourceName":"National AI Safety & Privacy Standard for Schools — Memorandum of Agreement","sourceLabel":"Negotiated standard and Microsoft-specific addenda","sourceUrl":"https://www.aft.org/sites/default/files/media/documents/2026/NAfAI-School_AI_Privacy_Standards.pdf","evidenceClass":"standards-guidance","outcomeClass":"emerging","topics":["knowledge-work","developers-agents","data-security","governance-procurement","accessibility-workforce","operating-model"],"finding":"The agreement offers districts an opt-in route to protections for defined educational products; general-purpose products are excluded.","sledRelevance":"Interpretation: The September 9 announcement creates a timely reason to review the precise terms covering a district's actual tools.","evidence":"Contract text, not an outcome evaluation. It includes a narrow safety exception to the training prohibition and controls for student action-taking features. No sample, baseline or demonstrated reduction in harm.","architectureImplications":"Interpretation: Map each licensed feature to identity, data inputs and external actions before deciding which controls to test. Cloud, local and hybrid choices still require separate requirements.","governanceImplications":"Interpretation: Have the district's authorized reviewers resolve scope and conflicting terms before representing a product as covered.","securityPrivacyImplications":"Interpretation: Test retention, deletion and external-action permissions using synthetic records; record exceptions and access to the supporting evidence.","caveats":"Addendum C records unfinished ISO 42001 assessment and specific Speaker Coach/Progress exceptions. District protection is not automatic or a universal legal guarantee. Exact PDF publication date is unconfirmed.","streamIds":["k12"],"roles":{"sales":"Interpretation: District procurement, technology and curriculum leaders may need to understand whether familiar products actually carry the promised protections. Ask which features are licensed, who can change their configuration, and whether the district has requested revised terms. A bounded engagement could compare one proposed classroom workflow with its agreement and produce a list of unresolved supplier questions. The value hypothesis is a clearer approval decision and fewer uncovered dependencies. This source establishes neither buying intent nor successful safety outcomes. Avoid describing a supplier relationship as blanket compliance or promising reduced incidents. Confirm the customer's own authority, renewal timing and review capacity before proposing work.","engineering":"Interpretation: Start with one authenticated classroom assistant and inventory its model, retrieval sources, memory and available write actions. Prerequisites include a named instructional purpose, a supplier data map and access to an isolated test tenant. Attempt unauthorized cross-class retrieval, changed retention settings and an external action that a student should not execute. Record the actual result and reviewer evidence. Include deletion and export tests with synthetic data. A useful proof of value joins instructional quality checks to permission tests; passing a contract review is insufficient. Do not infer a required hosting platform or allow an autonomous integration solely because a supplier has signed a standard.","delivery":"Interpretation: A district privacy lead should coordinate a staged release with curriculum, IT, procurement and school support staff. Establish the approved workflow, configure its controls and train teachers to identify inappropriate outputs and escalate failures. Dependencies include usable supplier evidence, staffed incident handling and accessible family communication. Proposed acceptance criteria: every pilot feature has a documented scope decision, all critical permission tests pass, and a deletion/export exercise has an accountable result before student access. Track review effort and unresolved issues through a dated continuation decision. These are proposed local criteria. Risks include supplier changes, incomplete exception records and staff assuming protections apply to unreviewed tools."},"retrievedAt":"2026-09-10T03:01:46Z","enrichedAt":"2026-09-10T03:04:22Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Interpretation: Include students using assistive technology and staff review time in the pilot; documentation alone cannot demonstrate usable access.","procurementImplications":"Interpretation: Request a product-specific written coverage statement and a priced assurance/exit plan before renewal.","operatingModelImplications":"Interpretation: Procurement owns the agreement record, IT owns configuration, and curriculum and privacy leads approve classroom use.","updateExplanation":"New to all 151 archived resources reviewed at offsets 0 and 100; no existing canonical URL match. Newly relevant September 9 announcement led to inspection of the agreement rather than reliance on promotional claims.","sourceVerification":{"openedUrl":"https://www.aft.org/sites/default/files/media/documents/2026/NAfAI-School_AI_Privacy_Standards.pdf","referenceExcerpt":"Complying with some principles but not others is not compliance.","promptVersion":"sled-research-v3.1","model":null,"basis":"agent-reported inspection"}}}]}