The Children's Online Privacy Protection Act (COPPA): A Compliance Guide for Operators
The Children’s Online Privacy Protection Act (COPPA) is a U.S. federal law that governs how websites, apps, and other online services collect, use, and disclose personal information from children under 13. The Federal Trade Commission (FTC) enforces it through the COPPA Rule (16 CFR Part 312). Operators must give clear notice, obtain verifiable parental consent before collecting a child’s personal information, give parents control over that data, keep it secure, and delete it when it is no longer reasonably necessary. The FTC finalized amendments to the Rule in 2025 that add separate parental consent for disclosures to third parties, a written information security program, a data retention policy, and expanded definitions of personal information. The compliance deadline for those amendments was April 22, 2026.
Organizations that collect data from children, or that may do so without realizing it, need to know which side of the line they are on. Kiteworks provides a control plane for secure data exchange that helps organizations protect children’s personal information with encryption, access control, and audit logging, and collect it through secure web forms.
This page provides general information, not legal advice. For guidance on how COPPA applies to your organization, consult your legal or privacy team.

Key Takeaways
1. COPPA Covers More Than Children’s Websites
A general audience service is covered if it has actual knowledge that it collects personal information from a child under 13. Operators of child-directed services are covered from the outset, and so are third parties such as ad networks and plug-ins that knowingly collect data through a child-directed service.
2. Consent Must Be Verifiable, Not Assumed
Operators must obtain verifiable parental consent before collecting, using, or disclosing a child’s personal information. The amended Rule requires separate consent for disclosures to third parties unless the disclosure is integral to the service.
3. Security and Retention Are Now Written Requirements
The amended Rule requires a written information security program and a data retention policy. Operators can no longer keep children’s data indefinitely, and they must show how it is protected.
4. Personal Information Is Defined Broadly
Persistent identifiers, photos, voice recordings, and geolocation all count, and the amendments add biometric identifiers. Cookies and device identifiers that track a child across services can trigger COPPA even without a name or email address.
5. Penalties Are Assessed Per Violation
Each violation can carry a civil penalty, and large cases have reached hundreds of millions of dollars. The FTC and state attorneys general both enforce COPPA.
What Is COPPA? Definition and Scope
Congress enacted COPPA in 1998 (15 U.S.C. 6501 to 6506), and the FTC’s implementing Rule took effect on April 21, 2000. The law applies to operators of commercial websites and online services, including mobile apps, connected toys, and other internet-connected products, that are:
- Directed to children under 13 and that collect personal information from them.
- General audience services that have actual knowledge they are collecting personal information from a child under 13.
- Mixed audience services that target children as one of several audiences. The amended Rule adds a standalone definition and lets these services age-screen users before collecting personal information, then apply COPPA protections to those who identify as under 13.
COPPA reaches foreign-based operators that direct services to children in the United States or knowingly collect their data. The FTC considers factors such as subject matter, visual content, animated characters, child-oriented activities, music, the age of models, advertising, and competent evidence of audience composition. The amended Rule adds marketing materials, representations to third parties, user reviews, and the age of users on similar services.
Who Is Protected Under COPPA?
COPPA protects children under 13. Once a user turns 13, COPPA no longer applies to their data, although other laws, including state privacy laws, may still require extra protection for teens. Operators generally cannot avoid the law by claiming no children use their service if their content, marketing, or user base suggests otherwise.
What Counts as Personal Information Under COPPA?
The Rule defines personal information broadly. It includes:
- A first and last name, a physical address, an email address or other online contact information, and a telephone number.
- A screen or user name that functions as online contact information.
- A persistent identifier that can recognize a user over time and across services, such as a cookie, an IP address, or a device identifier.
- A photo, video, or audio file that contains a child’s image or voice.
- Geolocation information precise enough to identify a street name and a city or town.
- Information about a child or parent that is collected and combined with one of these identifiers.
- Under the amendments, biometric identifiers such as fingerprints, voiceprints, facial templates, and gait patterns, along with government-issued identifiers beyond Social Security numbers, including passport numbers and birth certificates.
Our entry on PII and PHI explains how these categories relate to broader privacy terms.
What Does COPPA Require From Operators?
The Rule sets a core set of obligations:
- Post a clear online privacy notice that describes what information is collected from children, how it is used, and whether it is disclosed to third parties.
- Give direct notice to parents before collecting information from their child, including the purposes and the identity of any third parties that will receive it.
- Obtain verifiable parental consent before collecting, using, or disclosing a child’s personal information, subject to limited exceptions.
- Give parents control: the ability to review the information collected, direct its deletion, and refuse further collection.
- Limit collection to what is reasonably necessary for the child’s participation in an activity. Operators cannot require more data as a condition of participation.
- Protect confidentiality, security, and integrity of the data, and release it only to parties that can do the same.
- Retain data only as long as reasonably necessary for the purpose it was collected, and delete it securely afterward.
These duties echo principles in other privacy laws. See our guides to data minimization and the GDPR for comparison.
How Does Verifiable Parental Consent Work?
Verifiable parental consent means making reasonable efforts, considering available technology, to make sure the person giving consent is the child’s parent. The right method depends on how the data will be used. Accepted methods include a signed consent form, a credit card transaction that notifies the account holder, a toll-free call or video conference with trained personnel, and checking a government-issued ID. The amendments add three methods: knowledge-based authentication using difficult multiple-choice questions, submission of a government-issued photo ID, and a text message combined with a confirming step such as a follow-up text, letter, or call.
Operators that want to disclose children’s data to third parties for purposes not integral to the service must obtain a separate consent for that disclosure. Parents must be able to agree to collection and use without agreeing to third-party disclosure.
When Is Parental Consent Not Required?
The Rule allows narrow exceptions. In each case the operator may collect only what the exception needs, must not use it for other purposes, and must generally delete it afterward:
- Collecting a parent’s or child’s online contact information solely to obtain parental consent.
- Responding once to a child’s specific request, after which the contact information must be deleted.
- Responding more than once to a child’s request, such as a newsletter, with notice to the parent and a chance to opt out.
- Protecting a child’s safety.
- Protecting the security and integrity of the service, taking precautions against liability, responding to judicial process, or cooperating with law enforcement.
- Using a persistent identifier solely to support the internal operations of the service, without contacting the child.
- Under the amendments, collecting an audio file with a child’s voice solely to respond to a request and deleting it immediately afterward.
How Is COPPA Enforced?
The FTC enforces COPPA through investigations, civil penalty actions, and consent orders that often include data deletion, compliance programs, and long-term reporting. State attorneys general can also bring COPPA actions in federal court. Operators can join an FTC-approved safe harbor program, a self-regulatory program whose guidelines meet or exceed the Rule. Participation does not create immunity, but the FTC generally treats compliance with a safe harbor program’s guidelines as compliance with the Rule. The amended Rule requires approved programs to publicly disclose their member lists and to report to the FTC.
COPPA and Schools
Schools are not operators, but the vendors that serve them are. FTC guidance allows a school to authorize collection of student data on behalf of parents when the data is used only for the school’s educational purposes and not for commercial purposes. The FTC did not finalize its proposed education technology provisions in 2025 and deferred them pending possible changes related to the Family Educational Rights and Privacy Act (FERPA). Read our guide to FERPA compliance and FERPA best practices for the student records side.
COPPA, Social Media, and User-Generated Content
Features that let children post comments, photos, videos, or voice recordings can expose personal information publicly. Operators that allow this must obtain verifiable parental consent before collecting that information, or use reasonable measures to detect and delete personal information before it is posted. Services that rely on age gates should design them neutrally, without encouraging children to enter a false age.
How Does COPPA Relate to International Privacy Rules?
COPPA is one of several regimes that protect children’s data. The GDPR sets a default age of digital consent of 16, which member states may lower to 13. State laws such as the California Privacy Rights Act add opt-in requirements for selling the data of minors, and the United Kingdom has its own age-appropriate design requirements. Organizations that serve a global audience should compare obligations across regimes using our overview of global data privacy laws.
COPPA Compliance Checklist
- Determine whether your service is child-directed, mixed audience, or general audience with possible actual knowledge.
- Inventory the personal information you collect from children, including persistent identifiers, and every third party that receives it.
- Publish a clear, complete online privacy notice and prepare direct notices for parents.
- Choose a verifiable parental consent method that fits how you use the data.
- Obtain separate consent before disclosing children’s data to third parties for purposes that are not integral to the service.
- Give parents a simple way to review data, request deletion, and stop further collection.
- Limit collection to what each activity reasonably requires.
- Adopt a written information security program, name the accountable personnel, assess risks, and test safeguards at least annually.
- Set a data retention schedule and delete children’s data when it is no longer reasonably necessary.
- Keep records of notices, consents, vendor reviews, and deletion requests, and train staff who handle children’s data.
Current Status and Recent Developments
This section is reviewed and updated separately from the rest of the page. Last reviewed: October 2026.
Amended COPPA Rule. The FTC published its final amendments to the COPPA Rule in the Federal Register on April 22, 2025. The amendments took effect on June 23, 2025, and operators had until April 22, 2026 to comply, with different timelines for some safe harbor provisions. Operators are now expected to meet the new requirements.
Civil penalties. COPPA violations are treated as violations of an FTC rule, and the FTC can seek civil penalties per violation. The per-violation maximum is adjusted for inflation each year, and the figure listed in the FTC’s regulations at the time of this review was $53,088. The FTC has said it will continue to apply 2025 penalty levels for 2026.
Enforcement examples. Large cases show how penalties accumulate. In 2019, Google and YouTube agreed to pay $170 million to resolve FTC and New York Attorney General allegations of COPPA violations. In 2022, Epic Games agreed to pay $275 million in a COPPA settlement with the FTC.
How Kiteworks Helps Organizations Protect Children’s Data
Kiteworks provides a control plane for secure data exchange that governs how sensitive data moves between people, machines, and systems. For organizations that collect and share children’s personal information, the platform helps support COPPA security and accountability requirements:
- Secure collection. Secure web forms let organizations collect consent and other information with customizable notices.
- Encryption. Data is protected with double encryption, using separate keys at the file and disk levels, and customers own their encryption keys. Learn more about double encryption and email encryption.
- Least-privilege access. Granular permissions limit who can view, download, or share personal information, which helps limit exposure to the people who need it.
- Audit logging. A single audit log records user, data, and system activity, giving organizations evidence of how children’s data was accessed and shared. See our guide to the audit log.
Explore Kiteworks for COPPA compliance, learn about secure file sharing, or see the Kiteworks data control plane.
See how Kiteworks helps you protect children’s personal information in every exchange. Schedule a demo

