Skip to content
COPPA · COPPA-312-MIXED-AUDIENCE

COPPA 16 CFR 312.2 - Mixed audience definition and directed-to-children paragraph (3)

Assess mixed-audience eligibility and enforce neutral age determination before non-exempt collection from any visitor

HIGHProcess dutyAge verificationBinding regulationIn forceApplies from 22 April 2026

Where this comes from

Provision: 16 CFR 312.2 - Mixed audience definition and directed-to-children paragraph (3)

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

Citation: 16 CFR 312.2 (Mixed audience website or online service; Website or online service directed to children, paragraphs (1) and (3)); 312.5(c); 90 FR 16918 (22 April 2025)

Text version: 16 CFR 312.2 and 312.3, eCFR displayed through 3 September 2026, checked 6 September 2026; FTC May 2026 Not Just for Kids' Sites and Six-Step Compliance Plan used as staff guidance. 2025 final amendments generally require compliance from 22 April 2026. Current metadata does not implement historical-version evaluation.

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_MIXED_AUDIENCE_PATH: YES

What engineering work it implies

Sample acceptance criteria Landfall generates for this obligation:

  • Establish child-directed eligibility under the actual 312.2 factors and that children are not the primary audience; having adult users or a mixed-age label is insufficient.
  • Test collection from every visitor before age determination, including guests, landing-page SDKs, server calls and passive identifiers; permit only a specifically established limited 312.5(c) purpose with all applicable conditions.
  • Use age information or another reasonably calculated means considering available technology, with a neutral method, no default age and no cues encouraging falsification; date of birth, persistent cookies, ID uploads and facial images are not prescribed by this definition.
  • Test unknown, failed and conflicting age results, direct guest access and pre-determination traffic; unresolved determination must not silently become adult status or permit non-exempt collection.
  • For visitors identified under 13, apply the actual notice, consent/conditioned-exception and remaining duties. Age determination is not parental consent; do not use mixed-audience treatment to exclude children from a primarily child-directed service.

Evidence an auditor expects

  • Assessment documentDocument review

    Mixed-audience eligibility and pre-determination data-flow review

    [ ] Establish child-directed eligibility under the actual 312.2 factors and that children are not the primary audience; having adult users or a mixed-age label is insufficient. [ ] Test collection from every visitor before age determination, including guests, landing-page SDKs, server calls and passive identifiers; permit only a specifically established limited 312.5(c) purpose with all applicable conditions. [ ] Use age information or another reasonably calculated means considering available technology, with a neutral method, no default age and no cues encouraging falsification; date of birth, persistent cookies, ID uploads and facial images are not prescribed by this definition. [ ] Test unknown, failed and conflicting age results, direct guest access and pre-determination traffic; unresolved determination must not silently become adult status or permit non-exempt collection. [ ] For visitors identified under 13, apply the actual notice, consent/conditioned-exception and remaining duties. Age determination is not parental consent; do not use mixed-audience treatment to exclude children from a primarily child-directed service. [ ] Preserve minimized eligibility, method, traffic and decision evidence without raw child age/identity payloads. Review current February 2026 age-verification enforcement discretion separately; no checkbox automatically grants a rule or policy exception. This evidence supports review; it is not legal approval, consent or an automatic exception.

Questions people ask

Does COPPA 16 CFR 312.2 - Mixed audience definition and directed-to-children parag… apply to my service?
It applies when COPPA assessed activity Q_COPPA_MIXED_AUDIENCE_PATH: YES.
From when does this apply?
COPPA 16 CFR 312.2 - Mixed audience definition and directed-to-children parag… applies from 22 April 2026. Its current status is: in force.
What evidence does an auditor expect?
Mixed-audience eligibility and pre-determination data-flow review.

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