Jump to a section
Related resources
Buyer-facing trust packet with printable procurement support materials.
Processor and procurement terms for institutional reviews.
State and district addendum workflow support.
How to report vulnerabilities responsibly.
1. Security model
Security review covers the controls and responsibilities relevant to customer, account, and student-related data.
Review areas include
- Account access and permissions
- Logging, service monitoring, and incident handling
- Provider services, data locations, and recovery requirements
Request the current control scope for your proposed use and any requirements that need to be included in your agreement.
2. Buyer review matrix
This matrix is intended for procurement and questionnaire review and should be read together with the DPA and Subprocessors pages.
| Review area | Current practice | Buyer note |
|---|---|---|
| Hosting and data location | Service 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 | 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. |
| Authentication and access | 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. |
| Sign-in and rostering | 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. |
| FERPA alignment | 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. |
| Monitoring and logging | 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 recovery | 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. |
| Incident notice | 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. |
| Vendor management | 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. |
3. Access, monitoring, and vendor controls
Security depends on both platform controls and operational practices that limit how access is granted and how events are investigated.
- Administrative and support access is restricted based on need and role.
- Operational logging supports service health review, abuse detection, troubleshooting, and incident investigation.
- The Subprocessors page lists service providers and their purposes to support vendor due diligence.
- Systems and dependencies are updated as part of ongoing maintenance and risk management work.
4. Incident response and external reporting
If Classroom Pulse identifies a security event affecting customer personal data, the team works to investigate, contain, and remediate the issue.
When required by law or contract
- Affected customers are notified without undue delay
- Available details are shared to support response planning
- Follow-up remediation steps are tracked internally
Security researchers can report issues through the Vulnerability Disclosure Policy, and customers can route questionnaires or security review requests through the structured intake flow.
Questions or documentation requests
Use the structured intake for security questionnaires, architecture review, incident-related questions, or responsible disclosure follow-up.
Security intake
Open security review intakeSecurity email
security@classroompulse.ioDisclosure policy
View the vulnerability disclosure policy