Kochava SDK and Consent Handling


As the Kochava SDK deals with GDPR-sensitive data, there are two approaches available for initializing the Kochava SDK when consent handling is necessary. The following document describes the different approaches to consent handling.


Self-Managed Consent

Use this approach if you plan to handle consent requirements on your own or using a 3rd party SDK. In this case, the Kochava SDK should simply not be initialized until after you have determined that consent is either not required or has been granted. It should never be initialized if consent is required and has not been granted, as the SDK would potentially begin transmitting GDPR-sensitive data without consent.

The pseudocode sample below illustrates when you should initialize the Kochava SDK under typical consent scenarios.

 

Pseudocode:

NOTE: If handling consent independently, the app should never make use of the consent-related API calls within the Kochava SDK unless you have enabled the Intelligent Consent Management feature described below. If ICM is not enabled, consent-related API calls have no effect.


Intelligent Consent Management

Kochava offers an Intelligent Consent Management (ICM) feature which can be leveraged to fully manage your GDPR consent requirements for your app and all of your SDKs. By using this feature the Kochava SDK will determine if, when and how often a user should be prompted for consent while also managing your data sharing partner list. Our Intelligent Consent Management provides far more functionality than simply notifying you when a user in the European Union (EU) and removes much of the burden associated with GDPR consent handling.

For more information on Intelligent Consent Management, refer to our Intelligent Consent Management support documentation.

 
 

Last Modified: Jul 11, 2018 at 1:35 pm