Tapjoy SDK - C++ API
tapjoy::TJPrivacyPolicy Class Reference

Static Public Member Functions

static TJPrivacyPolicyHandle getPrivacyPolicy ()
 Returns the TJPrivacyPolicy instance for calling methods to set GDPR, User's consent, below consent age ,and US Privacy policy flags. More...
 
static void setSubjectToGDPR (TJPrivacyPolicyHandle handle, bool gdprApplicable)
 This can be used by the integrating App to indicate if the user falls in any of the GDPR applicable countries (European Economic Area). More...
 
static void setUserConsent (TJPrivacyPolicyHandle handle, const char *consent)
 Assigns a user ID for this user/device. More...
 
static void setBelowConsentAge (TJPrivacyPolicyHandle handle, bool isBelowConsentAge)
 In the US, the Children’s Online Privacy Protection Act (COPPA) imposes certain requirements on operators of online services that (a) have actual knowledge that the connected user is a child under 13 years of age, or (b) operate services (including apps) that are directed to children under 13. More...
 
static void setUSPrivacy (TJPrivacyPolicyHandle handle, const char *privacyValue)
 This is used for sending US Privacy value to behavioral advertising such as in the context of GDPR The value can be in IAB's US Privacy String Format consists of specification version to encode the string in number, explicit notice or opportunity to opt out in enum, opt-out sale in enum, LSPA covered transaction in enum . More...
 

Member Function Documentation

◆ getPrivacyPolicy()

static TJPrivacyPolicyHandle tapjoy::TJPrivacyPolicy::getPrivacyPolicy ( )
static

Returns the TJPrivacyPolicy instance for calling methods to set GDPR, User's consent, below consent age ,and US Privacy policy flags.

Returns
TJPrivacyPolicy singleton instance

◆ setBelowConsentAge()

static void tapjoy::TJPrivacyPolicy::setBelowConsentAge ( TJPrivacyPolicyHandle  handle,
bool  isBelowConsentAge 
)
static

In the US, the Children’s Online Privacy Protection Act (COPPA) imposes certain requirements on operators of online services that (a) have actual knowledge that the connected user is a child under 13 years of age, or (b) operate services (including apps) that are directed to children under 13.

Similarly, the GDPR imposes certain requirements in connection with data subjects who are below the applicable local minimum age for online consent (ranging from 13 to 16, as established by each member state).

For applications that are not directed towards children under 13 years of age, but still have a minority share of users known to be under the applicable minimum age, utilize this method to access Tapjoy’s monetization capability. This method will set ad_tracking_enabled to false for Tapjoy which only shows the user contextual ads. No ad tracking will be done on this user.

Parameters
isBelowConsentAgeTrue if below consent age (COPPA) applies to this user, false otherwise

◆ setSubjectToGDPR()

static void tapjoy::TJPrivacyPolicy::setSubjectToGDPR ( TJPrivacyPolicyHandle  handle,
bool  gdprApplicable 
)
static

This can be used by the integrating App to indicate if the user falls in any of the GDPR applicable countries (European Economic Area).

The value should be set to TRUE when User (Subject) is applicable to GDPR regulations and FALSE when User is not applicable to GDPR regulations. In the absence of this call, Tapjoy server makes the determination of GDPR applicability.

Parameters
gdprApplicabletrue if GDPR applies to this user, false otherwise

◆ setUserConsent()

static void tapjoy::TJPrivacyPolicy::setUserConsent ( TJPrivacyPolicyHandle  handle,
const char *  consent 
)
static

Assigns a user ID for this user/device.

This is used to identify the user in your application.

This is REQUIRED for NON-MANAGED currency apps.

Parameters
userIDuser ID you wish to assign to this device

◆ setUSPrivacy()

static void tapjoy::TJPrivacyPolicy::setUSPrivacy ( TJPrivacyPolicyHandle  handle,
const char *  privacyValue 
)
static

This is used for sending US Privacy value to behavioral advertising such as in the context of GDPR The value can be in IAB's US Privacy String Format consists of specification version to encode the string in number, explicit notice or opportunity to opt out in enum, opt-out sale in enum, LSPA covered transaction in enum .

eg. "1YNN" where 1 is char in string for the version, Y = YES, N = No, - = Not Applicable

See: IAB suggested US Privacy String Format : https://github.com/InteractiveAdvertisingBureau/USPrivacy/blob/master/CCPA/Version%201.0/US%20Privacy%20String.md#us-privacy-string-format

Parameters
privacyValueThe us privacy value string

The documentation for this class was generated from the following file: