Configure Marketing Cloud Engagement
Runtime Toggles
Event Tracking
Handle URLs
Data Protection and Privacy
Changelog
The Engagement SDK helps you comply with data protection regulations, such as the European Union’s General Data Protection Regulation (GDPR).
The SDK supports three privacy modes that affect your app’s ability to send messages and collect data:
These data protection and privacy features are available only in Marketing Cloud Engagement.
Note
Use Right to Be Forgotten mode when a contact requests that you remove all their data from Marketing Cloud Engagement. This mode marks a contact, identified by the SDK’s contact key string, as forgotten. This setting prevents data collection from that contact and blocks messages to them.
By default, this suppression lasts for 14 days. You can configure the suppression period in Contact Builder in Marketing Cloud Engagement. At the end of the suppression period, Marketing Cloud Engagement permanently deletes the contact data.
Note
The SDK restricts all functionality after it receives the first Right to Be Forgotten mode change for a contact from the server. The SDK receives this change through a silent push notification or when your app enters the foreground.
Right to Be Forgotten mode disables these functions for that contact for the life of your app:
When a contact deletes and reinstalls your app on their device, they move out of Right to Be Forgotten mode.
Restriction of Processing mode marks a contact, identified by the SDK’s contact key string, as restricted from data processing.
Restriction of Processing mode restricts these data operations for the contact:
The SDK restricts all functionality after it receives a Restriction of Processing mode change for a contact. This mode completely disables these functions when the contact is in a restricted state:
When the contact moves out of the restriction state, the SDK receives notification through a silent push notification or when your app enters the foreground. The SDK automatically reconfigures itself based on your last-used configuration settings.
Do Not Track mode marks a contact, identified by the SDK’s contact key string, as restricted from tracking activities. This setting restricts data operations that collect or act on Personally Identifiable Information (PII).
When a contact moves to Do Not Track mode, the SDK restricts functionality after it receives the first mode change from the server through a silent push notification or when your app enters the foreground.
This mode completely disables behavioral analytic tracking, geofences, and beacons. Push notifications and inbox functionality continue to work. In the Do Not Track state, the SDK can still track message delivery receipts and changes in registration attributes, such as tags and attributes.
Behavioral analytic tracking includes these events:
When the contact moves out of the Do Not Track state, the SDK receives notification through a silent push notification or when your app enters the foreground. The SDK automatically reconfigures itself based on your last-used configuration settings.
All recent versions of the SDK include the architecture required to enable data compliance functionality. Version 5.5.0 and later of the SDK for Android and version 5.1.0 and later of the SDK for iOS include this functionality. If your app uses an earlier version of the SDK, upgrade it.
In iOS apps, enable background refresh to ensure that silent pushes work as expected. For more information on data protection, see iOS Data Protection.