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

Disclosure in a Health or Safety Emergency

Disclosure in a Health or Safety Emergency explained for colleges: the rule, the exceptions, and the record an institution should keep.

Privacy check
Record
education record in consent and disclosure exceptions
Data
Disclosure in a Health or Safety Emergency
Safeguard
written consent, or an exception that fits the facts, recorded in the log
First check
Limit the sharing to the minimum the purpose requires.

The short answer

A practical way to approach sharing in a health or safety emergency is to request what a student would expect if they saw the disclosing described in plain language. Where the disclosing matches that expectation and the authorization supports it, it can proceed with a log entry; where it surprises, it needs consent, a named exception or a fresh determination, not a quiet assumption.

Proctoring tools collect some of the most personal data on site, and their adoption needs a higher standard of review than a routine classroom tool.

Training alters behaviour only when it is tied to the decisions staff actually make, with a named person to ask when the answer is unclear.

Personal survey topics need the highest standard of notification and consent, because the injury of an unwanted disclosure is greatest there.

Governance fails quietly when nobody owns a decision, and the first fix in most institutions is naming an owner, not writing a new policy.

What this covers

Platforms that feed directory information to outside directories need an opt-out verify built into the feed, not added as a manual afterthought.

Public files requests can reach student information, and staff handling them need to know which files are safeguarded before responding.

Alumni platforms hold giving, employment and contact data, and former students should be able to correct and limit that data.

Course copies carry student information into new terms, and stale copies ought to be cleaned rather than carried forward indefinitely.

An education file is defined by how it is maintained and whom it is regarding, not by the folder it sits in or the platform that retains it.

Parents of dependent students may receive files under an exemption, but dependency must be established, not assumed from a family relationship.

How to work through it

Track privacy metrics honestly, such as time to delete, time to respond to access requests, and number of vendors without current contracts.

Delete on schedule, and make deletion verifiable, because a deletion that cannot be shown is a deletion that will be doubted.

Scrutinise tracking in education tools for younger students, because behavioral information grows quietly over a school year.

Distinguish employee files from student files for student employees, since the capacity in which a file was created matters.

Prepare documentation a regulator would ask for, and retain it in one place, because scattered documentation reads as no documentation.

Separate health and counseling platforms from general student platforms, with access limited to the employees who provide the care.

Limit audit and evaluation releases to the audit purpose, and bind the recipient to that purpose in writing.

Tell 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

Consider a survey of younger users on a learning platform that collects birth dates for age screening and then retains them indefinitely.

Consider a student who asks to see an advising note that contains a factual error, and who receives the note, the correction procedure and a documented decision.

In that illustration the institution must retrofit an alternative under pressure, and the students affected have already lost trust in the procedure.

Consider a department that wants to publish a directory of student contact details for a course, and that verifies the directory designation and opt-out list first.

Consider a student organization that collects member data in a shared spreadsheet and discovers, during a review, that the sheet is visible to the whole site.

Where guides go wrong

This guide does not interpret the law for a specific institution, and readers should escalate cases it can not settle rather than treating its structure as a determination.

Documenting an emergency sharing following the fact, from memory, is a mistake, because later reconstruction rarely convinces a reviewer.

Allowing monitoring in learning applications for younger students to go unreviewed is an error, because behavioural information accumulates silently over a school year.

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

Delaying removal of children's data after a removal request is a mistake, since the data continues to be used while the request waits.

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.
  • Family Educational Rights and Privacy Act, 20 U.S.C. 1232g, statutory text.

Evidence basis: 34 CFR Part 99, disclosure and consent provisions Applies when: When a college holds, uses or discloses a education record in the context of consent and disclosure exceptions

Next on the ledger