Core delivery
Cloudflare, Inc.
Purpose: protected public network delivery, DNS, traffic routing, tunnel connectivity, and denial-of-service protection.
Data involved: network request information such as IP address, hostname, timestamp, protocol, and encrypted traffic in transit. Student screenshots and essays are not provided to Cloudflare for its own use.
Control: access is limited to service delivery and security. The school-facing application continues to enforce role and tenant boundaries.
Optional school integrations
Google LLC
Purpose: Google sign-in and, only when a teacher connects it, read-only Google Classroom course and roster synchronization.
Data involved: Google account identifiers, profile email, course identifiers, teacher and student roster information, and authorization tokens. Classroom Guardian does not request Gmail, Google Drive, or Google Workspace domain-administrator access.
Control: the integration is optional, uses limited scopes, and can be disconnected by the school.
Deployment-dependent infrastructure
Amazon Web Services, Inc. or Google LLC (Google Cloud)
Purpose: deployment-dependent storage, processing, backups, or service hosting where configured in the school’s signed order and data agreement.
Data involved: only the service data needed for the enabled workload. The selected provider and region must be recorded for each production school; the application does not treat both providers as active by default.
Aman With Code-operated mail service
Purpose: account, report, trial, and administrator-requested email delivery.
Data involved: recipient address, sender, subject, message body, delivery status, and message identifier. Student reports are sent only when the school enables and directs that feature.
Change control
Classroom Guardian will not add an external provider that processes student personal information for its own advertising or unrelated commercial purpose. Material provider changes must be reviewed, added to this schedule, and communicated as required by the signed school agreement before the provider receives school data.
Questions or objections may be sent to [email protected]. The operator’s verified postal address and phone number must also appear in the school’s direct COPPA notice; production readiness remains incomplete until those fields are configured.