COPPA Age Screening Without Collecting More Data
COPPA Age Screening Without Collecting More Data: what it means for a childrens online data, who may use it, and the check to make before it moves.
- Record
- childrens online data in coppa and younger students in edtech
- Data
- COPPA Age Screening Without Collecting More Data
- 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
The first thing to settle in coppa age screening without collecting more data is the identity of the childrens online data and the reason it is held, because every later issue regarding permission, exception 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 decision usually follows without drama.
Copies of files given to students should be full enough to be useful, and redactions of third-party information should be explained.
International students face additional exposure when records travel across borders, and that exposure ought to shape storage and sharing determinations.
Removal at contract end must be verifiable, not merely promised, and the verification method ought to be agreed before signing.
Training alters behavior solely when it is tied to the determinations staff really make, with a named person to request when the answer is unclear.
What this covers
Parents of dependent students may receive records under an exemption, but dependency must be established, not assumed from a family relationship.
Admissions information involves applicants who might never enroll, and their records deserve protection even though they never become students in the usual sense.
Accessibility information in a learning platform may reveal disability status, and access to it ought to 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.
Law enforcement records created by a campus police unit for a law enforcement objective are treated separately from education records, with their own limits.
Directory information is a defined subset that an university might designate and publish, and the designation must be published before it is relied on.
How to work through it
Own each group mailbox membership list, because an unowned list is an access control failure waiting to be discovered.
Read exemptions narrowly and on their own terms, and do not stretch an exemption to cover a purpose that merely resembles the named one.
Plan for remote work explicitly, with controls that travel with the file to staff homes and personal devices.
Retain audit evidence on a stated schedule, because evidence deleted too early cannot support a later defense, and evidence kept too long becomes a file of its own.
Route media requests for student information through the privacy officer, and do not let the first office to answer become the sharing determination.
Support students who keep personal copies of their records, since a student who can track their own file is a student who can spot errors early.
Review access when roles alter, and treat a role alter without an access review as an open incident, not an administrative delay.
State the objective in a sentence a student could understand, and if the sentence can not be written plainly, the objective is probably too broad.
A worked illustration
Consider an admissions office that holds applicant information for students who never enrolled, and that deletes those records when the stated schedule expires.
In that illustration the sharing log makes the answer easy, and the student leaves with a clearer picture of how their file travels.
Consider a student employee whose employment record is requested as if it were an academic record, and a registrar who distinguishes the two capacities.
In that illustration the survey report shows only aggregates above a stated threshold, and no small-group result may identify a respondent.
Consider a college that adopts the same platform without an alternative, and that discovers too late that some students can not or will not enrol.
Where guides go wrong
Keeping information just in case is a mistake dressed as caution, because information kept without objective is information exposed without benefit.
Approving a sharing without recording it is a mistake, since a reviewer, auditor or student shall eventually request what happened and why.
Accepting a checkbox as verifiable parental consent is an error, because a checkbox that anyone can tick verifies nothing.
Sending an accrediting body more than the accreditation purpose requires is an error, since the exception bounds what might be sent.
Writing a notification that no student may find, or that no student may understand, is a mistake that undermines every later reliance on that notification.
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