Skip to content
COPPA · COPPA-312-4B-DIRECT-NOTICE

COPPA 16 CFR 312.4(b), (c)(1)-(4) - Assess and implement the applicable direct notice

Assess the direct-notice pathway and deliver its complete contents and material-change notice where required

HIGHProcess dutyTransparencyBinding regulationIn forceApplies from 22 April 2026

Where this comes from

Provision: 16 CFR 312.4(b), (c)(1)-(4) - Assess and implement the applicable direct notice

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

Citation: 16 CFR 312.4(b), (c)(1)-(4) and 312.5(a), (c); 90 FR 16918 (22 April 2025), effective 23 June 2025, general compliance date 22 April 2026

Text version: 16 CFR 312.4 and 312.5(c), eCFR displayed through 3 September 2026, retrieved 6 September 2026; 2025 final rule, 90 FR 16918

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

What engineering work it implies

Sample acceptance criteria Landfall generates for this obligation:

  • Assess the covered activity and full 312.5(c) pathway before selecting direct-notice contents; do not collect parental contact information merely to complete this assessment.
  • For consent notice, include any preliminary name/contact collection, required consent and no further collection/use/disclosure without it, intended information/uses/disclosure opportunities, recipients or specific categories including the public, purposes and the separate choice, online notice link, verifiable-consent means and applicable name/contact deletion.
  • Reconcile reasonable-time deletion from notice under 312.4(c)(1)(vii) with deletion measured from collection under 312.5(c)(1); later notice cannot restart retention.
  • For participation updates, state parental contact collection, no other use/disclosure, refusal/deletion procedures and the online notice link.
  • For repeated contact, state both contact collections, no other use/disclosure/combination of the child's contact, refusal and deletion of both contact sets, stated-purpose effect of no response and the online notice link; undeliverable notice fails reasonable efforts.

Evidence an auditor expects

  • Assessment documentDocument review

    Notice assessment, contents and operational evidence

    Source-version and activity-specific notice assessment with implemented evidence: Assess the covered activity and full 312.5(c) pathway before selecting direct-notice contents; do not collect parental contact information merely to complete this assessment. For consent notice, include any preliminary name/contact collection, required consent and no further collection/use/disclosure without it, intended information/uses/disclosure opportunities, recipients or specific categories including the public, purposes and the separate choice, online notice link, verifiable-consent means and applicable name/contact deletion. Reconcile reasonable-time deletion from notice under 312.4(c)(1)(vii) with deletion measured from collection under 312.5(c)(1); later notice cannot restart retention. For participation updates, state parental contact collection, no other use/disclosure, refusal/deletion procedures and the online notice link. For repeated contact, state both contact collections, no other use/disclosure/combination of the child's contact, refusal and deletion of both contact sets, stated-purpose effect of no response and the online notice link; undeliverable notice fails reasonable efforts. For child safety, state child/parent name/contact collection, safety-only use/disclosure, refusal/deletion procedures, stated-purpose effect of no response and the online notice link. Test receipt efforts, refusal, deletion and material changes requiring renewed notice/consent; a link-only message or parental silence is not general consent. Preserve minimized status and notice-version evidence. A generated task or DRAFT source is not consent, an exception determination or legal approval.

Questions people ask

Does COPPA 16 CFR 312.4(b), (c)(1)-(4) - Assess and implement the applicable direc… apply to my service?
It applies when COPPA assessed activity Q_COPPA_COVERED_ACTIVITY: YES.
From when does this apply?
COPPA 16 CFR 312.4(b), (c)(1)-(4) - Assess and implement the applicable direc… applies from 22 April 2026. Its current status is: in force.
What evidence does an auditor expect?
Notice assessment, contents and operational evidence.

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