Skip to content
COPPA · COPPA-312-7-NO-CONDITIONING

COPPA 16 CFR 312.7 - No conditioning participation on excessive personal information

Do not require more personal information than reasonably necessary for a child's participation, including guest activities

CRITICALProhibitionData collectionBinding regulationIn forceApplies from 21 April 2000

Where this comes from

Provision: 16 CFR 312.7 - No conditioning participation on excessive personal information

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

Citation: 15 U.S.C. 6502(b)(1)(C); 16 CFR 312.7 and 312.6(c); 90 FR 16918, 16981 (22 April 2025); original rule 64 FR 59888 (3 November 1999), effective 21 April 2000. This prohibition predates the 2025 republication.

Text version: 16 CFR 312.7, eCFR displayed through 3 September 2026, retrieved 6 September 2026; 2025 final rule, 90 FR 16918, 16981.

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:

  • Inventory every required disclosure for covered games, prizes and other activities, including guest participation, registration, feature unlocks and SDK prerequisites.
  • Document why each required item of personal information is reasonably necessary for the particular activity under 312.7; remove or redesign conditions whose necessity is not established.
  • Test that declining unnecessary information does not block participation through interface controls, server validation or third-party requirements. Account registration is not a prerequisite for this prohibition.
  • Do not replace reasonably necessary with an invented strict-necessity test, treat parental consent as curing an excessive condition, or treat this section as permission for every optional collection.
  • Apply the same necessity limit to any service restriction following parental refusal/deletion under 312.6(c); assess other notice, consent, purpose and retention duties separately.

Evidence an auditor expects

  • Policy documentDocument review

    Activity-specific necessity and participation assessment

    [ ] Inventory every required disclosure for covered games, prizes and other activities, including guest participation, registration, feature unlocks and SDK prerequisites. [ ] Document why each required item of personal information is reasonably necessary for the particular activity under 312.7; remove or redesign conditions whose necessity is not established. [ ] Test that declining unnecessary information does not block participation through interface controls, server validation or third-party requirements. Account registration is not a prerequisite for this prohibition. [ ] Do not replace reasonably necessary with an invented strict-necessity test, treat parental consent as curing an excessive condition, or treat this section as permission for every optional collection. [ ] Apply the same necessity limit to any service restriction following parental refusal/deletion under 312.6(c); assess other notice, consent, purpose and retention duties separately. [ ] Keep minimized design decisions and synthetic positive/negative test evidence without live child records; unanswered necessity and scope questions require review. Evidence supports a source-based review; it is not legal approval or proof from raw child data.

Questions people ask

Does COPPA 16 CFR 312.7 - No conditioning participation on excessive personal info… apply to my service?
It applies when COPPA assessed activity Q_COPPA_COVERED_ACTIVITY: YES.
From when does this apply?
COPPA 16 CFR 312.7 - No conditioning participation on excessive personal info… applies from 21 April 2000. Its current status is: in force.
What evidence does an auditor expect?
Activity-specific necessity and participation 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