GDPR - New situations for new Regulations
A) User consents to have a profile in Xeerpa
In this case, the brand should send us the user ID by calling our API through this URL:
The brand can set or modify the Robinson parameter as an informative-not operational tag to specify whether the user wants to receive Commercial Communications or not by calling our API through this URL:
- We strongly recommend the brand to assign a unique CRMID to each user to be able to unequivocally identify and modify any profile that may have changed his details on the brand's CRM but not in Xeerpa. If you assign duplicated IDs across different campaigns for different users, those users with same ID will be unified.
- It is also very important to update users' preferences regarding the robinson parameter with each new login or registry, in order to count with users' newest choices. The robinson parameter works under the following logic:
robinson=true : User doesn't want to receive commercial communications.
robinson=false : User wants to receive commercial communications.
- AUTH-ID and AUTH-TOKEN will be sent back by Xeerpa during the step 2.4 of the login process if the Brand is using the Xeerpa Connect BackAuth Integration Method.
B) User should not have a profile in Xeerpa
In order to comply with the new GDPR Guidelines, there are two possibilities.
The brand can automatically request the anonymization of the profile by calling our API through this URL:
If the brand wants to remove the profile instead, the profile can be completely removed by calling our API through this URL:
If there is no user with that CRMID in the Brand's Xeerpa Database, our Service will respond "User doesn't exist" and the user won't be created.