From when does this apply?

FTC COPPA FAQs N.1-N.3 — merged into COPPA-312-EDTECH-PROVISIONS 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.

COPPA · COPPA-312-5C4-SCHOOL-AUTH

FTC COPPA FAQs N.1-N.3 — merged into COPPA-312-EDTECH-PROVISIONS

MERGED into COPPA-312-EDTECH-PROVISIONS (legal review, 5 October 2026). Retained for history; not an obligation.

HIGHProcess dutyConsentRegulatory guidanceIn forceApplies from 19 May 2022

Where this comes from

Provision: FTC COPPA FAQs N.1-N.3 — merged into COPPA-312-EDTECH-PROVISIONS

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

Citation: Merged into COPPA-312-EDTECH-PROVISIONS; see that record's citations

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 ↗

Evidence an auditor expects

Assessment documentDocument review
Source-linked COPPA activity, authority and control assessment
Identify the school-requested educational service, actual authorizing institution and covered activity; a school label alone does not establish consent. Verify the school using a method reasonably calculated to prevent child impersonation; school/district selection is guidance best practice, not a universal statutory signatory rule. Provide direct collection/use/disclosure notice and school review, deletion and prevention-of-further-use/collection controls. Document the limited educational authority and assess direct parental consent separately for other commercial use; preserve operator responsibility. Label the source as FTC guidance and enforcement policy, not a codified 312.5(c)(4) school exception or a verified eligibility finding. Record the exact source version, reviewer, activity and evidence limits. A template or seed is not consent or qualified legal approval.

Questions people ask

From when does this apply?: FTC COPPA FAQs N.1-N.3 — merged into COPPA-312-EDTECH-PROVISIONS 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.

Run the pre-scan All COPPA obligations

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