At a Glance
- The COPPA Rule applies to operators of websites, apps, and online services that are directed to children under 13 or that knowingly collect personal information from them.
- The FTC’s 2025 amendments took effect June 23, 2025, and the compliance deadline passed on April 22, 2026.
- Operators need verifiable parental consent before collecting a child’s personal information, and separate consent before disclosing it to third parties unless the disclosure is integral to the service.
- The amendments also added a written information security program and a written retention policy, and they prohibit indefinite retention.
- Civil penalties can reach USD 53,088 per violation, and the Department of Justice announced a USD 400 million settlement with TikTok and ByteDance in August 2026.
- COPPA 2.0 is not law. The Senate passed S.836 on March 5, 2026, and the House passed the KIDS Act, which includes COPPA 2.0, on June 29, 2026.
What Is the Children’s Online Privacy Protection Act (COPPA)?
The Children’s Online Privacy Protection Act (COPPA) is a federal privacy law in the United States that was passed in 1998 and came into effect in 2000. The FTC’s implementing regulation, the COPPA Rule (16 CFR Part 312), is often referred to by the same acronym.
The FTC has revised the COPPA Rule several times since it took effect in 2000, most significantly in 2013 and again in April 2025. The latter represents the first major update to the Rule in over a decade. The 2025 amendments, which took effect on June 23, 2025, and which operators were required to meet by April 22, 2026, introduced expanded definitions of personal information, new requirements for parental consent, and stricter data security and retention obligations.
Which Organizations Does COPPA Apply to?
The Children’s Online Privacy Protection Act applies to organizations that knowingly collect the personal information of children under age 13 online. However, because websites and social platforms are ecosystems, not silos, the law goes into more detail and applies to organizations that:
- Knowingly collect children’s personal information from users of another website or online service directed at children
- Knowingly collect children’s personal information even though the website or online service is directed at a general audience
- Run supplementary services with their website, app, or other service (e.g., ad network) and know that the supplementary services collect personal information from children under 13
How Does COPPA Define Personal Information?
Personal information within the scope of COPPA is fairly standard compared to other privacy laws, though it is a little more detailed regarding online account identifiers and digital media. Under Part 312.2 (Definitions), it includes:
- First and last name
- Home or other physical address
- Online contact information
- Screen name or username where it functions the same as online contact information
- Telephone number
- A government-issued identifier, such as a Social Security, state identification card, birth certificate, or passport number
- A “persistent identifier” that can be used to recognize a user over time and across different websites or online services, including, but not limited to, customer number held in a cookie, an Internet Protocol (IP) address, a processor or device serial number, or unique device identifier
- A photograph, video, or audio file containing the child’s image or voice
- Geolocation information sufficient to identify street name and name of a city or town
- Information concerning the child or the parents of that child that the operator collects online from the child and combines with an identifier
- A biometric identifier that can be used for the automated or semi-automated recognition of an individual, such as fingerprints, handprints, retina patterns, iris patterns, genetic data (including a DNA sequence), voiceprints, gait patterns, facial templates, or faceprints
How Does COPPA Define Websites and Online Services?
COPPA became law in 1998 before many of today’s popular online social platforms were developed, and before the ubiquity of smartphones and apps.
Sites such as SixDegrees and Classmates existed in the late 1990s, but LinkedIn and MySpace did not launch until 2003. Facebook arrived in 2004, Twitter in 2006, and Instagram in 2010. The iPhone launched in 2007, and TikTok reached a worldwide audience in 2018.
COPPA has been updated over the years to reflect digital advances, and its definition of a “website or online service” includes:
- Mobile apps that send or receive information online (like network-connected games, social networking apps, or apps that deliver behaviorally-targeted ads)
- Internet-enabled gaming platforms
- Plug-ins
- Advertising networks
- Internet-enabled location-based services
- Voice-over-internet-protocol (VoIP) services
- Connected toys or other Internet of Things devices
How Does COPPA Determine Whether a Website or Online Service Targets Children?
In Part 312.2 (Definitions), the Rule states:
In determining whether a Web site or online service, or a portion thereof, is directed to children, the Commission will consider its subject matter, visual content, use of animated characters or child-oriented activities and incentives, music or other audio content, age of models, presence of child celebrities or celebrities who appeal to children, language or other characteristics of the Web site or online service, as well as whether advertising promoting or appearing on the Web site or online service is directed to children. The Commission will also consider competent and reliable empirical evidence regarding audience composition, and evidence regarding the intended audience, including marketing or promotional materials or plans, representations to consumers or to third parties, reviews by users or third parties, and the age of users on similar websites or services.
A service that meets this test but does not target children as its primary audience is treated as mixed audience if it:
- Does not collect personal information from any visitor, other than for the limited purposes in § 312.5(c), before collecting age information or using another reasonable means to determine whether the visitor is a child
- Prevents the collection, use, or disclosure of personal information from visitors who identify themselves as under age 13 without first complying with notices and provisions regarding parental consent
- Refers or links to a child-directed service only through information location tools, such as a directory or search index, which does not by itself make the referring service child-directed
The FTC’s 2025 Rule amendments introduced a formal, standalone definition of “mixed audience website or online service,” codifying guidance that had previously existed only in the FTC’s FAQ materials. A mixed-audience site meets COPPA’s multi-factor child-directed test but does not target children as its primary audience.
Operators of such sites must age-screen visitors and apply COPPA’s notice and consent requirements to any visitor identified as under 13. The 2025 Rule also expanded the factors the FTC will consider when determining whether a site is directed to children, including marketing materials, representations made to third parties, and the ages of users on similar services. The amendment also expands the definition of “online contact information” and “personal information”. The latter now includes biometric data and government-issued identifiers.
What Protections Do Children Have Under COPPA?
The personal information of children under 13 cannot be collected, used, or disclosed without verifiable parental consent when a service is directed to children or the operator has actual knowledge that it is collecting personal information from a child.
COPPA uses an opt-in model, requiring consent to be obtained before any personal data collection. Some other privacy laws, like the EU’s General Data Protection Regulation (GDPR) and Brazil’s Lei Geral de Proteção de Dados Pessoais (LGPD), apply special consent or parental authorization rules to children’s data, though they also allow other legal bases in some cases.
Under most U.S. state privacy laws, consent is generally not required before personal data is collected. Instead, consumers can opt out of specific uses, such as sale, sharing, profiling, or targeted advertising. Those laws, however, typically require opt-in consent for sensitive data, and several require it for the sale of data from known minors or its use in targeted advertising.
Requirements for Parental Consent Under COPPA
Before operators can collect, use, or disclose children’s personal information, they must obtain verifiable parental consent. Because children cannot legally consent themselves, it must be obtained from a parent or guardian. There is leeway in how parents/guardians are informed about the request to collect information, and the purposes for its use.
The FTC’s 2025 Rule amendments strengthened these requirements in two material ways. First, operators must now obtain separate verifiable parental consent before disclosing children’s personal information to third parties, including for targeted advertising. Disclosure that is integral to the website or online service is the exception. A single general consent for collection no longer covers other downstream sharing.
Second, the 2025 amendments added new acceptable methods for obtaining consent: knowledge-based authentication, comparison of a government photo ID with a face image using facial recognition technology, and a text message coupled with additional steps. The text message method is available only when the operator does not disclose children’s personal information.
Regardless of the technology or platform used, the method must clearly communicate what personal information from the child would be collected, and how, and how it would be used and potentially shared with any third parties.
The organization must also take reasonably robust steps to verify that the parent/guardian is the one providing the consent.
Acceptable methods of obtaining parental consent include:
- Fax, mail, or electronic scan
- Online payment system that provides the account holder of separate transaction notifications
- Calling a toll-free number staffed by trained personnel
- Video conferencing with trained personnel
- Providing a copy of government-issued identification verifiable against a database, provided the identification is promptly deleted after the verification process
- Answering a series of knowledge-based questions difficult for someone other than the parent to answer
- Verifying a picture of a driver’s license or other photo identification submitted by the parent and using facial recognition technology to compare it to a second photo also submitted by the parent
Parents also have the option to provide consent to the collection and use of the child’s personal information by the requesting organization, but refuse consent for the disclosure of the information to third parties.
If a child’s personal information will be collected but only used internally by the organization collecting it, and not disclosed, “email plus” consent and verification is acceptable. The 2025 amendments added a comparable “text plus” method, which also applies only when the operator does not disclose the information. By this method, the organization emails the parent, who responds with their consent. Confirmation of consent is then sent to the parent via email, letter, or phone call.
Parents/guardians must be informed that they can revoke consent at any time, and if changes are made to the collection, use, or disclosure practices consented to, new notification must be provided and new consent obtained.
Exceptions to Consent Requirements Under COPPA
There are some instances wherein consent is not required to collect or use children’s personal information, though it should be noted that there may be specific notification requirements even if one or more of these conditions are met.
The following conditions and purposes outline when the child’s, parent’s, or contact information of both can be collected without consent.
- The child’s and parent’s name and online contact information may be collected for the purpose of:
- Protecting the child’s safety
- Obtaining parental consent, and must be deleted if consent is not obtained within a reasonable period of time
- Directly responding more than once to a child’s specific request, such as a newsletter subscription, with notice to the parent and no combination with other information about the child
- The parent/guardian’s online contact information may be collected for the purpose of:
- Providing notification about the child’s participation on a site or service that does not collect personal information
- The child’s online contact information may be collected for the purpose of:
- Directly responding to a child’s specific one-time request (e.g. entering a contest), provided the information is not used again for any other purpose and is deleted after responding
- Protecting the security or integrity of the website or online service, to take precautions against liability, to respond to judicial process, or (as permitted by law) to provide information to law enforcement
- A persistent identifier may be used for the purpose of:
- Supporting internal operations of the website or online service, with the notice required by § 312.4(d)(3), including:
- Maintaining or analyzing the functioning of the site
- Performing network communications
- Authenticating users of the site or personalizing content
- Serving contextual ads or frequency capping
- Protecting the security or integrity of the user or the site
- Legal or regulatory compliance
- Fulfilling a child’s request under the one-time contact or multiple contact exceptions
- Supporting internal operations of the website or online service, with the notice required by § 312.4(d)(3), including:
- A persistent identifier may be collected without parental consent from a returning user if all of the following apply:
- The operator collects only a persistent identifier and no other personal information
- The individual affirmatively interacts with the website or online service to trigger the collection
- The person’s previous registration with the operator, such as an age screen, indicates they are 13 or over
- An audio file containing a child’s voice, and no other personal information, may be collected to respond to the child’s specific request. The operator cannot use or disclose the file for any other purpose and must delete it immediately after responding. [This was added by the 2025 amendments, § 312.5(c)(9).]
Safe Harbor Programs and COPPA Compliance for Industry Groups
Industry groups can submit self-regulatory guidelines that implement COPPA requirements to the FTC for approval. Operators that follow FTC-approved guidelines as members of a Safe Harbor Program may be treated as meeting the covered requirements of the Rule for enforcement purposes.
The 2025 Rule amendments strengthened oversight of the Safe Harbor Program in two ways. The FTC’s review of Safe Harbor programs now explicitly extends to security policies and practices, as well as privacy, which expands the scope of the review.
Safe Harbor programs are also now required to publicly disclose their full membership lists and submit additional reporting to the FTC on an ongoing basis. Organizations relying on Safe Harbor membership for COPPA compliance should confirm their program has updated its practices to reflect these requirements.
What Responsibilities Do Companies Have Under COPPA?
Operators’ obligations under COPPA are detailed. As already noted, parental consent must be obtained under many circumstances before children’s personal data can be collected or used. Under the 2025 amendments, operators must maintain a written information security program appropriate to their size and the sensitivity of the data. The program must designate one or more employees to coordinate it, and it must include annual risk assessments and annual testing and monitoring of safeguards.
Companies must also provide an easily accessible privacy policy listing the following:
- All third parties collecting children’s personal information, e.g. social platform plug-ins, ad networks, etc.
- Name and contact information for each third party (phone number, address, email address)
- How those organizations will use the personal information
- Description of what personal information is collected, and how it’s used
- Must include types of personal information collected, e.g. name, address, email address, hobbies, etc.
- How the personal information is collected, e.g. via the child’s direct input, through cookies, etc.
- How the personal information will be used, e.g. marketing to the child, contest notification, enabling the child to make the information publicly available, like on the website
- Whether the personal information is disclosed to third parties (if so, see above re. requirements about those organizations)
- Description of parental rights
- Parents can review children’s personal information, direct the organization to delete it, and refuse further collection or use of the information
- Parents can agree to collection and use of children’s personal information but refuse to allow disclosure to third parties, unless that is part of the service (e.g. social platforms)
- Procedures for exercising their rights
- Data retention policy: the business need for retaining children’s personal information and the time frame for deleting it
- Children will not be required to disclose any more information than is reasonably necessary to participate in an activity
Operators must also follow the retention rules described in the section on data retention and deletion below.
COPPA Enforcement and Penalties
COPPA violators may face civil penalties of up to USD 53,088 per violation, a figure the FTC adjusts annually for inflation and did not change for 2026. The FTC enforces COPPA, and state attorneys general may also bring actions under the statute. Google was fined USD 170 million in 2019 for violations on YouTube, where children’s personal information was collected without consent and used to target them with advertising.
It should be noted that, while foreign companies are subject to COPPA if they collect or use the personal information of American children, the FTC has pursued them. Recent cases involving ByteDance, Cognosphere, and Apitor show that operators based outside the United States are within its reach.
The FTC reached a USD 5.7 million settlement with ByteDance in 2019 over COPPA violations on the TikTok platform, which at the time was one of the larger COPPA actions. The FTC has since substantially escalated enforcement, with penalties in subsequent cases reaching into the tens of millions of dollars. In August 2026, the Justice Department announced a USD 400 million settlement with TikTok and ByteDance. In the same month, Meta agreed to a multi-state settlement valued at up to USD 17 billion over ten years, with COPPA among the claims.
On February 25, 2026, the FTC said it intends to initiate a review of the COPPA Rule to address age verification mechanisms. Operators that rely on age screening should monitor it closely.
COPPA 2.0 and the KIDS Act: Legislation to Watch
The U.S. Senate passed the Children and Teens’ Online Privacy and Protection Act — widely known as COPPA 2.0 — by unanimous consent on March 5, 2026. Rather than advancing as standalone legislation, COPPA 2.0’s core provisions were subsequently folded into the broader KIDS Act (H.R. 7757), alongside the Kids Online Safety Act (KOSA) and new data broker provisions targeting minors’ data.
On June 29, 2026, the House passed the KIDS Act by a vote of 267–117. This Act is a multi-bill omnibus package incorporating the core provisions of COPPA 2.0 alongside a version of KOSA, and the bill was referred to the Senate Commerce Committee on July 13.
The House-passed version omits the duty-of-care standard central to the Senate’s own KOSA proposal, a departure that has drawn immediate objection from Senate sponsors of that bill. Reconciling the two chambers’ approaches, and resolving First Amendment concerns raised by digital rights advocates over age-verification mandates, remains an open question, and enactment is not assured.
That Senate track advanced further on August 5, 2026, when the Senate Commerce, Science, and Transportation Committee voted to approve its own version of KOSA (S.1748), retaining the duty-of-care standard the House version had dropped, along with three companion bills:
- Youth AI Privacy Act
- Children’s Health, Advancement, Trust, Boundaries, and Oversight in Technology (CHATBOT) Act
- Children’s Artificial Intelligence Toy Safety Act
As of November 2026, the full Senate has not voted on these bills, and Congress is in its lame-duck session. Bills that are not enacted before the 119th Congress ends in early January 2027 must be reintroduced. The CHATBOT Act would require AI chatbot providers to offer family accounts and verifiable parental consent for minors, adding a fresh compliance dimension for platforms whose services touch AI-driven interactions with young users.
Whether and how these committee-approved measures are reconciled with the House’s KIDS Act remains unresolved, and the overall legislative outcome is still uncertain.
The COPPA 2.0 provisions would make several substantive changes to the existing framework. In the Senate-passed bill, it would extend protections to teens under 17 (ages 13 to 16), not only children under 13. It would expand COPPA’s “actual knowledge” standard to include “knowledge fairly implied on the basis of objective circumstances,” making it harder for operators to claim they were unaware that a user was a minor. It would introduce a right to deletion for both children and teens.
It would also establish COPPA 2.0 as a floor for state-level protections, explicitly permitting states to enact stronger requirements.
Because the House and Senate have passed different bills and neither has been enacted, COPPA 2.0 is not yet law, and current compliance obligations remain governed by the existing COPPA statute and the FTC’s 2025 Rule amendments. Nonetheless, businesses handling data from younger audiences should monitor its progress, as enactment would materially expand the scope of compliance obligations, particularly for platforms serving teenagers.
Data Retention and Deletion Requirements Under COPPA
Data retention and deletion requirements were introduced into COPPA by the 2013 amendments. Under Section 312.10, operators may retain children’s personal information only for as long as necessary to achieve the purpose for which it was collected.
This is fairly standard in other privacy laws as well. Additionally, reasonable measures must be taken in deleting the information to protect it from unauthorized access or use.
As noted above, prior to deletion, if the purpose for collection changed, either by the organization that collected it or an approved third party processor, the parent or guardian must be notified and new consent obtained for the new use.
The 2013 amendments also added the requirement that third parties to which children’s personal information was disclosed have reasonable security measures in place to protect data. The FTC’s 2025 Rule amendments went further still, explicitly prohibiting indefinite retention of children’s personal information and requiring operators to maintain a written data retention policy specifically addressing children’s data. The policy must state the purposes for collection, the business need for retention, and the time frame for deletion, and it may form part of a broader organizational retention policy.
Usercentrics supports opt-out workflows, notice and disclosures, consent documentation, and geotargeted configurations across U.S. state and federal privacy laws. Start your 14-day free trial today.
Regulation of Children’s Privacy Internationally
COPPA is one of many children’s privacy laws. Most others cover older age groups and add duties on design, age assurance, and parental involvement. The table below compares the main regimes outside the United States.
How Do They Compare?
| Jurisdiction | Key Law | Age Covered | Core Requirements | Status and Enforcement |
| Australia | Privacy Act 1988; Children’s Online Privacy Code (in development) | Children, as defined in the code | Services likely to be accessed by children must meet additional requirements for handling their personal information, on top of the Australian Privacy Principles. | The Office of the Australian Information Commissioner (OAIC) consulted on an exposure draft from March 31 to June 5, 2026. The final code must be registered by December 10, 2026. |
| Brazil | LGPD (Art. 14); ECA Digital (Law 15.211/2025) | Children and adolescents (under 18) | Under the LGPD, companies must state what data they collect and why, make reasonable efforts to obtain parental consent, and verify it. ECA Digital adds risk prevention, age assurance, and parental supervision for services aimed at, or likely to be accessed by, young people. | The LGPD has applied since September 2020. ECA Digital has been in force since March 17, 2026, and the National Data Protection Authority (ANPD) enforces it. |
| China | Personal Information Protection Law (PIPL), Arts. 28, 29, and 31; Provisions on the Cyber Protection of Children’s Personal Information (2019) | Under 14 | Personal information of minors under 14 is sensitive, and processing it requires parental or guardian consent. Sensitive information also requires separate consent (Art. 29), as do cross-border transfers (Art. 39). | The PIPL took effect on November 1, 2021, and applies to organizations outside China that serve or analyze people in China. |
| European Union | GDPR (Art. 8); Digital Services Act | Under 16, or as low as 13 where a member state sets a lower age | Parental authorization is needed below the national digital consent age. The Digital Services Act bars profiling-based advertising to users known to be minors. | The GDPR has applied since 2018. In 2023, Ireland’s Data Protection Commission fined TikTok EUR 345 million over public-by-default settings, inadequate transparency, and dark patterns. |
| United Kingdom | UK GDPR; ICO Age Appropriate Design Code (the Children’s Code) | Under 18 | High privacy settings by default, limited data collection, and no manipulative design practices. | Enforcement between April 2024 and October 2025 affected more than three million child visitors. Dailymotion, Twitch, and Viber were required to implement private profiles by default. |
| India | Digital Personal Data Protection Act (DPDPA) 2023; DPDP Rules 2025 | Under 18 | Verifiable parental consent before processing a child’s data, and no tracking, behavioral monitoring, or targeted advertising directed at children. | The rules were finalized in November 2025. The consent manager rules apply from November 2026, and the remaining obligations from May 2027. |
| South Africa | Protection of Personal Information Act (POPIA), Sections 1 and 35 | Under 18 | Processing requires the consent of a “competent person” unless an exception applies. POPIA does not require verification, or that this person be a parent or guardian. | Effective July 1, 2020, with compliance required from July 2021. |
| South Korea | Personal Information Protection Act (amended 2020) | Under 14 | Consent from a parent or guardian to collect or use the data. Accepted verification methods include text message, smartphone authentication, and payment information. Privacy policies must use clear, easily understandable language. | In force following the 2020 amendments. |
Two patterns stand out. Age thresholds run from under 13 (COPPA) to under 18, so a global service cannot rely on COPPA’s line alone. Regulators are also moving from consent toward design: the UK Children’s Code, the EU Digital Services Act, Brazil’s ECA Digital, and Australia’s code all address how services are built.
United States
Protecting children’s privacy has emerged as one of the most active areas of U.S. state-level legislation. Across more than a dozen comprehensive state privacy laws now in effect, children’s personal data is treated as a sensitive category requiring heightened protection. Several states have gone considerably further than COPPA’s federal baseline.
California’s Age-Appropriate Design Code Act (CAADC), modeled on the UK’s equivalent framework, applies to businesses that provide an online service, product, or feature likely to be accessed by children, defined as consumers under 18. It requires, among other things, age estimation with reasonable certainty (or child-level protections for all users), high-privacy default settings, clear privacy information suited to children’s ages, and an obvious signal when a child is monitored or tracked.
Only the California Attorney General can enforce it, with civil penalties of up to USD 2,500 per affected child for each negligent violation and USD 7,500 per affected child for each intentional violation. After the Ninth Circuit’s March 12, 2026 ruling in NetChoice v. Bonta, those core requirements became enforceable in April 2026. The data protection impact assessment requirement, the data-use and dark-pattern restrictions, and the 90-day cure provision remain enjoined while the case continues.
Texas’s Securing Children Online Through Parental Empowerment (SCOPE) Act, which took partial effect in September 2024, requires parental consent for data collection from minors under 18 on covered social platforms, though several of its provisions remain subject to ongoing litigation. Maryland and Vermont have enacted similar age-appropriate design code legislation. Vermont’s takes effect on January 1, 2027.
The proliferation of state laws with differing age thresholds, consent standards, and enforcement mechanisms creates a complex compliance landscape for organizations operating nationally. COPPA sets a federal floor for children under 13, but the patchwork of state obligations now extends well beyond it.
Next Steps for COPPA Compliance
COPPA’s compliance date for the 2025 amendments has passed, and enforcement is active. The following steps can help support your obligations:
- Monitor the FTC’s age verification rulemaking and the progress of COPPA 2.0.
- Determine whether your service is directed to children or mixed audience, and document your reasoning.
- Audit the personal information you collect from children, including persistent identifiers and biometric data.
- Confirm that your consent flow supports separate parental consent for third-party disclosure.
- Put a written information security program and a written data retention policy in place.
