StudentPrivacy.college
The Privacy Ledger - protect and govern student data

Deprovisioning Accounts After Departure

A plain-language guide to deprovisioning accounts after departure: the record, the purpose, the authority and the safeguard.

Privacy check
Record
student record in the cloud in cloud systems and student portals
Data
Deprovisioning Accounts After Departure
Safeguard
access controls, logging and a contract that follows the record
First check
Name the record and its holder before any use or disclosure.

The short answer

Put simply, deprovisioning accounts after departure is about control over a student file in the cloud that belongs, in a practical sense, to a student and is retained in trust by an institution. The institution might use it for the purpose it was collected for, disclose 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.

A breach response that starts with notification and skips containment will notify students about a problem that is still getting worse.

Role changes must trigger access reviews, or former access quietly becomes current risk.

Analytics may improve teaching, but analytics built on identifiable student information need the same authorization analysis as any other use.

A privacy programme that solely reacts to incidents shall always be behind, because the determinations that produce risk are made during procurement and design.

What this covers

Health and counseling platforms should be segregated from broad student platforms, with access limited to the staff who provide the care.

Law enforcement files created by a site police unit for a law enforcement objective are treated separately from education files, with their own limits.

Biometric templates should be deleted when a student leaves, on a specified timetable, and the removal should be verifiable.

A note kept solely for its author's personal use, never shared, sits outside the category, and the moment it is shared that safeguarding can fall away.

Studies conducted on behalf of a college need documented agreements that limit use, require de-identification where possible, and require destruction on schedule.

Title IX files involve complainants, respondents and witnesses, and confidentiality handling there affects safety as well as compliance.

How to work through it

Include return of files in vendor contracts, in an usable format, because a file returned in an unusable form is not truly returned.

Read exceptions narrowly and on their own terms, and do not stretch an exception to cover a purpose that merely resembles the identified one.

Use role-based access as the default, and treat any exemption to it as a determination that needs its own justification.

Support students who keep personal copies of their records, since a student who can track their own file is a student who can spot errors early.

Separate duties so that the person who approves a sharing is not the only person who may see that it happened.

Include students in oversight, because students notice confidentiality problems that staff have normalised.

Assess AI tools with the same gate, plus a specific review of training information use, prompt storage and output handling.

Map data flows for each major platform, and update the map when integrations alter, since integrations alter silently.

A worked illustration

In that illustration the logs are released solely to the extent the process requires, with redactions for students not involved.

Consider a college that receives a media request for a student's disciplinary file and routes it to the privacy officer instead of answering from the first department.

In that illustration the rules are published to residents, access is logged, and footage is deleted on schedule unless it is required for a specific investigation.

In that illustration the employer receives a prompt, limited answer, and the graduate is not surprised by a broader sharing.

Consider an employer who requests a college to confirm a graduate's degree and is given solely the directory facts the college has designated, not the transcript.

Where guides go wrong

Retaining information just in case is an error dressed as caution, since information kept without objective is information exposed without benefit.

Disclosing a disciplinary outcome beyond the limits for that offence and receiver is an error that can injury a student long following the procedure ends.

Treating internal sharing as unrestricted is a mistake, because internal recipients still need a purpose and authorization for the file.

Mixing health or counselling records into broad student systems is a mistake that is hard to undo once the information has spread.

Approving a disclosure without recording it is a mistake, since a reviewer, auditor or student will eventually ask what happened and why.

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.
  • National Institute of Standards and Technology, Computer Security Resource Center - control guidance used here as method, not as law.

Evidence basis: 34 CFR Part 99 and Department of Education guidance Applies when: When a college holds, uses or discloses a student record in the cloud in the context of cloud systems and student portals

Next on the ledger