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

Vendor Breaches Affecting Student Data

Vendor Breaches Affecting Student Data: what it means for a exposed student record, who may use it, and the check to make before it moves.

Privacy check
Record
exposed student record in breaches and incident response
Data
Vendor Breaches Affecting Student Data
Safeguard
containment, notification and a written after-action record
First check
Name the record and its holder before any use or disclosure.

The short answer

Put merely, vendor breaches affecting student information is regarding control over an exposed student record that belongs, in a practical sense, to a student and is held 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 permission 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.

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

Vendor selection is a confidentiality decision before it is a purchasing decision, because the vendor's information practices become the institution's risk.

The burden of proving authority sits with the institution making the sharing, not with the student questioning it afterwards.

Transfer and withdrawal do not end a student's rights over files already retained, though the practical procedure for exercising them changes.

What this covers

Medical treatment files held by a campus clinic have their own treatment exemption, and the exemption ends when the file is used for another purpose.

Career services hold employment and internship data, and sharing that data with employers needs consent analysis even when the sharing feels useful.

Alumni directories raise the same designation issue, since former students retain an interest in how their information is published.

Parent and guardian access via a portal is a sharing determination, and the portal's permissions should reflect rights transfer, not family habit.

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

Employment files for student employees sit in a distinct category, and the distinction matters when a record is requested.

How to work through it

Respond to student access requests promptly and in an usable format, since delay turns a right into a frustration.

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

Apply the highest notice and consent standard to personal survey topics, since the injury of unwanted disclosure is greatest there.

Log access to personal files, and review those logs, since unreviewed logs safeguard nobody.

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

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

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

Inform students via the annual notice that releases to schools where they seek to enrol occur, since surprise releases damage trust even when lawful.

A worked illustration

Consider a counseling service that retains notes in a personal file and is asked whether those notes are education records, and that verifies the exemption before answering.

In that illustration the review, when it finally happens, finds monitoring that was never disclosed, and the college must withdraw the app mid-term.

Consider a campus that installs cameras in a residence hall entrance and writes storage, access and sharing rules before the cameras are switched on.

In that illustration the disclosing is limited to the disciplinary purpose, and the file is not treated as an ordinary student file afterwards.

Consider a college that merges two campuses and discovers that each site held the same records under different retention schedules.

Where guides go wrong

Screening younger users by collecting more information than the screening needs is a mistake, since the safeguarding then becomes the problem.

Starting an AI pilot for younger students before completing both the COPPA and the FERPA analysis is an error that is discovered, not prevented.

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.

Letting a privacy committee exist solely to advise is a mistake, since a committee that can not stop a project shall be ignored when it matters.

Writing a notice that no student can find, or that no student can understand, is an error that undermines every later reliance on that notice.

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: Department of Education guidance and state breach statutes Applies when: When a college holds, uses or discloses a exposed student record in the context of breaches and incident response

Next on the ledger