Feature

Age Assurance & COPPA

Profile-aware kids' privacy. Pass a known age and Cookie Panda blocks advertising and analytics for under-13s automatically — or show a built-in age gate when you don't know.

Kids' privacy that fits how your product already works.

COPPA in the US and the UK/EU children's codes demand that you don't run advertising or analytics on under-age users — but bolting a clumsy age wall onto every screen hurts everyone. Cookie Panda takes a profile-aware approach: if your product already knows the user's age — a streaming kids' profile, a logged-in birth date — you simply pass it (knownAge, or child: true) and the SDK applies the right outcome with no extra screen. Under the threshold, advertising and analytics are blocked automatically and the consent record is locked to essential-only, with the GPP "known child" flag set so the signal carries downstream.

When you don't know the age, the built-in self-declared age gate handles it on the web: a clean, on-brand prompt that blocks under-13s and can require a parental-confirmation step for teens. Either way you get the same compliant result without building consent logic yourself.

And it's everywhere your audience is. The auto-flag ships on web, iOS, tvOS, Android, Flutter and Roku, and on a profile switch you call setAge() (or change the prop) to re-apply the outcome live — so flipping from an adult profile to a kids' profile instantly turns advertising off, no reload required.

What's included

  • Pass a known age — no gate (profile-aware)

  • Built-in self-declared age gate fallback

  • Auto-blocks ads & analytics for children

  • Web, iOS, tvOS, Android, Flutter & Roku

How it works

Age Assurance & COPPA in four steps

  1. 1

    Tell us the age (if you know it)

    Pass knownAge or child: true at init — typically from the active profile or account.

  2. 2

    Or let the gate ask

    No age signal? The web age gate prompts the visitor and blocks under-13s, with an optional parental step for teens.

  3. 3

    Children are auto-protected

    Under the threshold, ads and analytics are blocked, consent is essential-only, and the GPP child flag is set.

  4. 4

    Re-apply on profile switch

    Call setAge() (or change the prop) when the user switches profiles — the outcome updates instantly.

Common questions

Do my users always see an age gate?

No. If your app already knows the age (e.g. a kids' profile), you pass it and no gate is shown. The self-declared gate is only the fallback for when the age is unknown.

Which platforms support it?

The known-age auto-pass works on web, iOS, tvOS, Android, Flutter and Roku. The self-declared gate UI is currently on the web.

Is this full COPPA compliance on its own?

It enforces the core requirement — no ads/analytics for under-age users plus the child signal. Ad-supported services aimed at children that need verified parental identity should also connect a parental-verification vendor.

More features

  • Consent Banner Designer — Design a fully on-brand consent experience with four layouts, live preview, and per-locale copy — no code required.

  • Automated Cookie Scanner — A headless Chromium crawler discovers every cookie, tracker and third-party vendor on your site and keeps your policy in sync.

  • Prior Cookie Blocking — Stop trackers before consent. Cookie Panda rewrites and gates tag-loading scripts until the user makes a choice.

Get compliant today. Stay compliant for good.

Join the teams using Cookie Panda to turn privacy compliance from a liability into a signal of trust. Free to start — no credit card required.