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

Disability Records and Student Privacy

A plain-language guide to disability records and student privacy: the record, the purpose, the authority and the safeguard.

Privacy check
Record
sensitive student record in accessibility, equity and student privacy
Data
Disability Records and Student Privacy
Safeguard
need-to-know access and notices a student can actually understand
First check
Confirm consent, a named exception, or a contract term before sharing.

The short answer

Put merely, disability records and student privacy is about control over a personal student file that belongs, in a practical sense, to a student and is retained in trust by a college. The college may use it for the objective it was collected for, disclose it where the law or a valid consent permits, and must safeguard it everywhere else. Everything in this guide is a way of making that sentence workable at a desk, stage by stage.

Cloud hosting does not move responsibility: the institution remains answerable for a file even when another company stores it.

Biometric information can not be reissued like a password, so a biometric breach has consequences that outlast any single incident response.

Subprocessors multiply risk since each one is another holder of the file, and the contract must reach them or the chain breaks.

Title IX procedures involve highly personal files, and confidentiality handling there needs both legal care and human care.

What this covers

Discussion posts in a course system are maintained regarding identifiable students, and their storage should follow the course file schedule.

Backups are copies too, and a deletion process that ignores backups leaves the file in place under another name.

Parent and guardian access through a portal is a disclosure decision, and the portal's permissions should reflect rights transfer, not family habit.

Medical treatment records retained by a site clinic have their own treatment exemption, and the exemption ends when the file is used for another objective.

Counselling files raise the same boundary issue, and staff ought to verify the exemption before treating such a record as a routine file.

Assistive technology can collect usage information that reveals disability, and vendors of such tools ought to be reviewed with that sensitivity in mind.

How to work through it

Run penetration tests on student platforms, and treat the findings as a work list with owners and dates, not as a report to file.

Encrypt records in transit and at rest, and treat encryption as a baseline, not as a substitute for access control or purpose limits.

Use external auditors where independence matters, and provide them access to the platforms they need to test, not only to policy documents.

Locate each copy before deciding, including the vendor copy, the backup copy and the copy in the disclosed drive.

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

Hold a confidentiality committee that may actually stop a project, since a committee that solely advises will be ignored when it matters.

Require a court order or subpoena procedure for compelled disclosures, and do not disclose on the strength of a letter alone.

Verify whether a course evaluation is maintained regarding identifiable students before treating it as anonymous feedback.

A worked illustration

In that illustration the survey report demonstrates only aggregates above a stated threshold, and no small-group result may identify a respondent.

In that illustration the sheet is restricted, the members are told, and the organization adopts a form with proper access control for future collection.

In that illustration students who decline biometrics are not disadvantaged, and the biometric templates of students who leave are deleted on schedule.

Consider an admissions office that retains applicant data for students who never enrolled, and that deletes those records when the stated schedule expires.

A second illustration, again hypothetical, shows the same adoption done badly: the university signs on standard consumer terms and discovers a right to use de-identified information for product improvement.

Where guides go wrong

Publishing a directory without verifying the opt-out list is a mistake that is visible to each student who opted out, and to their peers.

This guide does not substitute for an institution's own policies or counsel, and a conflict between the two should be resolved in favour of the institution's own advice.

Disclosing financial aid details beyond what the aid determination requires is a mistake, since the file often holds more than the determination needs.

Including a diagnosis in an accommodation letter, when an instructor only needs to know the accommodation, is an error that discloses more than the purpose requires.

Redacting access responses without explaining the redactions is an error, since an unexplained gap teaches a student that files are edited at shall.

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 sensitive student record in the context of accessibility, equity and student privacy

Next on the ledger