Our latest SDK release contains important functionality for supporting GDPR compliance as well as a few bug fixes and enhancements. If your app needs to be GDPR compliant, you’ll want to make sure you immediately update your apps to 5.1 and take advantage of the new functionality. Before we dive into the details, be sure to share the news with your dev team by sending them the SDK docs.
This SDK release contains the most up-to-date functionality for you to handle user requests to opt out of data collection or to have their data deleted. We added new APIs to the iOS, Android, and React Native SDKs and updated the Profile API.
Supporting consent and right to be forgotten
The new APIs allow you to instruct the SDK to do a few things when it comes to user consent. The first, pauseDataUploading allows you to continue to collect data on the device, but not send it to Localytics. This lets you collect data while you confirm a user’s opted-in status on your servers. If you confirm they’re opted in, you can then unpause data collection and all the data stored on the device will be sent to Localytics. The second, setPrivacyOptedOut allows you to stop all data collection for the user and simultaneously delete all personal information that is stored in Localytics.
Using the Profile API, you can ask Localytics to delete all of a user’s personal information should a user request to be forgotten through one of your other systems. If you add the Profile attribute “privacy_delete” to a user’s Profile and set it to “true”, Localytics will automatically delete all stored personal information on that user. This makes it easy to manage privacy requests across your entire marketing stack.
For more a detailed look at how to configure the SDK to handle privacy requests, you can read through this help doc.
Bug fixes and Enhancements
On Android, you now have more control over location updates by being able to set custom intervals. This allows you to decide how frequently the app requests location data from a device. Keep in mind, changing the interval will have an impact on how quickly your app depletes a device’s battery life.
On iOS, we fixed an issue that made targeting users for in-app messages, based on their app version, unreliable. Now app versions with more than one decimal point (ie. 2.2.1) will be targeted correctly.
These SDK changes will make it much easier for you to manage GDPR compliance for your app. With the regulations going into effect on May 25th, it’s important to get the updated SDK integrated and your process for handling consent and deletion requests set up as soon as possible. If you have questions or need assistance, be sure to log into the dashboard to submit a ticket. You can stay on top of updates to the SDK by checking the changelog.
Thanks for signing up. Look for your first email shortly!
We’ll reach out shortly to schedule a time to talk.