Opt-out compliance

Understand how to implement opt-out compliance for the Analytics SDK to comply with General Data Protection Regulation and California Consumer Privacy Act requirements.

Read time 1 minute

Last updated 8 months ago

All versions of the Analytics SDK provide compliance mechanisms consistent with known regulatory customers and guidance including General Data Protection Regulation (GDPR) and California Consumer Privacy Act (CCPA).

Unity 6.2 and later with Analytics SDK 6.1 and later

The Analytics SDK is controlled by the Developer Data framework

EndUserConsent

API, present in the Unity Engine from 6.2 onwards. To start or stop data collection, you must set the consent status for

AnalyticsIntent

Granted

Revoked

respectively.

For specific information about granting consent with the

EndUserConsent

API, refer to Developer Data framework.

Unity 6.1 and earlier, or Analytics SDK 6.0 and earlier

In regions that require you to provide an opt-out, you must provide your own logic to determine whether the player has opted out. You may call

AnalyticsService.Instance.StartDataCollection()

to start the SDK if the player hasn't opted out, otherwise you shouldn't call it and the SDK remains dormant.

Important

Unity Analytics requires you to implement a privacy solution separate from Unity Ads. If you're using both Unity Ads and Analytics, the Unity Ads opt-out mechanism does not apply to both services.


async void Start(){   await UnityServices.InitializeAsync();      if (playerHasOptedOut)   {		// Do nothing, leave the SDK off   }   else   {		AnalyticsService.Instance.StartDataCollection();   }}

Note

these API methods changed in version 5.0.0 of the SDK. Please ensure you have the latest version of the SDK installed!

Documentation

Development

User Acquisition

Monetization

Industry