Overview

The California Consumer Privacy Act (CCPA) was enacted to provide California consumers with greater transparency and control over their personal information.

Initially prompted by regulation in the California Consumer Privacy Act (CCPA), the IAB's US Privacy String was created to support compliance with the CCPA.

👍

For more information, see the following IAB CCPA's resources:

• About the IAB CCPA
• IAB CCPA US Privacy String (GitHub)
• IAB CCPA US Privacy API (GitHub)

Implement the US Privacy String

Prerequisites

To set up the US Privacy String on your app, follow the set up guidance to configure the CCPA US Privacy String in your OneTrust tenant.

How it works

With this latest implementation, there is no SDK code for the app to call to initialize or set the IAB US Privacy String. The SDK handles it automatically based on the configuration in the OneTrust tenant.

Access the US Privacy String

Per IAB Standards, the US Privacy String is saved to registry under the TCF section IABUSPrivacy_String key.

value = “”
Key = “IABUSPrivacy_String”
regSection = createObject(“roRegistrySection”, “TCF”)
if regSection.exists(key) then value = regSection.read(Key)
print value

📘

If your application is configured with a single geolocation rule, OneTrust will save and update the IAB CCPA values for every location, regardless of the value provided for geolocation. This is because the OneTrust SDK does not make a geolocation API call when only one geolocation rule exists and we will be unable to determine which location to apply the IAB CCPA updates to.