📘

Note

Please review the User Docs before implementation. This SDK changes the existing implementation.

Overview

This page describes the changes you need to make for GDPR compliance to the installation of the CleverTap Android and iOS SDKs in your application.

Android

Restrict Tracking with Google Ad ID

In compliance with GDPR, by default the CleverTap Android SDK will not use the Google Ad Id to generate CleverTap IDs.

From CleverTap Android SDK 3.1.9 onwards, you can choose to enable the use of Google Ad ID to generate CleverTap IDs by adding the following meta-data tag in the AndroidManifest.xml.

<meta-data
   android:name="CLEVERTAP_USE_GOOGLE_AD_ID"
   android:value="1"/>

Right to Suppress - Opt Out

From CleverTap Android SDK 3.1.9 onwards, in compliance with GDPR, we provide the following method using which the app can stop sending events to CleverTap.

cleverTap.setOptOut(true);

If the user wants to opt in again to share their data, you call the same method like this.

cleverTap.setOptOut(false);

By default, the SDK will send data to CleverTap i.e opt out will be set to false. It would be a good practice to capture the opt out flag of the user and set it whenever the app launches.

Device Network Information Reporting in Android

From CleverTap Android SDK 3.1.9 onwards, in compliance with GDPR, the CleverTap Android SDK will not capture any kind of personal information like WiFi, Bluetooth, Network Information and user IP information. To enable the capturing of all this information, you can call the following method,

cleverTap.enableDeviceNetworkInfoReporting(true);

To disable Device Network information to be sent to CleverTap you can use the same method as follows.

cleverTap.enableDeviceNetworkInfoReporting(false);

By default, Device Network Information will not be collected by CleverTap.

Marketing Opt Out

From CleverTap Android SDK 3.1.9 onwards, in compliance with GDPR, to ensure opt out of the user from all marketing channels, you can set a profile property against that user as shown below.

profileUpdate.put("MSG-email", false); // Disable email notifications
profileUpdate.put("MSG-push", true); // Enable push notifications
profileUpdate.put("MSG-sms", false); // Disable SMS notifications
profileUpdate.put(“MSG-push-all”, false); //Disable push notifications for all devices
cleverTap.profile.push(profileUpdate);

By default, all marketing channels will be available for communication with the user.

iOS

Right to Suppress - Opt Out

From CleverTap iOS SDK 3.1.7 onwards, in compliance with GDPR, we provide the following method that your app can use to stop sending events to CleverTap.

[[CleverTap sharedInstance] setOptOut:YES];

CleverTap.sharedInstance().setOptOut(true)

If the user wants to opt-in again to share their data, you call the same method like this.

[[CleverTap sharedInstance] setOptOut:NO];

CleverTap.sharedInstance().setOptOut(false)

By default, the SDK will send data to CleverTap i.e opt-out will be set to false. It would be a good practice to capture the opt-out flag of the user and set it whenever the app launches.

Device Network Information Reporting in iOS

From CleverTap iOS SDK 3.1.7 onwards, in compliance with GDPR, the CleverTap iOS SDK will not capture any kind of personal information like WiFi, Network Information, and user IP information. To enable the capturing of all this information, you can call the following method.

[[CleverTap sharedInstance] enableDeviceNetworkInfoReporting:YES];

CleverTap.sharedInstance().enableDeviceNetworkInfoReporting(true)

To disable Device Network information to be sent to CleverTap you can use the same method as follows.

[[CleverTap sharedInstance] enableDeviceNetworkInfoReporting:NO];

CleverTap.sharedInstance().enableDeviceNetworkInfoReporting(false)

By default, Device Network Information will not be collected by CleverTap.

Marketing Opt Out

From CleverTap iOS SDK 3.1.7 onwards, in compliance with GDPR, to ensure opt out of the user from all marketing channels, you can set a profile property against that user in the following way.

NSDictionary *profile = @{
    @"MSG-email": @NO, // Disable email notifications
    @"MSG-push": @NO, // Enable push notifications
    @"MSG-sms": @NO, // Disable SMS notifications
    @"MSG-push-all": @NO //Disable push notifications for all devices
};

[[CleverTap sharedInstance] profilePush:profile];

let profile: Dictionary<String, AnyObject> = [
    "MSG-email": false, // Disable email notifications
    "MSG-push": false, // Disable push notifications
    "MSG-sms": false, // Disable SMS notifications
    "MSG-push-all": false // Disable push notifications for all devices
]

CleverTap.sharedInstance()?.profilePush(profile)

By default, all marketing channels will be available for communication with the user.

Web/Javascript SDK

Data Suppress

• This will ensure that the data from the device will not reach CleverTap's servers.
• By default, the optOut is set to False.
• If a device needs to be opted out, at the JS SDK end, the flag needs to be set.

IP Collection

• This will ensure that the CleverTap does not auto collect the device IP.
• By default, the useIP is set to False.
• If a customer wants to collect to the device IP, they need to explicitly set it to true.

For more information, visit the Web Quick Start Guide.

clevertap.privacy.push({optOut: true}); //call the flag to true, if the user of the device opts out of sharing their data

clevertap.privacy.push({useIP: false}); //call the flag to true, if the user agrees to share their IP data

CleverTap Cookie Details

CleverTap sets first-party cookies and they are used to anonymously identify the website visitors/users. Customers explicitly choose to record data against the user's profile & activity. There's no implicit PII data recorded by the cookie. Refer to the table below to learn about the different cookies.

Parameters for Local Storage

FAQ

1. Can this cookie data collection be blocked through configuration?
   No. The cookie can not be blocked without blocking all cookies of the customer's domain.