Trust, continuously verified
Most products assert their data protections once a year in a PDF. Ours are checked live against the running system — row-level security, write-protected forensic tables, immutable audit logs, pseudonymized admin views, and more. What you see below is the current state, not a promise.
Live compliance checks
Row-level security on student tables
Last verified: 2026-10-25Every row in every student-scoped table is filtered to its owning teacher on read and write.
Forensic tables write-protected from client
Last verified: 2026-10-25Analysis output is written only by trusted server code; the client cannot mutate audit or scoring rows.
Pseudonymized admin views
Last verified: 2026-10-25Platform and school admin surfaces show anonymized identifiers; real names are gated behind a justification-logged reveal.
Immutable audit logs
Last verified: 2026-10-25Reveals, exports, and privileged operations are recorded to an append-only log.
Google tokens isolated from the client
Last verified: 2026-10-25OAuth tokens are stored server-side; the browser never receives them.
Encryption in transit (TLS 1.2+)
Last verified: 2026-10-25All traffic between browser, application, and database uses modern TLS, provided by our hosted infrastructure.
Encryption at rest (AES-256)
Last verified: 2026-10-25Stored student writing and metrics are encrypted at rest on the hosted database and storage layer we run on.
No AI training on student work
Last verified: 2026-10-25Submissions are analyzed, never used to train any model. This is contractually enforced with our AI provider under their API terms.
Self-serve export and deletion
Last verified: 2026-10-25Teachers can export class data or permanently delete it from the dashboard. Deletes are immediate on the live database; encrypted backups age out on the standard 7-day point-in-time recovery window.
Questions about any control? For Admins & IT → • Data Processing Addendum →