Skip to content
COPPA · COPPA-312-EDTECH-PROVISIONS

COPPA FTC Education Technology Policy (19 May 2022) - School-context data controls

Constrain school-authorized processing to the requested service and preserve the operator's collection, security, retention and consent responsibilities

HIGHProcess dutyConsentRegulatory guidanceIn forceApplies from 19 May 2022

Where this comes from

Provision: FTC Education Technology Policy (19 May 2022) - School-context data controls

Instrument: Children's Online Privacy Protection Act (COPPA)

Citation: FTC Education Technology Policy Statement, 19 May 2022, pp. 2-4; COPPA FAQs N.1-N.5; 16 CFR 312.4-312.8 and 312.10; 90 FR 16918, 16919 (2025)

Text version: FTC COPPA FAQs section N (staff guidance); 19 May 2022 Commission edtech policy; 90 FR 16918, 16919 (22 April 2025) retains guidance and does not codify school authorization; checked 6 September 2026

Checked against the source: 6 September 2026

Read the official text ↗

Who it applies to

It applies when all of these are true:

  • COPPA assessed activity Q_COPPA_COVERED_ACTIVITY: YES
  • COPPA assessed activity Q_COPPA_SCHOOL_PATH: YES

What engineering work it implies

Sample acceptance criteria Landfall generates for this obligation:

  • Trace the school-requested purpose through collection, processors, use, sharing and deletion; deny unrelated commercial reuse of school-authorized data.
  • Test that advertising, unrelated commercial profiling, sale and speculative future use cannot consume these data; a paid educational service is not excluded merely because it is commercial.
  • Verify collection necessity, an assessed retention schedule and reasonable security separately from the school's authorization.
  • Exercise the school's review, deletion and prevention controls and keep the operator's responsibility explicit in agreements.
  • Preserve a minimized record of purpose and authorization; do not copy child payloads into general audit logs.

Evidence an auditor expects

  • Assessment documentDocument review

    Source-linked COPPA activity, authority and control assessment

    Trace the school-requested purpose through collection, processors, use, sharing and deletion; deny unrelated commercial reuse of school-authorized data. Test that advertising, unrelated commercial profiling, sale and speculative future use cannot consume these data; a paid educational service is not excluded merely because it is commercial. Verify collection necessity, an assessed retention schedule and reasonable security separately from the school's authorization. Exercise the school's review, deletion and prevention controls and keep the operator's responsibility explicit in agreements. Preserve a minimized record of purpose and authorization; do not copy child payloads into general audit logs. Record the exact source version, reviewer, activity and evidence limits. A template or seed is not consent or qualified legal approval.

Questions people ask

Does COPPA FTC Education Technology Policy (19 May 2022) - School-context data con… apply to my service?
It applies when COPPA assessed activity Q_COPPA_COVERED_ACTIVITY: YES; COPPA assessed activity Q_COPPA_SCHOOL_PATH: YES.
From when does this apply?
COPPA FTC Education Technology Policy (19 May 2022) - School-context data con… applies from 19 May 2022. Its current status is: in force.
What evidence does an auditor expect?
Source-linked COPPA activity, authority and control assessment.

Find out whether this one lands on you

Landfall's pre-scan answers the applicability question above for your product in minutes, then turns every obligation that applies into traceable engineering tickets with a citation chain your auditors can follow.

Not legal advice. Landfall maps regulatory obligations to engineering work for planning purposes. Its verdicts are not legal advice and create no attorney-client relationship — verify with qualified counsel before relying on them.

What Landfall Is NOT

Critical Boundaries

Understanding these boundaries is essential before using this product. Misuse of this tool for purposes outside its scope may create legal, regulatory, or commercial risk for your organization.

NOT Legal Advice

This product does not provide legal advice and does not create an attorney-client relationship.

Interpretations are informational analysis, not legal counsel. Always consult qualified legal professionals for compliance decisions.

NOT a Risk Score

We do not quantify, calculate, or certify your compliance risk level.

No numerical risk rating, compliance percentage, or safety score. Risk assessment requires human judgment about your specific context.

NOT Runtime Enforcement

This is a planning and mapping tool, not a runtime enforcement system.

Does not integrate with your production systems. Does not block, filter, or enforce compliance in real-time. Implementation is your responsibility.

NOT Regulatory Approval

Using this tool does not mean you are compliant with any regulation.

No certification, seal of approval, or compliance guarantee. Regulators will evaluate your actual implementation, not your use of this tool.

NOT Authoritative Interpretation

Our interpretations are not binding and may differ from regulatory guidance.

Only regulators and courts provide authoritative interpretation. Our analysis reflects our reading of requirements, which may be incomplete or incorrect.

NOT a Safe Harbor

This tool does not shield you from enforcement actions or liability.

Documentation of your process is valuable, but does not constitute a legal defense. Compliance is ultimately your organization's responsibility.

NOT an AI Compliance Agent

AI features assist analysis but do not make compliance decisions for you.

AI-generated interpretations require human review and approval. Automated suggestions are starting points, not final answers.

NOT Complete Coverage

We do not cover all regulations, all obligations, or all jurisdictions.

Regulatory landscape is vast and evolving. Gaps in our coverage do not mean those requirements don't apply to you.

What This Tool IS:

  • A structured workflow for mapping regulatory requirements to implementation tasks
  • A documentation system for compliance decisions (audit trail)
  • A collaboration platform for compliance, legal, and engineering teams
  • An informational resource for understanding regulatory obligations