# Checklist: meeting the amended COPPA Rule, from audience test to retention policy

Thirteen steps for operators of child-directed or mixed audience sites and apps, and those with actual knowledge of users under 13, under 16 CFR part 312 as amended in 2025: separate consent for third-party disclosure, a written security program and a written retention policy.

Checklist · Cross-sector · Data & AI. Published November 14, 2026. Last reviewed November 14, 2026.

## The rule after the 2025 amendments

The Children’s Online Privacy Protection Rule, 16 CFR part 312, makes it unlawful for an operator of a website or online service directed to children, or an operator with actual knowledge that it collects or maintains personal information from a child, to collect that information in a way that breaks the rule. Section 312.2 defines a child as an individual under the age of 13. “Operator” covers commercial websites and online services, and excludes nonprofit entities that would otherwise be exempt from section 5 of the FTC Act [1]. The FTC published amendments on April 22, 2025. They took effect on June 23, 2025, and, except for three safe harbor provisions in section 312.11, regulated entities had until April 22, 2026 to comply [2]. As checked on November 14, 2026, the eCFR text, current to November 12, 2026, reflects these amendments, and a Federal Register search on 2026-11-14 found no later document amending part 312 [1] [2].

The rule reaches across sectors: a bank’s app for young savers, a hospital’s pediatric patient education site or a school-facing product can each raise the question in step 1. The steps assume a commercial operator.

## Using the steps

Steps 1 to 4 decide whether and where the rule applies; steps 5 to 8 cover notices and consent; steps 9 to 12 cover security, retention and parents’ rights; step 13 covers safe harbors and enforcement. Each step cites the section of the current eCFR text it rests on, current to November 12, 2026, and where a step is our suggestion, it says so. The owner under each step is a typical role, not one the rule names. This page explains the rule; it is not legal advice, and state children’s privacy laws may add duties.

Moraph’s teams help organizations with work like this. [See our solutions](https://www.moraph.com/solutions).

## The checklist

1. **For each website, app and portion of a service, decide whether it is directed to children, is mixed audience, or neither, and record the evidence.** (Privacy counsel with product leads) Section 312.2 lists what the FTC considers in deciding whether a service is directed to children, including subject matter, visual content, animated characters, music, the age of models, child celebrities, language and advertising, and also empirical evidence on audience composition and evidence of intended audience such as marketing plans and user reviews [1]. Section 312.3 applies the rule to operators of child-directed services and to operators with actual knowledge that they collect personal information from a child [1].
2. **If a service is mixed audience, put a neutral age screen in front of any collection of personal information.** (Product lead) Under section 312.2, a mixed audience service does not target children as its primary audience and collects no personal information, other than for the limited purposes in section 312.5(c), before collecting age information or using another reasonably calculated means to identify children. The age question must be neutral and must not default to a set age or encourage visitors to falsify their age [1].
3. **Inventory every item of personal information the service collects from children, using the rule’s definition, including identifiers collected by partners and SDKs.** (Data protection lead with engineering) Section 312.2 defines personal information to include names, addresses, online contact information, telephone numbers, government-issued identifiers, persistent identifiers such as cookies, IP addresses and device identifiers, photographs, video or audio files with a child’s image or voice, geolocation precise enough to identify a street and city, and biometric identifiers such as fingerprints, voiceprints, gait patterns and faceprints [1]. Information collected by an agent or service provider, or by another person the operator benefits from allowing, is collected on the operator’s behalf [1].
4. **Where a persistent identifier is collected without consent for internal operations only, list those operations and the controls in the online notice.** (Privacy counsel) Section 312.5(c)(7) allows a persistent identifier, and no other personal information, to be collected without consent solely to support internal operations, and requires the notice under section 312.4(d)(3) [1]. That notice must state the specific internal operations and the means the operator uses to keep the identifier from being used to contact a specific individual, including through behavioral advertising, or to amass a profile [1].
5. **Separate consent to third-party disclosure from consent to collection and use, unless the disclosure is integral to the service.** (Product lead with privacy counsel) Section 312.5(a)(2) requires the operator to let a parent consent to collection and use without consenting to disclosure to third parties, unless the disclosure is integral to the website or online service, and to obtain separate verifiable parental consent to that disclosure [1]. The direct notice must tell the parent this under section 312.4(c)(1)(iv) [1]. Writing down why any disclosure is treated as integral is our suggestion.
6. **Rebuild the direct notice to parents so it has every element section 312.4(c)(1) lists.** (Privacy counsel with the content team) The direct notice for consent must state, among other things, that consent is required and nothing will be collected without it; the items of information, how they will be used and the potential disclosures; the identities or specific categories of third parties and the purposes; a link to the online notice; how to give consent; and that contact details collected to seek consent will be deleted if the parent does not consent within a reasonable time [1].
7. **Update the online notice and place a prominent link to it on the home or landing screen and at each point of collection.** (Privacy counsel with the web and app teams) Section 312.4(d) requires the link on the home or landing page or screen and at each area where personal information is collected from children, close to the request. The notice must give the name, address, telephone number and email address of all operators, describe what is collected and how it is used, the identities and specific categories of third parties and the purposes of disclosure, and the operator’s data retention policy under section 312.10 [1].
8. **Choose consent methods from the list in section 312.5(b)(2), or show that another method is reasonably calculated to ensure the person consenting is the parent.** (Product lead with identity verification team) Section 312.5(b)(1) requires any method to be reasonably calculated, in light of available technology, to ensure the person consenting is the parent [1]. Section 312.5(b)(2) lists methods including a signed form, a payment card with notice of each transaction, a staffed toll-free line or video call, government ID checked against databases and then deleted promptly, knowledge-based questions a child could not answer, and a photo ID matched to the parent’s face with trained personnel confirming, with the images deleted promptly. Email plus and text message plus are available only to operators that do not disclose children’s personal information [1].
9. **Adopt a written information security program for children’s personal information, with a named coordinator and an annual risk assessment and review.** (CISO) Section 312.8(b) requires a written program appropriate to the sensitivity of the information and the operator’s size and complexity. It requires the operator to designate one or more employees to coordinate it, assess risks at least annually, design and maintain safeguards for the risks found, regularly test and monitor them, and evaluate and modify the program at least annually [1].
10. **Before any service provider or third party collects, holds or receives children’s data, check its capability and get written assurances.** (Vendor risk manager) Section 312.8(c) requires the operator to take reasonable steps to determine that other operators, service providers and third parties can maintain the confidentiality, security and integrity of the information, and to obtain written assurances that they will use reasonable measures to do so [1].
11. **Write and publish a data retention policy for children’s personal information with a deletion timeframe, and delete securely.** (Records manager with the data protection lead) Section 312.10 allows retention only as long as reasonably necessary for the specific purpose and bars indefinite retention. It requires a written retention policy setting out the purposes for collection, the business need for retention and a timeframe for deletion, published in the online notice, and deletion using reasonable measures against unauthorized access [1].
12. **Set up a way for parents to review their child’s information, refuse further collection and have it deleted, and check no activity asks for more than it needs.** (Customer support lead with privacy counsel) Section 312.6(a) requires the operator, on a parent’s request, to describe the types of personal information collected, let the parent refuse further use or collection and direct deletion, and give a means of reviewing the information, after making sure the requester is the parent without undue burden [1]. Section 312.7 bars conditioning a child’s participation in a game, prize or other activity on disclosing more personal information than is reasonably necessary [1].
13. **If the operator belongs to an FTC-approved safe harbor program, follow its guidelines; either way, keep evidence of each step.** (Chief privacy officer) Under section 312.11(h), an operator that complies with Commission-approved safe harbor guidelines is deemed to comply with sections 312.2 through 312.8 and 312.10 [1]. The compliance date of April 22, 2026 did not apply to sections 312.11(d)(1), (d)(4) and (g) [2], which set safe harbor programs’ own dates: a public list of subject operators no later than July 21, 2025, and a first annual report and proposed guideline changes by October 22, 2025 [1]. Section 312.9 treats a violation as a violation of a rule defining an unfair or deceptive act or practice under section 18(a)(1)(B) of the FTC Act [1]. Keeping dated evidence for each step is our suggestion.

## Sources

1. Electronic Code of Federal Regulations. 16 CFR part 312, Children’s Online Privacy Protection Rule, current text up to date as of November 12, 2026. <https://www.ecfr.gov/current/title-16/chapter-I/subchapter-C/part-312> Checked November 14, 2026.
2. Federal Trade Commission (Office of the Federal Register, via govinfo). Children’s Online Privacy Protection Rule, final rule, 90 FR 16918 (April 22, 2025). <https://www.govinfo.gov/content/pkg/FR-2025-04-22/html/2025-05904.htm> Checked November 14, 2026.

Published: November 14, 2026
Canonical URL: <https://insights.moraph.com/checklist-coppa-rule-2025-amendments-consent-security-retention>
Publisher: Moraph Insights
