Skip to content
COPPA · COPPA-312-8-DATA-SECURITY

COPPA 16 CFR 312.8(a)-(c) - Written information security program and recipient safeguards

Maintain a written, risk-based children's information security program, annual assessments and updates, regular safeguard testing, and prior written recipient assurances

CRITICALRequirementData processingBinding regulationIn forceApplies from 22 April 2026

Where this comes from

Provision: 16 CFR 312.8(a)-(c) - Written information security program and recipient safeguards

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

Citation: 16 CFR 312.8(a)-(c); 90 FR 16918 (22 April 2025), amended rule effective 23 June 2025, general compliance date 22 April 2026

Text version: 16 CFR Part 312, 2025 amended Rule (90 FR 16918); eCFR as of 3 September 2026; retrieved 6 September 2026

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:

  • Establish, implement and maintain a written program proportionate to children's information sensitivity and the operator's size, complexity and activities; designate employee coordinators.
  • Identify internal/external risks and safeguards' sufficiency, reassess at least annually, and implement controls based on information volume, sensitivity and likelihood of compromise.
  • Regularly test and monitor safeguard effectiveness; at least annually evaluate and modify the program for risks, results, methods and other material circumstances.
  • Before on-behalf collection/maintenance or release, reasonably assess recipient capability and obtain written assurances of reasonable protection measures.
  • Preserve minimized, attributable program, assessment, test and recipient evidence; justify chosen technologies without claiming that this provision mandates an algorithm or independent audit.

Evidence an auditor expects

  • Policy documentDocument review

    Written security program and implemented controls

    Reviewed evidence for the assessed activity and applicable source version: Establish, implement and maintain a written program proportionate to children's information sensitivity and the operator's size, complexity and activities; designate employee coordinators. Identify internal/external risks and safeguards' sufficiency, reassess at least annually, and implement controls based on information volume, sensitivity and likelihood of compromise. Regularly test and monitor safeguard effectiveness; at least annually evaluate and modify the program for risks, results, methods and other material circumstances. Before on-behalf collection/maintenance or release, reasonably assess recipient capability and obtain written assurances of reasonable protection measures. Preserve minimized, attributable program, assessment, test and recipient evidence; justify chosen technologies without claiming that this provision mandates an algorithm or independent audit. A generated task, policy document alone or DRAFT source does not establish implemented compliance.

Questions people ask

Does COPPA 16 CFR 312.8(a)-(c) - Written information security program and recipien… apply to my service?
It applies when COPPA assessed activity Q_COPPA_COVERED_ACTIVITY: YES.
From when does this apply?
COPPA 16 CFR 312.8(a)-(c) - Written information security program and recipien… applies from 22 April 2026. Its current status is: in force.
What evidence does an auditor expect?
Written security program and implemented controls.

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