Join our Newsletter — 33% off our NHI Course
Home› Guides› COPPA Rule 2025 Amendments Guide: Security Programme, Retention…
Guide Privacy & Data Protection

COPPA Rule 2025 Amendments Guide: Security Programme, Retention Limits and Consent Changes

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, under the editorial direction of Lalit Choda Updated 18 November 2026 14 min read
On this page

The 2025 amendments to the FTC's Children's Online Privacy Protection Rule turn general security and retention duties into written, testable programmes, and the compliance date of 22 April 2026 has now passed. The Federal Trade Commission announced the final amendments on 16 January 2025 and published them in the Federal Register on 22 April 2025 (90 FR 16918). They took effect on 23 June 2025, and most regulated operators had until 22 April 2026 to comply. This guide focuses only on what changed: the written information security programme in 16 CFR 312.8, the written data retention policy in 312.10, separate parental consent for third-party disclosure, new consent methods, wider definitions and new safe harbour reporting. For the underlying law, who it covers and the general obligations that did not change, see the COPPA and Children's Privacy Guide.

This page is general information, not legal advice. Status as of 17 Nov 2026. Confirm obligations against the final rule in the Federal Register and with qualified counsel.

Key takeaways

  • The amended Rule has been in force since 23 June 2025. For most provisions the compliance date was 22 April 2026, so operators should now be able to show working controls, not plans.
  • Section 312.8 now requires a written information security programme with a named coordinator, at least annual risk assessments, safeguards, regular testing and monitoring, and at least annual review.
  • Before sharing children's data, operators must take reasonable steps to check that recipients can keep it secure and obtain written assurances that they will.
  • Section 312.10 requires a written data retention policy, posted in the online notice, stating purposes, business need and a deletion timeframe. Children's data may not be kept indefinitely.
  • Disclosure of children's personal information to third parties, including for targeted advertising, now needs separate verifiable parental consent unless the disclosure is integral to the service.
  • Biometric identifiers and government-issued identifiers are now personal information, which pulls voiceprints, faceprints and similar templates into scope.
  • FTC-approved safe harbour programmes must publish membership lists and give the Commission more detailed reports.

The 2025 COPPA amendments at a glance

ItemWhat changedRule section
AnnouncementFinal rule announced by the FTC on 16 January 2025, approved 5-0 for publicationFTC press release
PublicationFederal Register, 22 April 2025, document 2025-0590490 FR 16918
Effective date23 June 2025Whole Rule
Compliance date22 April 2026, except 312.11(d)(1), (d)(4) and (g)Whole Rule
SecurityWritten information security programme and third-party assurances312.8
RetentionRetain only as long as reasonably necessary for specific purposes; written policy posted online; no indefinite retention312.10
Third-party disclosureSeparate verifiable parental consent for disclosure not integral to the service312.5(a)(2)
NoticesDirect notice names third parties or their categories and purposes; online notice explains internal-operations use of persistent identifiers312.4
Consent methodsNew methods including face match to verified photo ID and "text plus"; email plus redesignated312.5(b)(2)
DefinitionsBiometric identifiers, government-issued identifiers, mixed audience service, mobile number as online contact information312.2
Safe harboursPublic membership lists, fuller annual reports, triennial technology reports312.11

The Commission did not finalise its proposed limits on push notifications to children or its proposed changes for education technology providers in school settings.

Scope

The amendments do not change who COPPA applies to. The Rule still covers operators of websites and online services directed to children under 13, and operators with actual knowledge that they collect personal information from a child under 13. What changes is how much of a service's data and infrastructure falls inside that scope, and what evidence the operator must hold.

Wider personal information

Personal information now includes a biometric identifier that can be used for the automated or semi-automated recognition of an individual. The final rule gives examples such as fingerprints, handprints, retina and iris patterns, genetic data including DNA sequences, voiceprints, gait patterns, facial templates and faceprints. The Commission dropped a proposed reference to "data derived from voice data, gait data, or facial data". Government-issued identifiers, such as a Social Security number or a state identification card, are also listed, with the examples stated as non-exhaustive.

For engineering teams this means feature stores, embedding stores, voice assistants, face-based login, avatar tools and identity verification pipelines can all hold COPPA personal information, even where no name or email is stored.

Mixed audience services

The Rule now defines a mixed audience website or online service as a standalone term. Such a service may not collect personal information from any visitor, beyond the limited exceptions in 312.5(c), before it collects age information or uses another reasonably calculated means to determine whether the visitor is a child. The FTC states that mixed audience services remain a subset of child-directed services, so the full Rule applies to the child users once identified. Age screening therefore becomes the first control in the data flow, not an afterthought.

Online contact information

A mobile telephone number now counts as online contact information, but only where the operator uses it solely to send text messages to a parent to obtain consent. This supports the new text-based consent method without opening a general channel to the child.

Key obligations

Written information security programme (312.8)

Section 312.8 already required operators to establish and maintain reasonable procedures to protect the confidentiality, security and integrity of children's personal information. The amendment adds a written programme with safeguards suited to the sensitivity of the data and to the operator's size, complexity and nature of activities. The programme must:

  • designate one or more employees to coordinate it. The final rule allows that person to hold other duties;
  • identify and, at least annually, assess internal and external risks to children's personal information;
  • design, implement and maintain safeguards to control the identified risks;
  • regularly test and monitor the effectiveness of those safeguards;
  • be evaluated and modified at least annually in light of the testing, monitoring and any material changes.

The final rule uses the term "information security program" rather than the proposed "children's personal information security program". An operator does not need a separate programme if its general programme meets the requirements for children's data. In practice the FTC will expect to see that children's data is named in the scope, risk register and test plan of that general programme.

Third-party assurances

Before releasing children's personal information to other operators, service providers or third parties, an operator must take reasonable steps to determine that the recipient is capable of maintaining its confidentiality, security and integrity, and must obtain written assurances that it will do so. This is a vendor due diligence duty tied to each data release, and it applies to processors such as analytics, cloud storage and support tooling as much as to advertising partners.

Data retention and deletion (312.10)

The Rule now limits retention to as long as reasonably necessary for the specific purposes for which the information was collected. The final rule dropped proposed "secondary purpose" language. Information must be deleted using reasonable measures when it is no longer reasonably necessary, and it may not be retained indefinitely.

Operators must have a written data retention policy addressing personal information collected from children. It must set out the purposes for collection, the business need for retaining the information and the timeframe for deleting it, and it must be included in the online notice required by 312.4(d). As with security, an operator may use a general retention policy if it covers children's data.

Separate consent for third-party disclosure (312.5(a)(2))

Operators must obtain separate verifiable parental consent before disclosing a child's personal information to third parties, unless the disclosure is integral to the website or online service. The FTC press release summarises this as requiring parents to opt in to third-party advertising. Parents may consent to collection and use without consenting to disclosure for non-integral purposes, and the operator may not condition the child's participation on that disclosure. The rule does not ban targeted advertising outright, but it makes it an opt-in choice that is off unless the parent agrees.

Notice changes (312.4)

The direct notice to parents must now identify the third parties to which information will be disclosed, by name or by category, and the purposes of each disclosure, and must state that the parent can consent to collection without consenting to that disclosure. The online notice must include the written retention policy. A new 312.4(d)(3) requires operators relying on the internal-operations exception for persistent identifiers to describe that use in the online notice, which helps the FTC monitor how the exception is used.

Consent methods (312.5(b)(2))

The amendments add methods of verifiable parental consent, including matching a facial image to a verified photo identification document, which the Commission described as requiring human review, and a "text plus" method at 312.5(b)(2)(ix) that can be used where the child's information is not disclosed. The existing "email plus" method is redesignated as 312.5(b)(2)(viii). All methods must remain reasonably calculated, in light of available technology, to ensure that the person giving consent is the parent.

Safe harbour programmes (312.11)

FTC-approved safe harbour programmes must publicly post a list of their current participating operators and certified services, updated every six months. Annual reports to the Commission must include a narrative description of the programme's business model, copies of relevant consumer complaints and a description of disciplinary processes. Programmes must also submit triennial reports on their technological capabilities and their methods for assessing members. Sections 312.11(d)(1), (d)(4) and (g) carry separate compliance dates from the April 2026 date.

Enforcement and penalties

The COPPA Rule is enforced by the FTC, and state attorneys general may also bring actions under the statute. A violation of the Rule is treated as an unfair or deceptive act or practice, and the Commission can seek civil penalties for each violation, at amounts it adjusts every year for inflation. Settlements in COPPA cases commonly add injunctive terms, deletion of unlawfully held data and long-term compliance reporting on top of money penalties. Under the amended Rule, a missing written security programme, a retention policy that is not posted, or advertising disclosures made without separate consent are each concrete, checkable failures, which makes them easier to allege than a general claim that security was unreasonable.

Operators that belong to an approved safe harbour programme are deemed compliant while they follow its guidelines, but the new reporting and publication duties mean the FTC will see more of what those programmes find.

What it means for security and identity teams

Treat the programme as auditable evidence

The 312.8 elements are close to a standard information security management system. Teams that already run ISO/IEC 27001 or the NIST Cybersecurity Framework can map each element: the coordinator to a named role, the annual risk assessment to the risk register, safeguards to the control set, testing to the vulnerability and control testing programme, and annual evaluation to management review. The gap for most organisations is not the controls but the evidence that children's data is specifically in scope.

Find where children's data and biometric templates live

Biometric identifiers in scope mean that face, voice and gait templates, and the embeddings and models derived from them for recognition, need inventory, access control and deletion. Data discovery must reach object storage buckets, data warehouses, model training sets, logs and backups. If a template can be used to recognise a child, it is personal information whether or not a name is attached.

Control machine access to children's data

Most access to children's data in a modern service is by non-human identities: service accounts, API keys, ETL jobs, analytics connectors, AI agents and third-party SDKs. A programme that only reviews employee access will miss the main risk. Scope service accounts and tokens that can read children's data, give them least privilege, rotate their secrets, and log what they read. Every outbound integration that receives children's data is a 312.8 third-party release and needs a written assurance and, where it is not integral to the service, a separate parental consent.

Make deletion real

The no-indefinite-retention rule applies to derived copies. Deletion jobs must reach replicas, caches, analytics exports, model training corpora and vendor copies. Where full deletion from a trained model is not feasible, teams should document the decision and limit future use, and seek advice, because retention of children's data inside models is a likely area of scrutiny. See AI Data Retention and Deletion for engineering patterns.

Consent and age signals are identity data too

Parental consent records, government ID images used for face matching and phone numbers used for text plus are themselves sensitive. Store them separately, limit who and what can read them, and set short retention once verification is complete, consistent with the retention policy.

Compliance steps

  1. Confirm scope. Decide whether each service is child-directed, mixed audience or general audience with actual knowledge, and record the reasoning.
  2. Inventory children's data. List every data element, including biometric and government identifiers, every store and every non-human identity with access.
  3. Map disclosures. List each third party that receives children's data, its purpose and whether that disclosure is integral to the service.
  4. Write or extend the security programme. Name the coordinator, put children's data in the risk assessment, document safeguards, schedule testing and set the annual review date.
  5. Collect written assurances. Add children's data security terms to contracts with every recipient and keep evidence of due diligence before release.
  6. Write the retention policy. For each data category, state the purpose, business need and deletion timeframe, then publish it in the online notice.
  7. Rebuild consent flows. Separate consent for collection from consent for third-party disclosure, keep non-integral sharing off by default, and update the direct notice.
  8. Review consent methods. If adopting face match or text plus, run a privacy and security review of the vendor and the stored artefacts.
  9. Test and record. Test deletion, access controls and vendor controls, and retain dated evidence for the annual evaluation.

NHI Mgmt Group recommends running a first full internal review now if one was not completed before 22 April 2026, since the FTC can examine practices from that date onwards.

Common failure patterns

  • A general security policy exists, but children's data is not named in its scope, risk assessment or tests.
  • The designated coordinator is a job title with no time, budget or reporting line.
  • Analytics and advertising SDKs are added by product teams without a written assurance or a consent check.
  • Retention periods are written as "as long as needed" without a timeframe, which does not meet the policy content rule.
  • Deletion covers the production database but not backups, warehouses, vendor copies or training data.
  • Service account and API key access to children's data is never reviewed.
  • Voice or face features are launched without treating the templates as personal information.
  • Consent artefacts, such as ID images, are kept indefinitely after verification.

Practitioner checklist

  • Record which services are child-directed or mixed audience, and the date of the decision.
  • Name the information security programme coordinator in writing.
  • Show a dated annual risk assessment that covers children's personal information.
  • Keep a test and monitoring plan with results for safeguards protecting children's data.
  • Hold written security assurances from every recipient of children's data.
  • Publish a retention policy with purpose, business need and deletion timeframe per data category.
  • Show separate, off-by-default consent for non-integral third-party disclosure.
  • Inventory biometric and government identifiers and the non-human identities that can read them.
  • Test deletion end to end, including backups and vendor copies.
  • Set the next annual programme evaluation date.

Standards and references

Related NHI Mgmt Group resources: COPPA and Children's Privacy Guide · Age Assurance and Children's Design Codes · AI Data Retention and Deletion · Data Retention and Disposal Policy Template

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick both boxes to continue.