Children
TapMind trust and compliance information for publishers' engineers.
Children, Families & age signals
TapMind's rule. We do not knowingly process the personal data of anyone under 18 for targeted advertising. In apps that are directed at children, enrolled in Google Play's Families program or Apple's Kids category, or flagged as child-directed — and for any individual request flagged as relating to a child — TapMind uses no advertising identifier, sends a minimal device description, forwards the child flag to partners, and serves contextual ads only. No exceptions, and no consent unlocks identifier features for these apps.
What the SDK reads. Google Mobile Ads' age-restricted treatment (and the older child-directed and under-age-of-consent flags on older GMA versions) on every request, and your setAgeRestrictedUser(true) call. Either suppresses the advertising identifier for the session.
What you declare. In your attestation with TapMind: whether the app is directed at children, is in Families or Kids, or is likely to be used by a significant number of people under 18. Keep it current; TapMind may apply the child rule on its own if store signals indicate otherwise.
Age thresholds. Different countries set different ages (for example 18 in India, 13 or 16 in US states, 13–16 in the EEA, 14 in Quebec). You only signal; TapMind applies the country's threshold server-side.
Google Play Families self-certification. TapMind's SDKs are not yet self-certified for Google Play's Families program. Until they are listed as self-certified, do not include the TapMind SDK in apps enrolled in the Families program or in Apple's Kids category. We will update this line when certification is granted.