Skip to content
LEAPDocs
2026.08

Data retention

What is kept, for how long, and what is deliberately preserved rather than deleted.

What is retained

Academic recordEnrolments, attempts, marks, mastery and attendance. Retained for the institution’s reporting and audit period — this is the evidence accreditation depends on.
Course contentSyllabi, gates, lessons, questions and materials. Retained for the life of the course and its clones.
Recordings and transcriptsRetained per institution policy. Source audio is released once assembly and checksum verification confirm the upload.
Scanned scriptsRetained with the attempt so a mark stays auditable against the page it came from.
Proctoring flagsRetained with the attempt. Any stored capture is per-tenant encrypted and purged on schedule.
Voice feedbackTranscripts retained with the batch; audio per policy.

Preserved rather than deleted

Several operations that look like deletions are deliberately not. Withdrawing a student ends the enrolment but preserves their earlier work; moving a student between sections records the movement rather than overwriting it.

This is intentional. An academic record with holes in it cannot be audited, and a student who leaves and returns should not restart from zero.

Deletion

Institution deletion removes that tenant’s data and is irreversible in practice. Individual record deletion is deliberately narrow, because the academic record is the product.

Data minimisation

  • Proctoring analyses on-device and transmits observations, not media.
  • Gmail integration requests send permission only — LEAP never reads a mailbox.
  • Objects are served through the application rather than from a public bucket.
  • Tokens are redacted from logged URLs.