GDPR

The General Data Protection Regulation (GDPR) requires you to scope your user's consent. A user falls within the GDPR scope for your app when one more of the following applies:

• The user is currently located in the European Union (EU).

• The user registers with the app as an EU resident.

• The app specifically targets EU users.

For more information about how DT applies GDPR, see GDPR.

DT recommends that the first time you gather a user's consent, pass it to the DT FairBid SDK before initializing it. The SDK considers the user's consent when initializing. For future sessions, call the API if the user updates their consent, as the SDK caches the consent.

If you do not pass the user's consent to the DT FairBid SDK, the SDK only shows contextual ads to that user, which might negatively reduce your revenue.

User Consent Given

To indicate that the user gives consent, use the following API:

Android

Java

UserInfo.setGdprConsent(true, context);
      // true or YES if you have the user’s consent

iOS

Unity

User Consent NOT Given

To indicate that the user does not give consent, use the following API:

Android

Java

UserInfo.setGdprConsent(false, context);
      // false or NOT if you do not have the user’s consent

iOS

Unity

[Optional] Additional User Consent String

To pass an optional consent string, use the following API:

Android

Java

String consentString = "BOEFEAyOEFEAyXXXXXXI4AAAB9vABAASA";
UserInfo.setGdprConsentString(consentString, this);

iOS

Unity