Appnext and the GDPR

On May 25th, 2018, the new EU data protection regulatory framework – the General Data Protection Regulation ("GDPR") – will come into effect.

Appnext takes considerable efforts to ensure that its privacy practices comply with data protection laws and the industry's best practices.

For publishers who are implementing CMP ("Consent Management Platform") - It is possible to forward the end-user consent status to Appnext SDK - see below.

For publishers who don't implement CMP or are not require consent from their end-users, Appnext is GDPR compliant under the "Legitimate Interest" legal basis; On this case, the publisher is required to provide a transparency to the end-user indicating that Appnext SDK is in use.

🚧
Please Note!
The text in this page is provided for guidance and educational purposes only. The responsibilities and liabilities of Appnext to its partners and customers are controlled by Appnext agreements. For more information, contact your success manager/Appnext support.

Working with Appnext SDK directly

It is possible to forward the consent status to Appnext SDK on each time the SDK is initialized using a dedicated setParam function;

The consent boolean value (in string format) should be passed on each SDK session.

Example:

Appnext.init(context);
// The publisher should check the consent status on each SDK session;
if (...) {
  //Positive consent is provided by the end-user
 Appnext.setParam("consent", "true");
} else {
  //Negative consent is provided by the end-user
 Appnext.setParam("consent", "false");
}

Working with Mopub SDK

Appnext is not an official Mopub partner. This means that you will have to forward the negative consent to Appnext manually;

Mopub's MoPub.canCollectPersonalInformation() can provide the boolean status of the end-user's consent

Example:

//Initilize the Appnext SDK
Appnext.init(context);

//Forward the end-user consent from the MoPub SDK;
PersonalInfoManager personalInfoManager = MoPub.getPersonalInformationManager();
if (personalInfoManager != null && personalInfoManager.gdprApplies()) {
 boolean userProvidedConsent = personalInfoManager.canCollectPersonalInformation();
 Appnext.setParam("consent", String.valueOf(userProvidedConsent));
}

Please refer to Mopub's website for more information about working with Mopub's consent CMP

Working with Google Consent SDK

Google will introduce its own consent SDK (CMP) by the end of May 2018. Once the SDK will be released, Appnext will publish integration instructions on how to pass a negative consent to its Android SDK.

Working with the IAB consent framework

IAB Europe is in the process of releasing a unified framework for getting the end-users consent when working with in-apps. The framework is still in draft status, pending final requirements. Appnext is constantly monitoring the framework maturity level. Once the IAB will get the framework to a final status Appnext will implement it on its SDK.

Support & Integration

Should you have any problems integrating the product, log a ticket with us by emailing [email protected].