COPPA and School Authorisation Versus Parental Consent
A plain-language guide to coppa and school authorisation versus parental consent: the record, the purpose, the authority and the safeguard.
- Record
- childrens online data in coppa and younger students in edtech
- Data
- COPPA and School Authorisation Versus Parental Consent
- Safeguard
- verifiable parental consent before collection from a child
- First check
- Name the record and its holder before any use or disclosure.
The short answer
A practical way to approach coppa and school authorisation versus parental consent is to ask 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 can proceed with a log entry; where it surprises, it needs consent, a named exception or a fresh decision, not a quiet assumption.
Readiness for a regulator inquiry is built in ordinary weeks, via inventories and logs, not in the week the inquiry arrives.
Deletion rights for children's data ought to be honoured promptly, and the deletion ought to reach backups and subprocessors on a stated timetable.
A disclosure log is not bureaucracy: it is the record that lets a student, an auditor or a regulator reconstruct what happened.
Research uses of education files need their own authority analysis, and a research exception is narrower than researchers sometimes assume.
What this covers
Accommodation letters should disclose solely what a lecturer needs to provide the accommodation, not the underlying diagnosis.
Student portals concentrate files in one place, which makes access control both more significant and easier to audit than scattered files.
Career services hold employment and internship information, and sharing that information with employers needs permission analysis even when the sharing feels useful.
Research platforms hold datasets that might be de-identified in name but identifiable in combination, especially in small programmes.
Equity in privacy means recognising that the same disclosure harms different students differently, and that uniform procedures can still produce unequal risk.
Emergency releases require a real emergency and a judgement that the disclosure is necessary to safeguard health or safety, documented at the time.
How to work through it
Establish dependency before disclosing to parents of a student, and do not assume it from a family relationship or a shared surname.
Provide former students a workable procedure for exercising rights over files retained regarding them, since graduation ought not to end practical access.
Identify the authority before the information moves, not after, since retrospective authority is usually no authority at all.
Safeguard alumni files with the same care as current files, since graduation does not end the college's duty.
Put vendor terms in the contract, not in a sales deck, and check that the contract names the data, limits its use and requires removal on exit.
Separate health and counselling platforms from general student platforms, with access limited to the staff who provide the care.
Analyse mixed-audience platforms for their younger users separately, because a policy written for adults does not cover children.
Handle transfer and withdrawal files with care, since a student's rights over files previously held do not end when enrolment ends.
A worked illustration
Consider a campus that installs cameras in a residence hall entrance and writes storage, access and sharing requirements before the cameras are switched on.
In that illustration the employer receives a prompt, limited answer, and the graduate is not surprised by a broader disclosure.
In that illustration the disclosing is limited to the disciplinary objective, and the record is not treated as a routine student file afterwards.
In that illustration the disclosure log makes the answer easy, and the student leaves with a clearer picture of how their record travels.
Consider a learning app for younger students that tracks behavior across sessions and shares aggregates with a third party, without a privacy review.
Where guides go wrong
Accepting a vendor's self-assessment as evidence, where the data is sensitive, is an error, because self-assessment answers the issues the vendor chose to ask.
Treating alumni records as unprotected history is an error, since graduation does not end the college's duty.
Including a diagnosis in an accommodation letter, when a lecturer solely needs to know the accommodation, is an error that discloses more than the objective needs.
Disclosing to a parent on the basis of family relationship alone, without establishing dependency, is an error that recurs each enrolment season.
Starting an AI pilot for younger students before completing both the COPPA and the FERPA analysis is a mistake that is discovered, not prevented.
Sources and evidence on the record
- Children's Online Privacy Protection Rule, 16 CFR Part 312, text on eCFR.
- Federal Trade Commission, COPPA guidance pages.
- Family Educational Rights and Privacy Act regulations, 34 CFR Part 99, text on eCFR.
Evidence basis: COPPA Rule, 16 CFR Part 312, and FTC guidance Applies when: When a college holds, uses or discloses a childrens online data in the context of coppa and younger students in edtech