Consumer privacy act compliance#

All versions of the Unity Ads SDK are compliant with the following consumer privacy acts:

• The California Consumer Privacy Act (CCPA), which is effective in California starting January 2019.
• Brazilian General Data Protection Law (LGPD), which is effective starting August 2021.
• The Virginia Consumer Data Privacy Act (VCDPA), which is effective in Virginia starting January 2023.
• The Colorado Privacy Act (CPA), which is efffective in Colorado starting July 2023.
• The Connecticut Data Privacy Act (CTDPA), which is effective in Connecticut starting July 2023.
• Quebec Law 25 (QCLAW25), which is effective in Quebec, Canada starting September 2023.
• Utah Consumer Privacy Act (UCPA), which is effective in Utah starting December 2023.
• Florida Digital Bill of Rights (FDBR), which is effective in Utah starting July 2024.
• Oregon Consumer Privacy Act (OCPA), which is effective in Oregon starting July 2024.
• Texas Data Privacy and Security Act (TDPSA), which is effective in Texas starting July 2024.
• Montana Consumer Data Privacy Act (MCDPA), which is effective in Montana starting October 2024.

Visit our legal site for more information on Unity's approach to privacy.

Implement Unity's built-in consent solution#

The recommended best practice is to update to the latest version of the Unity Ads SDK, but this is not required, but this is not required for CCPA, LGPD, VCDPA, CPA, CTDPA, Quebec Law 25, UCPA, FDBR, OCPA, TDPSA, MCDPA compliance.

SDK versions 2.0 and later automatically present affected users with an opportunity to opt in to targeted advertising, with no implementation needed from the publisher. On a per-app basis, the first time a Unity ad displays, a banner provides the option to opt in to behaviorally targeted advertising. Thereafter, the user can select an information button to manage their privacy choices.

Implement a custom consent solution#

If you implement a custom consent solution in your app, you must send your users’ consent statuses to the Unity Ads SDK.

Custom consent implementation using Developer Consent API#

If a publisher or mediator sends us a value via the Developer Consent API, the Unity opt-in does not display. Note that users can still request opt-out or data deletion, and can access their data at any time during an ad display by selecting the Unity Data Privacy icon.

While the recommended best practice is to use boolean values for MetaData consent flags, the Unity Ads SDK also accepts integer values (1 or 0), interpreting 1 as “true” and 0 as “false”. This ensures compatibility with customized or legacy SDK implementations that may use these integer values. While the Unity Ads SDK supports integer values, publishers are encouraged to use boolean values to pass consent flags as shown in the following code examples.

Use the following API to pass a consent flag to the Unity Ads SDK.

Unity (C#)#

// If the user opts in to targeted advertising:
MetaData privacyMetaData = new MetaData("privacy");
privacyMetaData.Set("consent", "true");
Advertisement.SetMetaData(privacyMetaData);

// If the user opts out of targeted advertising:
MetaData privacyMetaData = new MetaData("privacy");
privacyMetaData.Set("consent", "false");
Advertisement.SetMetaData(privacyMetaData);

iOS (Objective-C)#

// If the user opts in to targeted advertising:
UADSMetaData *privacyConsentMetaData = [[UADSMetaData alloc] init];
[privacyConsentMetaData set:@"privacy.consent" value:@YES];
[privacyConsentMetaData commit];

// If the user opts out of targeted advertising:
UADSMetaData *privacyConsentMetaData = [[UADSMetaData alloc] init];
[privacyConsentMetaData set:@"privacy.consent" value:@NO];
[privacyConsentMetaData commit];

Android (Java)#

// If the user opts in to targeted advertising:
MetaData privacyMetaData = new MetaData(this);
privacyMetaData.set("privacy.consent", true);
privacyMetaData.commit();

// If the user opts out of targeted advertising:
MetaData privacyMetaData = new MetaData(this);
privacyMetaData.set("privacy.consent", false);
privacyMetaData.commit();