Public school readiness
K-12 privacy and procurement evidence map
Public school review is strongest when every compliance claim maps to a document, workflow, owner, or district-specific agreement. This matrix shows where reviewers should look first and where the institution remains the records custodian or decision-maker.
Review boundary
This hub is procurement and product documentation. It is not a legal opinion, district policy, or a substitute for the school's FERPA, COPPA, IDEA, state-law, or contract determinations.
Parent and eligible-student records requests
Institution-led workflowDistricts remain the records custodian. Classroom Pulse should support routing, exports, and response evidence for institution-managed access and amendment requests.
Student record access and disclosure evidence
Product evidence pathDistrict administrators need reviewable event history for student-record access, exports, disclosures, and emergency releases without overstating FERPA disclosure-log rules for internal school officials.
COPPA school authorization and third-party notice
Documented review pathSchool-managed child privacy review should keep authorization records, surface third-party categories or names, and separate integral service providers from non-integral disclosures.
Texas and state student-data commitments
Contract review pathDistrict reviewers need plain attestations for no targeted advertising, no sale of student data, deletion support, breach support, and state or district addendum routing.
Deletion, destruction, and termination evidence
Contract workflowPublic schools commonly require deletion-on-request workflows, termination handling, and data-destruction certificates through the DPA or district privacy addendum.
Incident and breach response support
Operational supportDistricts need fast incident evidence: affected data, affected students or users where known, notification contacts, timelines, and exportable materials for local reporting duties.