Last updated: April 7, 2026
Celerity is built for K-12 education. Compliance with federal and state student data privacy laws is foundational to how we design, build, and operate the platform. This page provides a central reference for our compliance posture, key documents, and the frameworks we follow.
Celerity operates as a "school official" under 34 CFR §99.31(a)(1), processing education records on behalf of districts under a legitimate educational interest. Our Data Processing Agreement formalizes this relationship, including:
Celerity does not collect personal information directly from children under 13. Schools and districts provide consent under the COPPA school consent exception. Our platform enforces data minimization and prohibits any commercial use of student data.
Celerity maintains compliance with state-level student data privacy statutes. Our DPA and platform controls are designed to satisfy the requirements of the following frameworks:
| State | Law | Status |
|---|---|---|
| Texas | HB 2087 (Student Data Privacy) | Compliant |
| California | SOPIPA (Student Online Personal Information Protection Act) | Compliant |
| New York | Education Law 2-d | Compliant |
| Colorado | Student Data Transparency and Security Act | Compliant |
| Illinois | SOPPA (Student Online Personal Protection Act) | Compliant |
| Connecticut | PA 16-189 (Student Data Privacy) | Compliant |
Additional states will be added as Celerity enters new markets. Contact us if your state has specific requirements.
Celerity has signed the SDPC National Student Data Privacy Agreement, a standardized framework recognized by school districts nationwide. This streamlines procurement by providing a pre-negotiated DPA that districts can adopt.
Student data flows through the Celerity platform as follows:
District SIS / Data Source
|
v
Keycloak (Authentication)
OIDC / SAML 2.0 — identity verified
|
v
PostgREST API (Authorization)
JWT validated — tenant scope enforced
|
v
Tenant Schema (Isolation)
Schema-per-tenant + row-level security
|
v
Amazon RDS (Storage)
AES-256 at rest — TLS 1.2+ in transit
US-only data residencyEach tenant's data is isolated at the database schema level. Cross-tenant access is architecturally prevented by row-level security policies enforced at every query.
| Classification | Examples | Handling |
|---|---|---|
| Education Records (FERPA) | Grades, enrollment, assessments, IEP data | Encrypted, tenant-isolated, access logged, no commercial use |
| Personally Identifiable Information | Student names, IDs, dates of birth, contact info | Encrypted, access restricted to authorized roles, never in logs |
| Directory Information | School name, grade level, enrollment status | Treated as PII unless district designates otherwise |
Celerity will never:
Under FERPA, parents and eligible students have the right to inspect and review education records. Celerity supports this process:
The following compliance documents are available. Per-customer agreements (DPA, MSA) are provided during onboarding and are accessible through the customer portal.
| Document | Access |
|---|---|
| Privacy Policy | Public |
| Security Practices | Public |
| Acceptable Use Policy | Public |
| Responsible Disclosure Policy | Public |
| Data Processing Agreement (DPA) | Customer portal |
| Master Service Agreement (MSA) | Customer portal |
| Service Level Agreement (SLA) | Customer portal |
Compliance inquiries: privacy@celerityedu.com
Security inquiries: security@celerityedu.com
