Data Processing Guide

After the EngageLab SDK is initialized in your app or website, it will collect data. For more information, see The data collected by the EngageLab SDK.

The data automatically collected by the EngageLab SDK is generally not PII (Personally Identifiable Information), except for any sensitive user information you pass to us in user attributes. Remember, linkable data (such as names or birthdays) is still considered PII, even if it is not sensitive data. Customers handling PII are required to establish a privacy policy that specifies the content they store.

This guide will explain how to use EngageLab without sending personal user data.

Personal Information in User Attributes

EngageLab requires you to obtain appropriate consent for any data you send to us, including any personal data you may send as user attributes or other fields.

For example, if you send us a user's phone number, you must ensure that you have obtained all necessary consents.

Some data is automatically collected by the EngageLab SDK. A complete list of automatically collected information can be found here: The data collected by the EngageLab SDK.

You can exclude fields by modifying our SDK code or customize these fields using the provided helper methods. Descriptions and examples of each method are provided below.

Obtaining User Consent

To meet any compliance requirements, you should not initialize the EngageLab SDK before the user consents to the privacy agreement. Please proceed with initialization only after the user has agreed to the privacy agreement.

Push Tokens

Push Tokens are generally not considered PII data because you cannot share Push Tokens with others, nor can they be used to contact the person or determine any information about them. However, we recommend disclosing in your privacy policy that data is shared with third parties to send personalized or targeted notifications. This applies regardless of the service you use.