Privacy Compliance
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 need to handle the following:
- 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.
Developers can pass the do-not-sell flag to CartySDK using the following code. ( it is need to be placed before the CartySDK initialization code)
- Objective-C
//Not Opt Out
[[CartyADSDK sharedInstance] setDoNotSell:NO];
//Opt Out
[[CartyADSDK sharedInstance] setDoNotSell:YES];- Swift
//Not Opt Out
CartyADSDK.sharedInstance().setDoNotSell(false);
//Opt Out
CartyADSDK.sharedInstance().setDoNotSell(true);COPPA Implementation
Our platform is built to abide by regulations such as COPPA, (Children's Online Privacy Protection Act), which imposes certain restrictions on the operators of websites and online services that are directed to children under 13 years of age。 For more details, you may refer to The Children’s Online Privacy Protection Act (COPPA).
As per Complying with COPPA: Frequently Asked Questions | Federal Trade Commission, developers are responsible for determining whether or not an app is child-directed by considering factors including “its subject matter, visual content, use of animated characters or child-oriented activities and incentives, music or other audio content, age of models, presence of child celebrities or celebrities who appeal to children, language or other characteristics of the Web site or online service, as well as whether advertising promoting or appearing on the Web site or online service is directed to children".
You should make use of the following API to pass a flag to the CartySDK:. ( it is need to be placed before the CartySDK initialization code)
- Objective-C
//end-user is not a child
[[CartyADSDK sharedInstance] setCOPPAStatus:NO];
//end-user is a child
[[CartyADSDK sharedInstance] setCOPPAStatus:YES];- Swift
//end-user is not a child
CartyADSDK.sharedInstance().setCOPPAStatus(false);
//end-user is a child
CartyADSDK.sharedInstance().setCOPPAStatus(true);Apple's app privacy questionnaire
According to Apple’s privacy details on the App Store requirements, starting December 8, 2020, app developers need to define which data is collected by their apps and SDKs integrated in their apps.
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.
| 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 |
