Skip to content
COPPA · COPPA-312-10-SAFE-HARBOR

COPPA 16 CFR §312.11(h) - Operator participation in approved safe harbor programs

Assess actual guideline compliance and the service-specific scope of any COPPA safe-harbor reliance

MEDIUMProcess dutyGovernanceBinding regulationIn forceApplies from 21 April 2000

Where this comes from

Provision: 16 CFR §312.11(h) - Operator participation in approved safe harbor programs

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

Citation: 16 CFR §312.11(b)(2), (g), (h); 15 U.S.C. §6503

Text version: 16 CFR 312.11(h), with (b)(2) and (g) context; eCFR displayed through 2026-09-03. FTC approved-program directory and May 2020 membership-claims guidance checked 2026-09-06; current approval decisions and individual guidelines must be checked at reliance.

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

What engineering work it implies

Sample acceptance criteria Landfall generates for this obligation:

  • Record the actual operator and each proposed or current covered service; participation is optional and an assessed pathway is not legal approval.
  • Verify current FTC approval, applicable guideline version and service-specific membership/certification from original sources; a badge, application or certificate alone does not establish compliance.
  • Assess actual guideline compliance and the program's at-least-annual independent privacy/security review; preserve findings, remediation and disciplinary history without assuming immunity.
  • Reassess changed features/guidelines, expiry, suspension, departure and revoked approval; remove or correct unsupported public membership claims.
  • Distinguish member-operator conditions from program-administrator reporting, records, public-list and technology-review duties; assign the latter only after a separate actor-specific assessment.

Evidence an auditor expects

  • Assessment documentDocument review

    Operator safe-harbor reliance assessment

    Record the actual operator and each proposed or current covered service; participation is optional and an assessed pathway is not legal approval. Verify current FTC approval, applicable guideline version and service-specific membership/certification from original sources; a badge, application or certificate alone does not establish compliance. Assess actual guideline compliance and the program's at-least-annual independent privacy/security review; preserve findings, remediation and disciplinary history without assuming immunity. Reassess changed features/guidelines, expiry, suspension, departure and revoked approval; remove or correct unsupported public membership claims. Distinguish member-operator conditions from program-administrator reporting, records, public-list and technology-review duties; assign the latter only after a separate actor-specific assessment. Preserve minimized source/version/scope/status evidence and test stale badges, uncovered services and unresolved findings; do not copy child records or unredacted complaints into the general register. Completion is not legal approval.

Questions people ask

Does COPPA 16 CFR §312.11(h) - Operator participation in approved safe harbor prog… apply to my service?
It applies when COPPA assessed activity Q_COPPA_SAFE_HARBOR_RELIANCE: YES.
From when does this apply?
COPPA 16 CFR §312.11(h) - Operator participation in approved safe harbor prog… applies from 21 April 2000. Its current status is: in force.
What evidence does an auditor expect?
Operator safe-harbor reliance 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