Security & Trust

Built like student data depends on it. Because it does.

Schools hand us the records of children. We treat that as the design constraint for everything, not a checkbox at the end. This page says plainly how the platform protects what you give it.

Tenant isolation, enforced in the database

Every district lives in its own walled data space. Isolation is enforced by row-level security policies in the database itself, on every tenant table, and our test suite fails the build if a new table ships without its policy. It is not a filter an application bug can forget.

FERPA-scoped access

Access follows role and building. A teacher sees their own students, a counselor sees their caseload, and building staff never browse another building's children. Sensitive records carry their own visibility controls on top.

Student safety in the workflow

Employers are school-vetted before a student ever sees a posting. Adult contact with students runs through school-mediated channels, never a private back door. Family app access is verified per household and scoped to each family's own students.

An immutable audit trail

Every approval and status change records who, when, and what. Failed sign-in attempts are logged. The audit system never records request contents, so passwords and sensitive fields cannot leak into logs. History survives staff turnover.

Nothing hard-deleted

Records are retired, never destroyed. When someone asks what happened here, the answer exists. Deliberate retention controls let districts prune on their own schedule, never by accident.

Your data stays yours

The district owns its data, full stop. CSV and PDF exports are built into the screens staff already use, and a complete export is available on request. No hostage data, ever.

Operating practices

  • Hosted on AWS in the United States
  • Encrypted in transit everywhere, on every page and API call
  • Daily infrastructure snapshots and nightly database backups, privately stored with bounded retention
  • Least-privilege service roles for backups and integrations
  • Rate limiting on public endpoints; uploads validated and scanned by type
  • Student-data privacy agreement (DPA) available on request