Skip to content
COPPA · COPPA-312-STREAMING-AUDIO

COPPA 16 CFR 312.2, 312.5(c)(9), 312.4(d)(4) - Assess child audio and the narrow request-response exception

Assess child-voice audio collection, consent and every condition of the specific-request audio exception, including immediate deletion and online notice

HIGHProcess dutyData collectionBinding regulationIn forceApplies from 22 April 2026

Where this comes from

Provision: 16 CFR 312.2, 312.5(c)(9), 312.4(d)(4) - Assess child audio and the narrow request-response exception

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

Citation: 16 CFR 312.2 (personal information (8), (10)), 312.5(c)(9), 312.4(d)(4), 312.10; 90 FR 16918, effective 23 June 2025, general compliance date 22 April 2026

Text version: 16 CFR 312.2, 312.4, 312.5, eCFR displayed through 3 September 2026, retrieved 6 September 2026; 2025 final rule, 90 FR 16918

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
  • COPPA assessed activity Q_COPPA_CHILD_AUDIO: YES

What engineering work it implies

Sample acceptance criteria Landfall generates for this obligation:

  • Assess actual collection of a file containing the child's voice, including streaming, separately from microphone permission and recognition-capable biometric voiceprints.
  • For 312.5(c)(9), establish the child's specific request and audio-only collection with no other personal information, no other use and no disclosure.
  • Delete the audio immediately after responding so it is not retrievable in the normal course of business; test buffers, queues, logs, caches and storage.
  • Provide the 312.4(d)(4) online notice describing use and immediate deletion; absence of a direct-notice duty under this branch does not remove online notice.
  • Assess spoken/requested personal information, linked identifiers, retained transcripts, training, personalization and actual recipient conduct; unresolved or failed conditions require a separate consent/legal-basis decision.

Evidence an auditor expects

  • Assessment documentDocument review

    Complete exception assessment and implemented boundary evidence

    Source/version/activity-specific evidence: Assess actual collection of a file containing the child's voice, including streaming, separately from microphone permission and recognition-capable biometric voiceprints. For 312.5(c)(9), establish the child's specific request and audio-only collection with no other personal information, no other use and no disclosure. Delete the audio immediately after responding so it is not retrievable in the normal course of business; test buffers, queues, logs, caches and storage. Provide the 312.4(d)(4) online notice describing use and immediate deletion; absence of a direct-notice duty under this branch does not remove online notice. Assess spoken/requested personal information, linked identifiers, retained transcripts, training, personalization and actual recipient conduct; unresolved or failed conditions require a separate consent/legal-basis decision. Preserve minimized deletion/control evidence without raw audio or extra transcripts; consent does not justify unnecessary retention under 312.10. A DRAFT source, selected feature or generated task is not consent or an approved exception.

Questions people ask

Does COPPA 16 CFR 312.2, 312.5(c)(9), 312.4(d)(4) - Assess child audio and the nar… apply to my service?
It applies when COPPA assessed activity Q_COPPA_COVERED_ACTIVITY: YES; COPPA assessed activity Q_COPPA_CHILD_AUDIO: YES.
From when does this apply?
COPPA 16 CFR 312.2, 312.5(c)(9), 312.4(d)(4) - Assess child audio and the nar… applies from 22 April 2026. Its current status is: in force.
What evidence does an auditor expect?
Complete exception assessment and implemented boundary evidence.

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