LGBTQ Students and Directory Information Risks
A plain-language guide to lgbtq students and directory information risks: the record, the purpose, the authority and the safeguard.
- Record
- sensitive student record in accessibility, equity and student privacy
- Data
- LGBTQ Students and Directory Information Risks
- Safeguard
- need-to-know access and notices a student can actually understand
- First check
- State the purpose in a sentence a student could understand.
The short answer
The first thing to settle in lgbtq students and directory information risks is the identity of the sensitive student record and the reason it is retained, since each later question regarding consent, exemption or contract depends on those two facts. Where the record is unclear, the rest of the analysis wobbles with it; where the record is clear, the determination usually follows without drama.
Opt-out procedures that are hard to find or hard to use shall be treated, fairly, as if they did not exist.
Deletion rights for children's information should be honoured swiftly, and the deletion should reach backups and subprocessors on a stated timetable.
The record comes first and the rule follows it, and any determination made in the opposite order should be rechecked before it is acted on.
Retaining a personal copy of a record file helps a student track what an institution retains, and institutions should not obstruct that habit.
What this covers
Biometric templates should be deleted when a student leaves, on a stated timetable, and the removal should be verifiable.
Audit and evaluation disclosures must be limited to the audit or evaluation purpose, and the receiver must be bound to that purpose.
Fingerprint and palm platforms for building access produce a biometric record for each student who enrols in them, and an alternative must exist for students who decline.
Video surveillance holds images of identifiable students, and its storage, access and sharing rules ought to be written before cameras are installed.
Assistive technology may collect usage information that reveals disability, and vendors of such tools ought to be reviewed with that sensitivity in mind.
Alumni directories raise the same designation question, because former students retain an interest in how their information is published.
How to work through it
Analyse mixed-audience platforms for their younger users separately, because a policy documented for adults does not cover children.
Document emergency releases at the time, with the facts that made the emergency real, because later reconstruction rarely convinces a reviewer.
Audit access to personal files, and follow up on anomalies, since an audit that finds nothing is either lucky or blind.
Run penetration tests on student systems, and treat the findings as a work list with owners and dates, not as a report to file.
Retain applicant records on a stated schedule, and delete them when that schedule expires, rather than keeping them indefinitely.
Write notices in plain language, and test them on students, since a notification that confuses its readers has failed its objective.
Need verifiable parental consent for younger users, and do not accept a checkbox that anyone may tick as verification.
Respond to student access requests promptly and in an usable format, since delay turns a right into a frustration.
A worked illustration
In that illustration a review finds the storage unjustified, the birth dates are deleted, and the screening is redesigned to collect the minimum needed.
Consider a health center that shares treatment files with a general student system by accident, and that treats the accident as an incident, not as a clerical slip.
In that illustration the request is answered for the employment capacity only, and the academic record is not disclosed by mistake.
Where the full record is genuinely needed in such a case, the sharing is limited, explained to the student where required, and noted in the record.
In that illustration the rules are published to residents, access is logged, and footage is deleted on schedule unless it is needed for a particular investigation.
Where guides go wrong
Assuming cloud hosting moves responsibility is an error, since the college remains answerable for a file another company stores.
Excluding students from privacy oversight is a mistake, since students notification problems that staff have normalised.
Analysing a marketing use as routine, and therefore authorised, is a mistake, since routine is not authority.
Adopting a free tool without reviewing its information practices is a mistake, because the price is often paid in information uses nobody reviewed.
Keeping applicant records indefinitely is a mistake, since applicants who never enrol still have records that deserve a stated schedule.
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