Security
The main technical and operational controls used to protect agency and student data.
Version 2026-10-10
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
Platform-hosted document files are stored privately and accessed through short-lived signed URLs. Document downloads are authorized server-side and access attempts are audit logged. Imported legacy files may remain with the original provider until migrated; their protection also depends on that provider.
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
Authorized managers can use erasure workflows. Retention mechanisms require approved periods, configuration, and verification of scheduled execution before automatic deletion can be relied on. During the pilot, scheduled retention is not confirmed operational. Failed storage cleanup requires follow-up; a partially completed erasure is not complete file deletion.
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.