Jump to a section
Related resources
How information is handled across the product and website.
How the platform supports school-controlled education records.
Contractual processing terms often reviewed by districts and schools.
Primary vendors used for hosting, billing, and transactional operations.
Operational data lifecycle and deletion workflow overview.
1. Classroom Pulse is built for adult-managed use
Classroom Pulse is designed for educators, administrators, specialists, and other authorized adults. Students do not create independent Classroom Pulse accounts.
That design supports a school-managed workflow in which institutions decide what information is entered, who may access it, and how parent communications are handled.
2. Limited collection and use
Classroom Pulse collects only the information needed to operate the service and support educational workflows.
Key commitments
- No direct child sign-up flow
- No targeted advertising based on student data
- No sale of student information
- No unnecessary collection of personal data from children
3. School and parent roles
Schools and districts are responsible for determining when school authorization, parental notice, or parental consent is required in their environment.
Parents and guardians typically access or correct student-related information through the school or district that controls the records, unless directed otherwise through a specific support process.
For public school use, the authorization trail should identify the approving institution, covered product use, data categories, parent-notice path, and any district-specific limits on collection, use, disclosure, or retention.
4. Safeguards and commercial boundaries
Classroom Pulse applies access controls, security practices, and contract limits to help protect student information.
In addition
- Student data is handled for educational workflows, not marketing
- Commercial subscription and billing workflows are handled separately from student account access
- Procurement reviews may request supporting privacy, security, and DPA documentation
5. Third parties, retention, and non-integral disclosures
School COPPA review should be able to answer three questions without hunting through unrelated documents
- Which third parties or categories of third parties receive child-related data to operate the service
- How long child-related data is retained and how deletion requests are handled
- Whether any disclosure is not integral to the service and therefore requires separate authorization before use
Classroom Pulse publishes a subprocessor list and data-protection overview to support that review. District-specific agreements may add stricter notice, objection, deletion, or retention terms.
Questions or documentation requests
Questions about child privacy, school-managed consent, or parent access workflows can be sent to the privacy team.
Mailing address
Classroom Pulse, 5435 N Garland Ave Suite 140-127, Garland, TX 75040, United States