LMS Data Retention After a Course Ends
A plain-language guide to lms data retention after a course ends: the record, the purpose, the authority and the safeguard.
- Record
- learning record in lms platforms and learning data
- Data
- LMS Data Retention After a Course Ends
- Safeguard
- role-based access and retention tied to the course term
- First check
- Check that the recipient is bound to use the data only as agreed.
The short answer
Put merely, lms data retention following a course ends is about control over an education record that belongs, in a practical sense, to a student and is retained in trust by an university. The university might use it for the purpose it was collected for, share it where the law or a valid consent permits, and must protect it everywhere else. Everything in this guide is a way of making that sentence workable at a desk, stage by stage.
AI tutors used by younger students raise both COPPA and FERPA issues, and both analyses must be done before the pilot, not following it.
Role alters must trigger access reviews, or former access quietly becomes current risk.
Audit findings that are never tracked to closure are worse than no audit, because they prove the institution knew and did not act.
Support employees access to live records is a sharing in substance, even when the vendor describes it as maintenance.
What this covers
Network logs hold connection information that can reveal student activity patterns, and access to those logs ought to be logged in turn.
Health and counseling platforms ought to be segregated from broad student platforms, with access limited to the staff who provide the care.
Video surveillance holds images of identifiable students, and its storage, access and disclosure rules should be documented before cameras are installed.
Platforms that feed directory information to outside directories need an opt-out verify built into the feed, not added as a manual afterthought.
Directory information is a defined subset that a college may designate and publish, and the designation must be published before it is relied on.
Cloud platforms do not change what counts as a file, but they change where copies live, and every copy needs the same governance as the original.
How to work through it
Delete on schedule, and make deletion verifiable, because a deletion that can not be shown is a deletion that shall be doubted.
Analyse outside survey requests separately from institutional surveys, since the authorization for one does not cover the other.
Plan for remote work explicitly, with controls that travel with the file to staff homes and personal devices.
Verify whether a course evaluation is maintained about identifiable students before treating it as anonymous feedback.
Patch platforms on a specified timetable, and prioritise patches for platforms holding identifiable student information.
Bound accrediting disclosures to the scope of the exemption, and send only what the accreditation purpose requires.
Prepare documentation a regulator would ask for, and retain it in one place, because scattered documentation reads as no documentation.
Inform students through the yearly notification that releases to schools where they seek to enrol occur, since surprise releases damage trust even when lawful.
A worked illustration
In that illustration the disclosed officer reviews procurements for both colleges, and the arrangement is written down with responsibilities and response times.
Consider a registrar asked by a parent for a student's grades after the student has turned eighteen and is no longer a dependent for the relevant purpose.
In the badly done illustration, personal comments were included in the export, no deletion date was agreed, and the student notification still described the old platform.
Consider a researcher who requests for identifiable student files and is offered a de-identified extract instead, with a documented agreement for the study.
In that illustration students who decline biometrics are not disadvantaged, and the biometric templates of students who leave are deleted on schedule.
Where guides go wrong
Disclosing on the strength of a letter alone, without a court order or subpoena process, is an error that can be avoided by a single phone call to the privacy officer.
Treating a vendor as if it owned the data it procedures is a governance failure, even when the vendor's sales material encourages that view.
Accepting a vendor's consumer privacy policy as a substitute for a contract is an error, because consumer policies describe the vendor's own practices, not the institution's objectives.
Forgetting that a studies agreement must limit use and need destruction is an error that leaves research information in circulation following the study ends.
Responding to a media request from the first department that answers is an error, since the first department is rarely the department that knows the sharing limits.
Sources and evidence on the record
- Family Educational Rights and Privacy Act regulations, 34 CFR Part 99, text on eCFR.
- US Department of Education, Student Privacy Policy Office, studentprivacy.ed.gov - FERPA guidance, FAQs and model notices.
- US Department of Education, ed.gov - guidance, Dear Colleague letters and enforcement information.
Evidence basis: 34 CFR Part 99 and Department of Education guidance Applies when: When a college holds, uses or discloses a learning record in the context of lms platforms and learning data