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

FERPA Disclosures to Other Institutions

FERPA Disclosures to Other Institutions explained for colleges: the rule, the exceptions, and the record an institution should keep.

Privacy check
Record
education record in ferpa in full
Data
FERPA Disclosures to Other Institutions
Safeguard
written consent or a named exception, logged at disclosure
First check
Limit the sharing to the minimum the purpose requires.

The short answer

Put simply, ferpa disclosures to other institutions is about control over an education record that belongs, in a practical sense, to a student and is retained in trust by an institution. The institution might use it for the objective it was collected for, share 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.

Yearly notifications are not a formality: they are the moment students learn what directory information means and how to opt out.

Permission, an identified exemption, or a contract term must cover the particular sharing in front of you, not a similar sharing from last term.

Vendor selection is a privacy decision before it is a purchasing decision, because the vendor's data practices become the university's risk.

What this covers

AI feedback tools might retain student work for training unless the contract says otherwise, and that term ought to be settled before adoption.

Language access matters for confidentiality notifications, because a student who cannot read a notice cannot meaningfully consent or opt out.

Proctoring integrations collect video, audio, screen and sometimes biometric data, and the sensitivity of that collection should set the review standard.

Media requests for student information should go through the confidentiality officer, not through the first office that picks up the phone.

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

Campus card platforms hold transaction and location data, and their storage should reflect that sensitivity rather than the convenience of indefinite logs.

How to work through it

Document emergency disclosures at the time, with the facts that made the emergency real, because later reconstruction rarely convinces a reviewer.

Limit financial aid releases to what the aid decision needs, and do not contain unrelated record details since they happen to be in the same file.

Name a person to ask when the answer is unclear, and welcome escalation, since punished escalation produces quiet non-adherence.

Analyse marketing uses of student data for permission even when the marketing feels ordinary, since ordinary is not authorization.

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

Establish dependency before disclosing to parents of a student, and do not assume it from a family relationship or a disclosed surname.

Assess surveillance proposals for necessity and proportionality, not solely for legality, since lawful surveillance may still harm trust.

Provide small colleges a disclosed-service option for confidentiality review, since an university without a dedicated officer still carries the same duties.

A worked illustration

Consider a proctoring tool adopted during a rush to online teaching, and reviewed properly only a year later, after thousands of recordings were stored.

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

In that illustration the study proceeds on the extract, the agreement limits use and needs destruction, and no identifiable file leaves the institution.

Consider a network team that holds connection logs and is asked for them during a disciplinary process, and that verifies the disclosure rules before releasing any log.

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

Where guides go wrong

Accepting a vendor's self-assessment as evidence, where the information is personal, is an error, since self-assessment answers the issues the vendor chose to request.

Collecting biometric data without a non-biometric alternative is an error, since some students cannot or shall not enrol, and they ought not to be disadvantaged.

Forgetting that a studies agreement must limit use and require destruction is a mistake that leaves research data in circulation after the study ends.

Failing to tell students via the annual notice that releases to schools where they seek to enroll occur is an error that damages trust even when the disclosure is lawful.

The most common error is treating a file as informal because it lives in an email thread, a chat log or a disclosed drive rather than in the platform of file.

Sources and evidence on the record

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

Evidence basis: FERPA statute 20 U.S.C. 1232g and 34 CFR Part 99 Applies when: When a college holds, uses or discloses a education record in the context of ferpa in full

Next on the ledger