Singular offers special versions of the Singular SDK for apps directed at underage users. These versions of the SDK support Singular attribution while complying with the restrictions placed by the Apple App Store and Google Play Store on apps for children.
Integrating the Kids Apps SDK instead of the regular SDK for your platform is a good way to ensure that your app doesn't collect device identifiers that are considered personally identifiable information and that are forbidden by the Apple App Store and Google Play for use in children's apps.
Singular offers Kids Apps SDKs for iOS, Android, and Unity.
FAQ
Apps for children are listed in the Kids Category in the App Store, and have special restrictions placed on them in order to protect the security and privacy of children online.
Regarding MMPs such as Singular, the guidelines say:
"In limited cases, third-party analytics may be permitted provided that the services do not collect or transmit the IDFA or any identifiable information about children (such as name, date of birth, email address), their location, or their devices." (App Store Review Guidelines)
In terms of using Singular in your app, this means that Singular can't collect the IDFA from the device.
According to the Google Play Policy Center, apps that target children must comply with the Google Play Families Policy. Regarding data collection, the policy says:
You must not transmit Android advertising identifier (AAID), SIM Serial, Build Serial, BSSID, MAC, SSID, IMEI, and/or IMSI from children or users of unknown age.
In terms of using Singular in your app, this means that Singular can't collect the GAID (AAID) from the device.
The Kids Apps SDK enables your app to pass the Kids Apps review required by the Apple App Store and the Google Play Store.
For iOS apps: If you use the Kids Apps SDK, you can be assured that Singular will not collect the IDFA from the end-user's device.
For Android apps: The Kids Apps SDK will not collect the GAID (AAID) from the end-user's device.
Notes
- Self-attributed networks (SANs) such as Google and Facebook require the IDFA/GAID in order to process requests from Singular or any other MMP. If your app uses the Kids Apps SDK, you will not get SAN attribution for that app based on IDFA/GAID (SKAN and Referrer-based measurement would still be available).
- In apps distributed outside of the Google Play Store, Singular supports identifiers such as OAID (On Huawei devices) and AMID (on Amazon devices). Check with your legal team to make sure that your app is compliant with any applicable privacy regulations.
Self-attributed networks (SANs) such as Google and Facebook require the GAID/IDFA in order to process attribution requests from Singular or any other MMP. If your app uses the Kids Apps SDK, you will not get SAN attribution for that app based on the device ID.
The Android SDK uses the InstallReferrer decryption method. The iOS SDK uses SKAdNetwork.
The SDKs support SKAdNetwork.
| 1 |
Download the relevant SDK: |
| 2 |
To integrate the SDK follow the instructions in the relevant implementation guide. For iOS:
For Android:
For Unity: Follow the Unity SDK implementation guide. |
The USA's COPPA (Children’s Online Privacy Protection Act) and the European Union's GDPR Kids (General Data Protection Regulation for Kids) each have specific requirements for preserving children's privacy and security online. These may differ from the standards used by Apple and Google in their app stores. Using the Kids Apps SDKs doesn't necessarily ensure compliance with COPPA/GDPR, and it's possible to use Singular's general SDKs and still comply with COPPA/GDPR.
If you are looking to build a COPPA/GDPR-compliant app, you can reach out to your Singular Customer Success Manager or Singular Support for guidelines.
