Primary use
District and school review
Best for procurement teams, legal reviewers, privacy leads, and technology buyers.
This page packages the public trust materials most often requested by schools, districts, and procurement reviewers. Use it for internal handoff, print-to-PDF workflows, or to route legal and security review.
Primary use
District and school review
Best for procurement teams, legal reviewers, privacy leads, and technology buyers.
Delivery options
HTML, PDF, and CSV
Download the public packet PDF, security summary PDF, or the current subprocessors CSV.
Escalation path
Structured intake
Use the contact workflow to request a signed DPA, state addendum review, or security questionnaire support.
These are the public materials most often requested during buyer review. Each item reflects the current public date shown in the Trust Center.
HTML + PDF download
Printable trust overview with procurement contacts, core documents, security review notes, and state addenda workflow.
Open documentHTML
Processor and service-provider terms for school, district, and institutional review.
Open documentHTML + PDF download
Operational controls, incident handling, and security review notes.
Open documentHTML + PDF download
Overview of product, website, billing, and student-related data handling.
Open documentHTML + CSV download
Service providers used for application delivery, AI processing, billing, email, and monitoring.
Open documentHTML
Overview of state-specific addendum workflows and what districts should send for review.
Open documentService providers support application delivery, authentication, storage, and other operations. Processing locations depend on the service and configuration.
Review the Subprocessors page and request location details for your proposed use. Applicable customer agreements govern any agreed location restrictions.
Encryption is part of the security review for data in transit and stored records. Request the current control scope for your proposed use.
Use the Security Practices page and applicable agreement for the contractual summary. A reference to a security framework is not a certification or independent attestation.
Authenticated accounts, role-based permissions, and need-based administrative access are used to limit access to customer workspaces and support tools.
Google and email-based sign-in paths are supported in the current product stack.
Google Sign-In and email-based sign-in are available to all users today, alongside CSV roster import/export for bulk setup. Enterprise SSO (SAML/OIDC), SCIM provisioning, and automated roster sync (Clever/ClassLink) are not currently available.
Districts with specific identity or roster-sync requirements can raise them through the security review intake so we can share current roadmap status; these integrations are not part of the shipped product today.
Classroom Pulse is designed to operate as a "school official with a legitimate educational interest" under 34 CFR § 99.31(a)(1)(i)(B) when engaged by a school or district. Behavior records, FBA artifacts, and AI-assisted outputs are processed only to provide the service; student data is never sold or used for advertising.
See the FERPA page for the full disclosure framework and the DPA for contractual scope. Customers retain control of student records and remain the educational agency of record.
Operational logging and monitoring support service health review, abuse detection, troubleshooting, and incident investigation.
Logs are used for operational security and support workflows, not targeted advertising.
Backup and restoration requirements should be reviewed for the proposed service and customer agreement.
Schools with stricter continuity requirements should request contract language or questionnaire support through procurement intake.
Confirmed incidents affecting customer personal data are investigated, contained, and notified without undue delay when required by law or contract.
Customer-specific agreements may impose narrower timeframes or additional notice obligations.
The Subprocessors page describes service providers and their purposes. Applicable agreements govern confidentiality and data protection obligations.
The public subprocessor list is intended for vendor due diligence and contract routing.
District and state templates often supplement the public DPA. Send the actual exhibit or district form with a deadline so the request can be routed correctly.
| State or program | Framework | Typical artifact | Notes |
|---|---|---|---|
| New York | Education Law 2-d and district privacy exhibits | District student data privacy addendum or state exhibit | Provide the district template or required exhibit and the legal review timeline. |
| Illinois | Student Online Personal Protection Act and local district addenda | District-specific SOPPA or student data addendum | Districts often request a local exhibit even when a public DPA already exists. |
| California | State student privacy terms and district purchasing addenda | District privacy addendum or services agreement attachment | Share the district paper and any required incident notice or deletion clauses up front. |
| Texas | Texas Education Code Chapter 32 student data privacy provisions and district purchasing addenda | Texas Student Privacy Alliance (TX-NDPA) agreement or district-specific addendum | Send the TX-NDPA or district exhibit; note that Texas Public Information Act obligations may apply to the district side of the correspondence. |
| Other U.S. states | District or cooperative purchasing templates | State-specific or district-specific addendum | Classroom Pulse can review state and district forms through the procurement intake workflow. |