I read a lot of privacy policies on kids’ sites and apps, and the same mistakes come up again and again. Some are cosmetic. Others are the kind of thing that ends up in an FTC complaint. With the compliance deadline for the amended COPPA Rule behind us since April 22, 2026, a few of them are now clearer problems than they used to be.
A quick refresher first. COPPA requires two different notices: an online notice, which is your privacy policy, and a direct notice to parents when you ask for their consent. This post is about the online notice. Under the Rule it has to be clearly and understandably written, complete, and free of unrelated, confusing or contradictory material. Here’s where policies most often fall short.
1. Copying a general-audience template
“We do not knowingly collect personal information from children under 13.” That line belongs on a general-audience site, if anywhere. On a site built for kids it’s either untrue or a sign that nobody read the policy before publishing it. Start from what your service actually does, not from someone else’s policy.
2. Not naming every operator
The notice has to list the name, address, phone number and email address of every operator collecting or maintaining children’s personal information through your site or service. You can designate one operator to handle parents’ questions, but all of them still have to be named. Ad networks, analytics tools and plug-ins that collect personal information through a child-directed site can be operators too, and the site is responsible for them. If you don’t know which third parties collect data through your app, find out before you write a word.
3. Vague sharing language
“We may share information with trusted partners” tells a parent nothing. Your notice has to describe your disclosure practices, and under the amended Rule that includes the identities or specific categories of the third parties you disclose children’s information to, and the purposes. If you disclose for reasons that aren’t integral to your service, you also need separate parental consent for that disclosure, which I explained in Verifiable parental consent: accepted methods.
4. No data retention policy
This one is new, and it’s widely missed. The amended Rule requires a written data retention policy that states why you collect children’s personal information, why you need to keep it and when you’ll delete it, and that policy has to appear in your online notice. The Rule also says children’s personal information may not be retained indefinitely, so “we keep data as long as necessary” with no timeframe doesn’t do the job.
5. Saying nothing about persistent identifiers
Lots of kids’ apps rely on the exception that lets them collect persistent identifiers, such as cookies or device IDs, without consent, solely to support internal operations. Under the amended Rule, if you rely on it, your notice has to say which internal operations you collect them for and how you make sure they aren’t used to contact a specific person, build a profile or serve behavioral ads. Silence isn’t an option anymore.
6. Leaving out parents’ rights
Parents can review the personal information you’ve collected from their child, have it deleted and refuse to let you collect or use any more. The notice has to say so and explain how. A generic “contact us with questions” isn’t a procedure.
7. Burying the link
The Rule calls for a prominent, clearly labeled link to the notice on the home or landing page or screen, and at each area where you collect personal information from children, close to the request. A grey footer link in tiny type at the bottom of a long page isn’t prominent. In an app, think about the landing screen and every sign-up or profile screen, not just a settings menu.
8. Treating the policy as the direct notice
A privacy policy doesn’t replace the direct notice to parents. When you collect a parent’s contact information to ask for consent, you have to send them a notice that covers specific points, including what you’ll collect, how you’ll use it, how to give consent, and that you’ll delete their contact information if they don’t respond within a reasonable time. It also has to link to your online notice. The FTC’s case against i-Dressup, which I posted about in 2019, alleged problems with both notices.
9. Ignoring the new categories
The amended Rule added biometric identifiers, such as fingerprints, voiceprints and faceprints, and government-issued identifiers to the definition of personal information. If your product uses voice features, face filters or ID checks, your policy needs to account for them. If you rely on the exception for audio files of a child’s voice, the notice has to describe how you use them and say that you delete them immediately after responding to the child’s request.
10. A policy that doesn’t match reality
The most expensive mistake is a policy that says one thing while the product does another. Claims that data is deleted, encrypted or never shared have to be true. When practices change, the policy has to change with them, and a material change to how you collect, use or disclose children’s information can require fresh parental consent.
A quick self-check
- Could a parent read your policy in a few minutes and know what you collect, why, who gets it and how long you keep it?
- Does it name every operator collecting data through your service?
- Does it include your retention policy and, where relevant, your internal operations and audio file practices?
- Is the link easy to find everywhere you collect information from kids?
- When did someone last compare it against what the product actually does?
My take
Most of these mistakes aren’t malicious. They come from treating the privacy policy as boilerplate that legal signs off on once and nobody reads again. COPPA asks for the opposite: a document a parent can actually use. If teens use your service too, check that your policy describes their data accurately as well; see Teens over 13: does COPPA still apply? The FTC’s own guidance is linked from the Links page.
This is commentary, not legal advice. A privacy notice has to fit your actual practices, so have a lawyer who works on children’s privacy review yours.