Privacy

GDPR – Managing Consent

As of May 25, 2019, the General Data Protection Regulation (GDPR) will be enforced in the European Union. To comply with GDPR, developers have the following options.

• You need to integrate with a Consent Management Platform (CMP) that complies with IAB TCF v2 for your user consent flow, such as Google UMP.
• You should wait for the CMP to establish consent status before loading an ad.
• Then Carty SDK will read the TCF v2 string provided by the CMP.

US Privacy compliance

State laws in the United States may require you to display a “Do Not Sell or Share My Personal Information” link to users in those states, or to provide other options through which those users can opt out of interest-based advertising. Such users can opt out of both interest-based advertising and the sale or sharing of their personal information for interest-based advertising. You must set a flag for users from those states that indicates whether those users opt out in this way. Refer to the sample code below for details.

• Java

// Sdk default value is false
CTGlobalSettings.getInstance().setDoNotSell(false);

• Kotlin

// Sdk default value is false
CTGlobalSettings.getInstance().isDoNotSell = false

##COPPA Implementation

Whether it is an APP for children under the age of 13 and is subject to and comply with COPPA regulations. If you select "Yes", the data processing of persistent identifiers will strictly comply with COPPA, and will not be used to serve behavior-oriented ads or track users for this purpose (it is recommended to be placed before the SDK initialization code)

• Java

// Sdk default value is false
CTGlobalSettings.getInstance().setCoppa(false);

• Kotlin

// Sdk default value is false
CTGlobalSettings.getInstance().isCoppa = false

CartySDK data collection

To help you answer the questionnaire about the information collected by CartySDK, please refer to the following table. Here is all the information CartySDK collected.

Tips: The list only describes CartySDK data collection. The list does not describe developers’ overall app data collection and use, or that of any other SDK.

Types of data	Used for tracking?	Purpose
Location Data
Coarse Location	YES	Third-party advertising and analytics
Identifiers
Device ID	YES	Third-party advertising and analytics
Usage Data
Product Interaction	NO	Third-party advertising and analytics
Advertising Data	NO	Third-party advertising and analytics