Mobile: Manage GDPR compliance

In this article, we will focus on the GDPR methods to implement, for iOS and Android, in order to ensure compliance with the European text. 


First, we would like to remind you that the permission for data collection is managed differently from the permission for push notifications. Although these two permissions are linked, they do use two distinct methods. 



MANAGE GDPR COMPLIANCE ON ANDROID


There are two steps for sending user opt-in for data collection to Accengage:


First, there is a parameter that lets us know that the GDPR method is being called and used in your application. 
The parameter acc_optin_data, have to be in your string resource file: <string name="acc_optin_data">true</string> 


Then, you have to call the method setOptinData before any other methods from the Accengage SDK for letting us know the opt-in state of the user: A4S.get(this).setOptinData(this, OptinType.YES); 


The GDPR pop-up needs to be developed on your side. This allows you to personalize the content and the form as you wish. 


If the user accepts GDPR terms, he becomes opt-in GDPR. So, you can collect data and send push notifications to the user. 

However, if he refuse, he becomes opt-out GDPR. This means that we couldn't collect any data, even some essential elements for sending notifications, such as device ID or token. In this case, our SDK will not launch and therefore it will not be possible to send any type of notifications to this user.  


If needed, you can find more information about the integration of the GDPR in our technical documentation



MANAGE GDPR COMPLIANCE ON iOS


There are two steps for sending user opt-in for data collection to Accengage.


First, there is a parameter that lets us know that the GDPR method is being called and used in your application. 

This parameter is startWithOptIn: [Accengage startWithOptIn: ACCOptInEnabled]; 


Then, you have to call the method setDataOptInEnabled before any other methods from the Accengage SDK for letting us know the opt-in state of the user: setDataOptInEnabled 


The GDPR pop-up needs to be developed on your side. This allows you to personalize the content and the form as you wish. 


If the user accepts GDPR terms, he becomes opt-in GDPR. So, you can collect data and send push notifications to the user. 

However, if he refuse, he becomes opt-out GDPR. It means that we couldn't collect any data, even some essential elements for sending notifications, such as device ID or token. In this case, our SDK will not launch and therefore it will not be possible to send any type of notifications to this user.  


On iOS, in order to become opt-in notifications, the user has to accept the push pop-up. Nevertheless, if the user is GDPR opt-out, there is no need to display the notification authorization pop-up. Indeed, in all cases, the information will not be reported back. 


If needed, you can find more information about the integration of the GDPR in our technical documentation



HOW WE MANAGE OPTIN TO OPTOUT DATA PROFILES?

The operation is the same for both OS, when a user is opt-in GDPR and then becomes opt-out GDPR. 

The main difference is that we already have data from the user in our database. In this situation, our SDK will get back the opt-out status and will stop all its activities. Afterwards, we are applying a script which have for objective to wipe all the setDataOptIn: NO profiles, per application. This script runs continuously and randomly, it allows us to purge a GDPR opt-out profile within 7 days



Please feel free to contact our Support team if you have any additional questions: 

Cet article vous a-t-il été utile ?
Utilisateurs qui ont trouvé cela utile : 0 sur 0

Commentaires

0 commentaire

Vous devez vous connecter pour laisser un commentaire.

Envoyer une demande