Skip to content
COPPA · COPPA-312-FTC-ENFORCEMENT

COPPA 15 U.S.C. §§6504-6505

Record COPPA enforcement authority and dated penalty context without inventing liability or recordkeeping requirements

CRITICALProcess dutyGovernanceBinding regulationIn forceApplies from 21 April 2000

Where this comes from

Provision: 15 U.S.C. §§6504-6505; 16 CFR §1.98 - Enforcement authority and dated penalty context

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

Citation: 15 U.S.C. §§6504, 6505; 15 U.S.C. §45(m)(1)(A); 16 CFR §1.98(d)

Text version: 16 CFR 1.98(d), eCFR through 2026-09-03; schedule for penalties assessed after 2025-01-17. 15 USC 6504/6505, House preliminary text through 2026-09-01 / 2026-09-05 respectively.

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:

  • Identify the activity and applicable FTC or agency-specific statutory authority with a qualified reviewer; lack of FTC jurisdiction alone is not a COPPA exemption.
  • Verify the current 1.98(d) schedule and penalty assessment date. The checked $53,088 maximum applies to assessments after 17 January 2025, including earlier violations; it is not a newly verified 2026 adjustment.
  • Record liability conditions, remedies and unresolved questions; task applicability is not a violation finding and this is not a liability calculation or a child-user multiplier.
  • Preserve the separate 6504 state-action threshold, federal-court remedies, notice/intervention rules and pending Commission-action limitation; do not treat the FTC amount as every state's penalty.
  • Record a source-change/reliance review owner and minimized source references; this workflow does not impose a blanket duty to retain all child or consent records.

Evidence an auditor expects

  • Assessment documentDocument review

    Dated enforcement-context register

    Identify the activity and applicable FTC or agency-specific statutory authority with a qualified reviewer; lack of FTC jurisdiction alone is not a COPPA exemption. Verify the current 1.98(d) schedule and penalty assessment date. The checked $53,088 maximum applies to assessments after 17 January 2025, including earlier violations; it is not a newly verified 2026 adjustment. Record liability conditions, remedies and unresolved questions; task applicability is not a violation finding and this is not a liability calculation or a child-user multiplier. Preserve the separate 6504 state-action threshold, federal-court remedies, notice/intervention rules and pending Commission-action limitation; do not treat the FTC amount as every state's penalty. Record a source-change/reliance review owner and minimized source references; this workflow does not impose a blanket duty to retain all child or consent records. Keep dated schedule history separate from the current register entry; qualified review and controlled evidence are required, not legal approval by the tool. Completion is not legal approval.

Questions people ask

Does COPPA 15 U.S.C. §§6504-6505 apply to my service?
It applies when COPPA assessed activity Q_COPPA_COVERED_ACTIVITY: YES.
From when does this apply?
COPPA 15 U.S.C. §§6504-6505 applies from 21 April 2000. Its current status is: in force.
What evidence does an auditor expect?
Dated enforcement-context register.

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