Consent request clearly describes what data is collected and how it is used

COPPA §312.4 and §312.5 require that the direct notice to parents describe what personal information will be collected and how it will be used — vague notices like 'I agree to the Terms of Service' do not satisfy this requirement. The consent must be informed: a parent who clicks 'approve' without knowing that the app collects usage events linked to their child's account, or that the display name is visible to other users, has not meaningfully consented to those specific practices. Disclosures that don't match actual collection also violate GDPR Article 13 for EU children, compounding exposure. The FTC has cited inadequate disclosure in consent notices as an independent ground for enforcement.

Rewrite the parental consent notice to enumerate each category of data collected, how it is used, whether it is shared, and what is visible to other users. Use plain language — not legal boilerplate.

Subject: [App Name] — Please review and approve your child's account

WHAT WE COLLECT FROM CHILDREN
- A display name (chosen by the child — not their real name)
- The child's email address (account communication only)
- Usage data within the app (not linked to real-world identity, not shared with advertisers)

HOW WE USE THIS INFORMATION
- To operate the account and provide the service
- We do NOT use children's data for behavioral advertising
- We do NOT share children's personal information with third parties for their own use

WHAT IS VISIBLE TO OTHERS
- The child's display name is visible to other users
- No other information is publicly visible

YOUR RIGHTS AS A PARENT
You may review, correct, or delete your child's data at any time
by contacting privacy@example.com.

Update the notice whenever you add a new data collection point to child sessions — stale consent disclosure is a §312.4 violation in its own right.