Documentation

Support

Children and Child-Directed Apps

Guidance on children and child-directed apps for LevelPlay legal compliance.
Read time 1 minuteLast updated 3 hours ago

Children and child-directed apps

In this article, we explain how mobile apps can apply settings applicable to children and child-directed apps, as required by the US Children’s Online Privacy Protection Act (COPPA), the EU General Data Protection Regulation (GDPR), and Google Play’s “Designed For Families” program.

Publisher Responsibilities

  • Evaluate your apps and determine if they are child-directed
  • Correctly flag your apps as child-directed on your ironSource dashboard
  • Set the COPPA SDK Functionality as explained below
  • Ensure your apps comply with applicable laws
For more on COPPA obligations, see the FTC’s Children’s Privacy page.

How to flag apps as not directed to children

If your app is not directed to children (COPPA), choose the “not directed to children” flag in the dashboard. You can still use COPPA SDK Functionality to flag specific devices for compliance.
not COPPA

How to flag an app as child-directed

If your app is primarily directed to children, flag it as “Primarily Directed to Children” in the dashboard. This applies to all end-users and only affects ironSource’s own ad network. For mediation, check that additional networks are configured correctly.
COPPA
Apps in the Google Play Designed for Families program or Apple App Store’s Kids Category must be flagged as child-directed and follow ironSource Designed for Family SDK instructions.

How to flag a specific end-user as a child

For mixed-audience apps or those with age gates, flag the app as “Mixed Audience” and use COPPA SDK Functionality to flag specific end-users as children (below age 13, 16, or as required).
mixed audience
Read more about end-user flagging:

Complying with Google Play’s Designed for Families program

Apps in this program must be flagged as child-directed. Configure additional settings for child-directed apps:

ironSource collection and use of data from a child-directed app

  • Data collected (advertising ID, IP address) is used only for contextual ads, frequency capping, fraud prevention, and internal operations as permitted by COPPA and other laws.
  • No sharing of persistent identifiers with third-party bidders except as directed by the publisher for internal operations.
  • No survey ads or campaigns that prompt end-users to disclose personal information.

ironSource Mediation and child-directed apps

ironSource SDK offers a client-side API to flag specific end-users as children. Mediated apps must use the API to communicate child status to supported networks. For networks not listed, contact them directly. Supported networks and flags:

Network

iOS Adapter

Android Adapter

Unity Adapter

Flag

ironSource7.1.07.1.0.17.1.0.1is_child_directed
AdMob4.3.114.3.94.3.12AdMob_TFCD, AdMob_TFUA
AppLovin4.3.154.3.154.3.18AppLovin_AgeRestrictedUser
InMobi4.3.144.3.144.3.18inMobi_AgeRestricted
Mintegral4.3.124.3.124.3.12Mintegral_COPPA
Pangle4.1.54.1.24.1.7Pangle_COPPA
Tapjoy4.1.194.1.204.1.24Tapjoy_coppa
UnityAds4.3.154.3.164.3.19UnityAds_coppa
Vungle4.3.154.3.24Vungle_coppa
Yahoo4.3.04.3.04.3.0Yahoo_coppa

App developers under the age of 13

ironSource’s terms prohibit app developers under age 13 from using their services.
For more information, see: