Security
The main technical and operational controls used to protect agency and student data.
Version 2026-07-12
Tenant isolation
Every agency is separated by database-level row-level security. Tenant and role claims come from authenticated server-side session data, not client input.
Document protection
Document files are stored privately and accessed through short-lived signed URLs. Document downloads are authorized server-side and sensitive access is audit logged.
Access control
Staff, manager, and participant roles are separated. Students can access only their own portal data. Manager-only workflows, such as erasure and finance views, are separately gated.
Retention and erasure
The codebase includes right-to-erasure workflows and a document retention purge path. Operational retention periods should be finalized in the legal/compliance pack and agency agreements.
Incident response
Security incidents should be triaged immediately, access should be contained, affected controllers/agencies should be notified, and breach-notification obligations should be assessed using the breach runbook.