COPPA 2026 Notice Lint

It reads a children's privacy notice - PRIVACY.md, a docs page, or a served HTML file - and checks it against 18 clauses of the amended COPPA Rule that became fully enforceable on 22 April 2026. Each finding names the line and the section of 16 CFR Part 312 behind it, so you edit the sentence rather than rewrite the document.

Developers and solo publishers who ship apps, games or edtech to children under 13 in the United States and keep the privacy notice in the repository. It is written for the person who has no privacy counsel on retainer and who is the one who will be asked, by an app store reviewer or by a school district, to prove the notice is current.

Both were trained on notices written before the 2025 amendments. They produce the 2013 shape: a retention sentence with no timeframe, no separate consent for third-party disclosure, no list of operators, and often the GDPR threshold of 16 rather than COPPA's 13. On the sample notice shipped here that pattern returns 16 findings.

Checking the notice open in your editor against all 18 clauses is free, with no key and no account, as is the same check in the browser. The paid part is a different job: sweeping every notice, translation and doc page in the workspace and writing a dated report file you keep. That is $29 once, one key per person or CI seat, 7-day full refund.

Outside privacy counsel reviewing one children's notice against the amended Rule bills roughly 6 to 10 hours at $350 to $550 an hour. The lint does not replace that review; it removes the mechanical gaps first, so the hours that are billed are spent on judgement rather than on finding a missing retention timeframe.