Jump to a section
Related resources
Contract processor terms that govern customer-directed personal data.
Operational security and incident handling practices.
Printable buyer-facing packet with the core trust review materials.
District and state-specific addendum workflow support.
How personal and student-related data is handled more broadly.
1. How to use this list
This page identifies the primary subprocessors Classroom Pulse uses to operate the service.
It is intended to support procurement, privacy review, and vendor due diligence. The applicable DPA, order form, or signed agreement controls if it differs from this public summary for a specific customer.
2. Current subprocessors
These are the primary third-party processors involved in infrastructure, billing, and transactional communication delivery.
| Subprocessor | Purpose | Location |
|---|---|---|
| Google Cloud / Firebase | Application hosting, authentication, database storage, and backups | United States |
| Stripe | Subscription billing, transaction handling, and fraud controls | United States |
| Resend or comparable email infrastructure | Transactional email delivery requested by the customer or required to operate the service | United States |
3. Change notices and requests
Classroom Pulse may update this list as infrastructure or operational needs evolve.
When changes are material
- We may update this page
- We may notify customers through the DPA, contract workflow, or written notice where appropriate
- Customer-specific agreements may include additional notice or objection procedures
For signed copies, questionnaires, or procurement requests, use the structured procurement intake or contact legal@classroompulse.io.
Questions or documentation requests
Use these contacts for vendor questionnaires, signed DPAs, or school and district review support.
Vendor review intake
Open procurement review intakeSecurity
security@classroompulse.io