User privacy
Configure privacy settings like GDPR, CCPA, or COPPA in accordance with user consent and applicable regulations using the Tapjoy Android privacy documentation.
Read time 3 minutesLast updated 6 months ago
GDPR
Publishers using the Tapjoy Offerwall and associated Unity Technologies SF services, including the Unity Rewards offerwall, should ensure their consent mechanisms gather consent for these services and data processing where required. These measures must be reflective of any relevant legal requirements, and comply with the applicable Data Protection Addendum with Tapjoy. Publishers using the Unity Rewards offerwall, should specifically ensure that their consent mechanisms collect consent for such services and the processing of data in accordance with Unity's Game Player and App User Privacy Policy.CCPA
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). If you are updating from a previous version of the Offerwall SDK and have set privacy values using the old method, 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.Android advertising ID opt out
To comply with the Google Families Program rules, where apps targetting children should not access the advertising ID, Offerwall 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.Tapjoy.optOutAdvertisingID(this, true);// Get current valueTapjoy.getOptOutAdvertisingID(context)
Implementation
To set your privacy flags first create an instance of TJPrivacyPolicy:A setUserConsent function takes aTJPrivacyPolicy tjPrivacyPolicy = Tapjoy.getPrivacyPolicy();
TJStatusTJStatus.FALSETJStatus.TRUETJStatus.UNKNOWNTJStatusTJStatus.TRUETJStatus.FALSETJStatus.UNKNOWNTJStatusTJStatus.TRUETJStatus.FALSETJStatus.UNKNOWN1YNNYou can also get the current values of privacy flags like so:TJPrivacyPolicy tjPrivacyPolicy = Tapjoy.getPrivacyPolicy();tjPrivacyPolicy.setSubjectToGDPR(TJStatus.TRUE);tjPrivacyPolicy.setUserConsent(TJStatus.FALSE);tjPrivacyPolicy.setBelowConsentAge(TJStatus.TRUE);tjPrivacyPolicy.setUSPrivacy("1YYY");
TJStatus subjectToGDPR = privacyPolicy.getSubjectToGDPR();TJStatus userConsent = privacyPolicy.getUserConsent();TJStatus belowConsentAge = privacyPolicy.getBelowConsentAge();String usPrivacy = privacyPolicy.getUSPrivacy();
GDPR FAQ
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 the Offerwall 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, might be different than Tapjoy’s.It is left to application to determine if the Offerwall 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 Offerwall SDK should not be initialized for such users.
The Offerwall 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 (for example, 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 can also contact support@tapjoy.com and request that Tapjoy honor the consent preferences of all users of their application, regardless of whether they are covered by GDPR or not.