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

Sole Possession Notes and the Personal Note Exception

Sole Possession Notes and the Personal Note Exception explained for colleges: the rule, the exceptions, and the record an institution should keep.

Privacy check
Record
education record in education records and directory information
Data
Sole Possession Notes and the Personal Note Exception
Safeguard
a published directory designation and a working opt-out
First check
Check that the recipient is bound to use the data only as agreed.

The short answer

A practical way to approach sole possession notes and the personal note exception is to request what a student would expect if they saw the sharing described in plain language. Where the sharing matches that expectation and the authority supports it, it may proceed with a log entry; where it surprises, it needs permission, a named exception or a fresh decision, not a quiet assumption.

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

Surveillance on campus alters behaviour even when it is lawful, and that chilling effect belongs in the decision, not outside it.

Amendment is not the same as deletion: a successful challenge corrects or explains a record, and the original entry often remains in the file with the challenge noted.

A sharing is lawful solely when its objective, its authorization and its receiver all line up, and a gap in any one of those three is a reason to pause.

What this covers

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

Fingerprint and palm systems for building access produce a biometric record for every student who enrols in them, and an alternative must exist for students who decline.

Emergency disclosures need a real emergency and a judgement that the sharing is necessary to safeguard health or safety, documented at the time.

Language access matters for confidentiality notices, since a student who can not read a notice can not meaningfully permission or opt out.

Video surveillance retains images of identifiable students, and its retention, access and disclosure requirements should be written before cameras are installed.

Subpoenas and court orders for student records have their own process, and employees ought not to disclose on the strength of a letter alone.

How to work through it

Bound accrediting releases to the scope of the exemption, and send solely what the accreditation objective needs.

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

Hold a privacy committee that may actually stop a project, because a committee that only advises will be ignored when it matters.

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

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

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

Turn audit findings into a remediation plan with priorities, because a list of findings without a plan is a list of known risks left open.

Audit releases against the log, and treat a disclosure missing from the log as a finding, not as a clerical gap.

A worked illustration

In that illustration the registrar explains the position politely, in writing, and offers the parent a route through the student's own consent.

Consider an alumni department that wants to publish a class directory and that verifies opt-outs and designations for former students before publishing.

Consider a student employee whose employment file is requested as if it were an academic file, and a registrar who distinguishes the two capacities.

Consider a small college without a dedicated confidentiality officer that discloses the role with a neighbouring institution through a formal arrangement.

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

Where guides go wrong

Keeping information just in case is a mistake dressed as caution, because information kept without purpose is information exposed without benefit.

Punishing escalation is an error, since staff who are punished for asking shall stop asking and start deciding quietly.

Collecting disability information via assistive technology without reviewing the vendor is an error, since usage information can reveal disability.

Forgetting to review privacy governance after a merger or platform change is a mistake, because the information map from before the change will no longer be accurate.

Disclosing a disciplinary outcome beyond the limits for that offence and recipient is a mistake that may harm a student long following the procedure ends.

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 and Department of Education guidance Applies when: When a college holds, uses or discloses a education record in the context of education records and directory information

Next on the ledger