Data practices in Families apps

Apps should not transmit the following from children or users of unknown age: 

  • Android Advertising ID (AAID)
  • SIM Serial
  • Build Serial
  • BSSID
  • MAC
  • SSID
  • IMEI
  • IMSI 

This means that apps that solely target children should never transmit these identifiers. Apps that target children and older age groups may only transmit these identifiers from users that they know are adults. 

Transmit means to send data through the network to any off-device destination, including the developer’s own server as well as destinations not controlled by the developer. In addition, apps targeting children should not request the device phone number from the TelephonyManager API.

For analytics, developers are encouraged to use app set ID.

How to comply with Families data practices for SIM Serial, Build Serial, BSSID, MAC, SSID, IMEI, IMSI, and phone number

To comply with Families data practices for SIM Serial, Build Serial, BSSID, MAC, SSID, IMEI, IMSI, and phone number, all apps:

  • Can have a target API Level of at least 29 (Android 10) to help prevent these identifiers from being transmitted by your app.
  • Should not transmit these identifiers from children or users of unknown age, or use SDKs that transmit these identifiers from children or users of unknown age.
  • Should not request or collect the phone number from the TelephonyManager API.

How to comply with Families data practices for Android Advertising ID (AAID)

Apps that target children

Apps that solely target children can comply with Families data practices for AAID by:

  • Ensuring your app code and SDK calls are configured correctly such as to not transmit AAID. This may require doing one or more of the following:
    • Modifying the SDK configuration settings inside your code or your app config file.
    • Modifying individual calls to the SDK, such as including a tag in an ad request that indicates the user is under the age of consent.
    • Updating global app settings on the SDK website or configuration portal. For example, turning on a global child-directed setting on the SDK configuration portal. 
    • It is possible that certain SDKs may not have the ability to function without transmitting AAID. In this case, you must remove these SDKs from your app. 

As a reminder, apps that solely target children must only use SDKs that have self-certified their compliance with Google Play’s Families Ads Program requirements to show ads and should only use SDKs which are approved for use in child-directed services. 

Apps that target children and adults

To comply with Families data practices for AAID, apps that target children and adults:

  • Must make sure that AAID is transmitted only when it's known that the user is not a child:
    • Ensure that, by default, app code and SDKs do not transmit AAID.
    • Only after determining that the user is not a child, adjust code, SDK settings, and SDK calls such that AAID may be transmitted. For example, once you have determined that the user is an adult, you may remove a tag from an ad request that indicates the user is under the age of consent. 

As a reminder:

Was this helpful?
How can we improve it?

Need more help?

Sign in for additional support options to quickly solve your issue

Search
Clear search
Close search
Google apps
Main menu
Search Help Center
true
92637
false