Retention & deletion
Retention and deletion.
Align retention to your jurisdiction: academic records, finance, communications, and logs have configurable policies per module.
Who sets the period
Retention is configurable per kind of data, so a school can align it to its jurisdiction. The period for a kind of data is resolved in this order:
- the school's own setting;
- an override set by the platform operator;
- the platform default, which is chosen to keep data longer rather than shorter.
A period of zero means keep, never purge. A student-data period below the platform's minimum is refused, never applied.
Archive first, then purge
- Nothing is deleted that was not first copied into a verified archive.
- Records under a legal hold are excluded, whether the hold is on a kind of data or on a single student.
- Student data covered includes attendance, discipline incidents, health records, and returned library loans.
A report before any deletion
A scheduled retention report counts what a real run would erase, and erases nothing. It is off until an operator turns it on. When it finds something eligible, it writes one append-only audit record so the owner can see what a real run would take before deciding to run one.
End of contract
School data is exported and the school's workspace is torn down on the schedule in the contract. Subprocessors are notified as the data processing agreement requires. Exports can carry an integrity hash so a regulator can check the file is the one the platform generated.