Does COPPA apply to you?
Your service is directed at children under 13, or you have actual knowledge that you collect personal information from them. Persistent identifiers — a cookie, a device ID, an advertising identifier — count as personal information under COPPA, so analytics alone can put a kids' site in scope.
- ✓Who it covers: children under 13 in the United States.
- ✓In force since 21 April 2000, with the amended FTC Rule from 22 June 2025.
- ✓Exposure if you ignore it: Up to $53,088 per violation, enforced by the FTC and by state attorneys general.
What COPPA asks a product to do
Four obligations carry most of the weight for a digital product. They are what the clause set below is written against, and what the scan is looking for evidence of.
- ✓Get verifiable parental consent before collecting anything from a child under 13, including a persistent identifier used for advertising.
- ✓Publish a direct notice to parents describing what you collect, how you use it and how they can review or delete it.
- ✓Delete children's data when it is no longer needed for the purpose it was collected for — the amended Rule requires a written retention policy saying so.
- ✓Do not condition a child's participation in a game or activity on giving up more information than is reasonably necessary for it.
What Poliogo puts in your documents
Poliogo carries a clause set written against COPPA specifically. Every heading in the list below is a section the generator really writes, drawn from a library built from published regulatory text. Your stack is identified by pattern matching, not by a model, and the COPPA sections are appended from the library whether or not any AI is reachable. An AI model is used for one thing: drafting extra clauses from operational notes you type yourself.
- ✓Children Under 13 And Parental Consent — appended automatically when your stack and jurisdiction call for it.
- ✓Notice At Collection For California Residents — appended automatically when your stack and jurisdiction call for it.
- ✓Global Retention Baseline — appended automatically when your stack and jurisdiction call for it.
- ✓Security Safeguards And Breach Notification — appended automatically when your stack and jurisdiction call for it.
Why a generated COPPA policy beats a template
A template describes a product someone imagined. This one describes yours, and notices when yours changes.
Written from evidence, not recall
No SDKManifests first, then a vendor-endpoint sweep over the source. A raw fetch to a payment or model API with no SDK installed — the normal shape of AI-generated code — is still detected.
The statutory sections are fixed text
The COPPA sections come from a pre-drafted library and are appended from it, not written by a model. Your stack is identified by pattern matching, so a model outage cannot remove a mandatory section. An AI model drafts only the extra clauses you ask for from your own operational notes.
You can explain every paragraph
Beside each clause sits a plain-English note: what it means, and which detected service made it necessary. You will not publish a sentence you could not defend to a customer.
It stays true after launch
DriftEach scan is diffed against the snapshot your documents were generated from. Adding a tracker on a Tuesday produces a pull request, not a quiet inaccuracy discovered during an audit.
The law moves too
A curated bulletin written against the statutes, filtered to the changes your own stack makes relevant — not a news feed. Included from Starter.
One product, several regimes
Most products serve more than one jurisdiction. The regional clause sets stack rather than compete, so a policy can satisfy the GDPR, CCPA and Israeli law at once without three documents.
How it works
A Git repository, a hosting account, or the repository your no-code builder syncs to. Source is read in flight rather than stored, and nothing in it changes except through a pull request you approve.
Every service your code calls, in plain English, with the evidence for each. This is what decides which COPPA disclosures your documents need — a product with no advertising pixel should not carry an advertising disclosure.
Privacy policy, cookie policy and — from Starter — terms of service, with the COPPA sections appended from the clause library. Those sections are fixed text, not written by a model.
Re-scan whenever you like on any plan, or let a paid plan watch in the background. A stack change becomes a pull request with a plain-English diff, and merging it is the approval.
Questions people ask
Does COPPA apply to me?
Your service is directed at children under 13, or you have actual knowledge that you collect personal information from them. Persistent identifiers — a cookie, a device ID, an advertising identifier — count as personal information under COPPA, so analytics alone can put a kids' site in scope. If you are unsure, the honest answer is that most products serving children under 13 in the United States are in scope, and the cost of assuming otherwise is up to $53,088 per violation, enforced by the ftc and by state attorneys general.
What does Poliogo actually write for COPPA?
Poliogo carries a clause set written against COPPA specifically. Every heading in the list below is a section the generator really writes, drawn from a library built from published regulatory text. Your stack is identified by pattern matching, not by a model, and the COPPA sections are appended from the library whether or not any AI is reachable. An AI model is used for one thing: drafting extra clauses from operational notes you type yourself.
Is a generated policy good enough, or do I need a lawyer?
For routine day-to-day compliance — a privacy policy that matches your product, a working consent banner, and keeping both current as the product changes — this does the heavy lifting from clause logic built from published regulatory text. It does not replace counsel for a regulatory dispute, a corporate transaction or anything unusual about your situation. Poliogo is a compliance management technology platform, not a law firm, and this page is not legal advice.
How does it know what my product does with data?
It reads the project. Dependency manifests first, then a sweep of the source for known vendor endpoints — the URLs your fetch, axios and httpx calls address — so a raw HTTP call to a payment or model API is detected even with no SDK installed. Environment variable names are read as evidence; their values never are.
What happens when the law changes?
Regulation monitoring is a curated bulletin written against the statutes themselves, not a news crawler, and it is filtered to the changes your own stack makes relevant. It is included from Starter. When a change affects you, the update arrives with a plain-English explanation of what it asks for.
Can I see the COPPA sections before I commit to anything?
Yes. Connect a project on the Free plan, run the scan and generate the documents — the full text, with the plain-English explanation beside every clause saying what it means and which detected service made it necessary. Nothing is published until you approve it, and no card is asked for.
Generate your COPPA documents
Connect a project and see the detected stack in under 60 seconds. Free plan, no credit card, and nothing is published until you approve it. Poliogo is a compliance management technology platform, not a law firm, and this page is not legal advice.
Start free — no credit cardPoliogo is an automated code analysis and document display tool, not a law firm. Poliogo does not provide legal advice, representation, or guarantees of statutory compliance, ADA/WCAG certification, or legal immunity. Visual banners and generated documents are advisory tools and do not substitute for professional legal review.