Last July, we announced Advertising policy changes to help bolster security and privacy. We added new restrictions on identifiers used by apps that target children.
When users choose to delete their advertising ID in order to opt-out of personalization advertising, developers will receive a string of zeros instead of the identifier if they attempt to access the identifier. This behavior will extend to phones, tablets, and Android TV starting April 1, 2022.
We also announced that you need to declare AD_ID permission when you update your app targeting API level to 31 (Android 12). Today, we are sharing that we will give developers more time to ease the transition. We will require this permission declaration when your apps are able to target Android 13 instead of starting with Android 12.
Action Items :
If you use an advertising ID, you must declare the AD_ID Permission when your app targets Android 13 or above. Apps that don’t declare the permission will get a string of zeros. Note: You’ll be able to target Android 13 later this year.
If your app uses an SDK that has declared the Ad ID permission, it will acquire the permission declaration through the manifest merge.
If your app’s target audience includes children, you must not transmit Android Advertising ID (AAID) from children or users of unknown age.
New mail from google play about “Update on ad ID usage for apps that target children”
Last July, we announced Families policy changes to help bolster security and privacy. We added new restrictions on identifiers used by apps that target children. The changes related to Android Advertising ID (AAID) are required by 1 April, so we encourage you to review your apps in case you need to make updates.
We also announced an AD_ID permission that could be used to aid compliance when you update your app’s target API level to 31 (Android 12). Ad ID would have been disabled when you targeted Android 12 and did not include the new AD_ID permission. Now, we’re giving developers more time to adjust and will start this behaviour with Android 13, instead of Android 12.
This means that apps with target API level 31 (Android 12) can still access the ad ID without this permission. When you update your apps to target Android 13 and you don’t include this permission declaration, ad ID will be disabled.
Due to this update, you may receive warnings starting in April to change your compliance method. If you need more time to target Android 13, you may be able to get an extension to this Families update by following the instructions in the warning notification. When you’re able to target Android 13, we will require this permission declaration.
If your app’s target audience is children only, you must not transmit Android Advertising ID (AAID) from children or users of unknown age.
If your app targets both children and adults, ensure that any SDKs used that may collect AAID provides you with the ability to disable transmission when the user is a child or of unknown age.
As always, we appreciate your partnership in building a safer and more robust Families ecosystem on Google Play.
i think you are not targeting children in your app because you are using kodular platform which put their ad inside your app, and it is not allowed to target children due to google policy. so, do not warry about the mail…
currently Kodular targets SDK 30, which is Android 11…
in other words: currently there is nothing to do…
You must complete the advertising ID declaration before releasing an app that targets Android 13
Jul 26, 2022 20:13
The advertising ID declaration form is now available for you to complete.
We’ll use this declaration to provide safeguards in Play Console. You will not be able to create releases targeting Android 13 until you complete the declaration.
Apps using advertising ID that target API level 33 (Android 13) or later must declare the normal permission com.google.android.gms.permission.AD_ID in their AndroidManifest.xml . This will prevent your advertising identifier from zeroing out. If you do not declare the permission in your manifest file, or if you use an SDK that omits the permission from their library manifest, this may impact your advertising and analytics use cases.
@Kodular Please advise action to be taken on the above email received.
