GDPR TCF Compliance - pubnative/pubnative-hybid-android-sdk GitHub Wiki

Publishing Partner Responsibilities

As a publisher, you are expected to manage the GDPR consent for your users as necessary. You are responsible for presenting the consent solicitation/dialog to the users and capture and save their consent preference. Per IAB standards you are also expected to save the user's preference, in a standard format published by iAB GDPR Storage Format, in "shared" storage for the App on user's mobile device from where our SDK will access it.

3rd party CMP support

The HyBid SDK complies with the IAB standard for TCF 2.0 implementation. This means that if the app uses any 3rd party CMP that writes the consent string to the defined location in the shared preferences, the HyBid SDK will read it from there and use it to determine the consent preference for the user.

If your app uses this type of integration, you don't need to do anything else to set up the user consent with HyBid SDK.

Manually setting and accessing the consent

If your app doesn't use any IAB TCF compliant CMP you may use the following convenience methods our SDK provides to set and access the shared storage compliant with IAB standards:

Setting the consent

To set the GDPR consent string use setIABGDPRConsentString method:

HyBid.getUserDataManager().setIABGDPRConsentString(GDPRConsentString);

Getting the consent

To read the stored value, use getIABGDPRConsentString method:

HyBid.getUserDataManager().getIABGDPRConsentString();

Clearing consent value

To remove the stored value, use removeIABGDPRConsentString method:

HyBid.getUserDataManager().removeIABGDPRConsentString();