F. Requesting Consent

Requesting Consent from European Users

Under the Google EU User Consent Policy, you must make certain disclosures to your users in the European Economic Area (EEA) and obtain their consent to use cookies or other local storage, where legally required, and to use personal data (such as AdID) to serve ads. This policy reflects the requirements of the EU ePrivacy Directive and the General Data Protection Regulation (GDPR).

Ads served by Google can be categorized as personalized or non-personalized, both requiring consent from users in the EEA. By default, ad requests to Google serve personalized ads, with ad selection based on the user's previously collected data. Google also supports configuring ad requests to serve non-personalized ads. Learn more about personalized and non-personalized ads.

To support publishers in meeting their duties under this policy, Google offers a Consent SDK. But the SDK is not yet available. we, are keeping an eye on that and as soon as that SDK is released, we will make it available as an ANE to all AIR developers.

However, To make sure your apps comply with the GDPR, you really don't need a Consent SDK. All you have to do is to open up a privacy page for your users and present your app's privacy to them. As far as the Admob SDK is concerned, you can decide if Admob can use personalized ads or not based on users consent.

The default behavior of the Google Mobile Ads SDK is to serve personalized ads. If a user has consented to receive only non-personalized ads, you can configure an AdRequest object with the following code to specify that only non-personalized ads should be returned:

var adRequest:AdRequest = new AdRequest();
adRequest.extras = {npa:1}; // npa stands for "Non-Personalized Ads"
AdMob.api.banner.loadAd(adRequest);

For more information about this, visit the official Google docs here.