Tapjoy is GDPR-compliant based on "legitimate interest," therefore the following functions are not mandatory. However, we offer these functions for those publishers who wish to pass consent information to Tapjoy. If the publisher implements these functions and the user does not consent, Tapjoy will serve non-interest based content to that user.
Tapjoy has features that help publishers comply with the California Consumer Privacy Act (CCPA). The “TJPrivacyPolicy” class allows you to manage all privacy flags (GDPR, user consent, below consent age, and US privacy).
NB: If you are updating from a previous version of the Tapjoy SDK and have set privacy values using the old method don’t worry – the new SDK will still read the previously set values and you do not need to manually set them again. However, we would recommend eventually migrating your code to use this new method.
To comply with the Google Families Program rules, where apps targetting children should not access the advertising id, Tapjoy SDK 12.10.0 has added a new privacy flag you can choose to implement.
This flag can be set any time, before or after connect, and can be changed at any time during the session.
To set your privacy flags first create an instance of TJPrivacyPolicy:
TJPrivacyPolicy tjPrivacyPolicy = Tapjoy.getPrivacyPolicy();
A setUserConsent function takes a string of either "0″ (user does not consent), "1″ (user does consent) or a more detailed consent string. This more detailed string is the consent string as described in the Transparency and Consent Framework as supported by the IAB.
An optional "subject to GDPR" flag takes a boolean value that can be set to YES/TRUE (if the user is subject to GDPR rules) or NO/FALSE (if the user is not subject to GDPR rules). This function should only be called if the application has made its own determination as to whether GDPR is applicable to the user or not. If this function is not called, Tapjoy assumes the application has not made such a determination, and therefore Tapjoy makes its own determination of GDPR applicability.
A belowConsentAge flag takes a boolean value and can either be TRUE or FALSE. This flag can be used to inform us of COPPA compliance and also GDPR age compliance. It will also inform Tapjoy’s ad tracking policy.
Finally is the new USPrivacy flag. This flag takes a string value. The string that this flag takes is derived from the IAB’s US Privacy String Format and encodes the string in an enum.
1YNN where 1 is char in string for the version, Y = YES, N = No, – = Not Applicable
See: IAB suggested US Privacy String Format
This example shows the setting of all privacy flags:
TJPrivacyPolicy tjPrivacyPolicy = Tapjoy.getPrivacyPolicy(); tjPrivacyPolicy.setSubjectToGDPR(true); tjPrivacyPolicy.setUserConsent(“0”); tjPrivacyPolicy.setBelowConsentAge(true); tjPrivacyPolicy.setUSPrivacy(“1YYY”);
If a user does not consent or withdraws existing consent, will the Tapjoy SDK still send advertising identifiers to Tapjoy?
Yes. The functions listed above are designed for interest-based advertising, and they send the user consent status for interest-based advertising to Tapjoy. Therefore, the status of the consent does not disable Tapjoy SDK from sending advertising identifier at SDK initialization or during ad requests.
Tapjoy’s legal basis for compliance is ‘legitimate interest’. However, the publisher’s legal basis for compliance, and consequently their requirement for advertiser identifier collection, could be different than Tapjoy’s.
It is left to application to determine if the Tapjoy SDK should be initialized or not, depending on the application’s compliance need. For example, if an application’s legitimate basis for collection of advertising identifier is consent, and user has not consented, then the Tapjoy SDK should not be initialized for such users.
If a user from a country that is not covered by GDPR does not consent or withdraws consent, would Tapjoy limit advertising to non-interest-based ads for such a user?
The Tapjoy SDK provides flexibility to handle different types applications, including applications that have no in-app method for determining whether the user is subject to GDPR or not.
Therefore, when an Application does not make any determination (i.e. the subjectToGDPR function is not called), Tapjoy servers determine whether the user is subject to GDPR. Then, Tapjoy honors the user’s consent preferences only for ad requests that Tapjoy determines are coming from GDPR-covered users.
If the intent is to allow users from any country to withdraw consent as if they were governed by GDPR, this can be done by calling the subjectToGDPR method with TRUE for all non-consenting users. In this case, Tapjoy’s servers will honor the content of the subjectToGDPR method call, and will not make its own determination as to whether or not the user is covered by GDPR. The publisher may also contact firstname.lastname@example.org and request that Tapjoy honor the consent preferences of all users of their application, regardless of whether they are covered by GDPR or not.