Equity and Differential Privacy Harms
A plain-language guide to equity and differential privacy harms: the record, the purpose, the authority and the safeguard.
- Record
- sensitive student record in accessibility, equity and student privacy
- Data
- Equity and Differential Privacy Harms
- Safeguard
- need-to-know access and notices a student can actually understand
- First check
- Check that the recipient is bound to use the data only as agreed.
The short answer
The first thing to settle in equity and differential confidentiality harms is the identity of the personal student record and the reason it is held, since each later issue about 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.
A policy that nobody has read is not a control, and the test of a policy is whether staff may state its key requirement without opening the document.
Penetration testing finds technical gaps, but it does not test whether a sharing decision was lawful, and both tests are needed.
Where two requirements point in different directions, the stricter applicable rule usually governs, and the conflict itself should be escalated rather than resolved quietly at a desk.
Transfer and withdrawal do not end a student's rights over records already held, though the practical procedure for exercising them alters.
What this covers
Bluetooth beacons in classrooms may record attendance quietly, and silent collection deserves explicit notification to the students affected.
Wi-Fi tracking may reconstruct a student's movements across site, and that capability should be governed before it is used, not following it is discovered.
Research systems retain datasets that may be de-identified in name but identifiable in combination, especially in small programmes.
Accessibility information in a learning system may reveal disability status, and access to it should be limited to staff who need it for support.
Audit and evaluation releases must be limited to the audit or evaluation objective, and the receiver must be bound to that objective.
State biometric laws add duties that vary by state, and a campus operating across states must not assume one state's requirement covers another's.
How to work through it
Run penetration tests on student systems, and treat the findings as a work list with owners and dates, not as a report to file.
Separate duties so that the person who approves a disclosure is not the solely person who may see that it happened.
Write notifications in plain language, and test them on students, since a notification that confuses its readers has failed its purpose.
Analyse outside survey requests separately from institutional surveys, since the authority for one does not cover the other.
State the purpose in a sentence a student could understand, and if the sentence can not be written plainly, the purpose is probably too broad.
Retain audit evidence on a specified schedule, since evidence deleted too early can not support a later defense, and evidence kept too long becomes a record of its own.
Complete both the COPPA and the FERPA analysis for AI tutors used by younger students before any pilot begins.
Limit the disclosure to the minimum the objective requires, and treat extra data as extra risk rather than extra helpfulness.
A worked illustration
In that illustration the audit finding becomes a remediation task with an owner and a date, and the subprocessor's copy is deleted on a verified timetable.
Consider a college that merges two campuses and discovers that each site retained the same files under different storage schedules.
In that illustration the study proceeds on the extract, the agreement limits use and needs destruction, and no identifiable file leaves the college.
Consider a vendor audit that finds a subprocessor nobody had recorded, holding a copy of student records for a retired integration.
In that illustration the institution must retrofit an alternative under pressure, and the students affected have already lost trust in the process.
Where guides go wrong
Permitting monitoring in education applications for younger students to go unchecked is an error, because behavioral information grows silently over a school year.
Auditing AI tools only for accuracy, and not for data storage and prompt handling, is an error, because AI systems produce records that ordinary audits miss.
A second common error is relying on a permission that was never particular, never explained, or obtained following the disclosure it was meant to authorise.
Screening younger users by collecting more information than the screening requires is an error, because the protection 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.
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