Table of contents
General Data Protection Regulation (GDPR)
Under EU laws, app developers are required to collect user's consent to users in European Economic Area (EEA) before serving any ads. Read more on Privacy Guidelines for Publishers.
Criteo Publisher SDK uses the iAB GDPR Consent Framework in order to read users' consent. The following keys are read by Criteo SDK and would need to be readily available on NSUserDefaults for applicable users:
TCF v1.1:
IABConsent_ConsentString,IABConsent_SubjectToGDPRTCF v2.0:
IABTCF_TCString,IABTCF_gdprApplies
If you have a custom Consent Management Provider (CMP) to handle user consent, please make sure that your CMP conforms to the iAB CMP framework.
California Consumer Privacy Act (CCPA)
In order to help App developers ensure CCPA compliance, starting from version 3.3.0, Criteo Publisher SDK accepts two different methods to indicate user's consent in California state:
iAB CCPA Compliance Framework
According to the iAB CCPA Compliance Framework, App developers would need to ensure that the US privacy string with key IABUSPrivacy_String is readily available NSUserDefaults for applicable users. Read more on this document under the "In-app Support" section for more information.
If you have a custom Consent Management Provider (CMP) to handle the user's consent, please make sure that your CMP conforms to the iAB CCPA framework.
CCPA Binary API
Alternatively, Criteo Publisher SDK provides a public API for app developers who would prefer to pass explicit opt-out value to Criteo.
This value must be passed to Criteo as soon as your app receives consent, or otherwise, from applicable users.
[[Criteo sharedCriteo] registerCriteoPublisherId:criteoPublisherId withAdUnits:adUnits]; // Set CCPA opt out value [[Criteo sharedCriteo] setUsPrivacyOptOut:false];
| Description |
|---|---|
| User have not opted out |
| User opted out |