Across Europe new privacy legislation has been introduced; GDPR.
In a nutshell it says that the following are the responsibility of not only the customer but also the supplier:
- Seeking consent from data subjects where personal data is stored on their behalf
- Providing robust processes and tools to enable the “right to be forgotten” (i.e. data about an individual must be able to be completely deleted, and evidence produced that this has been done)
- Setting out clear, unambiguous retention periods for the data we store, and a defined business need for retaining specific types of data
- Reporting breaches if and when they occur
The legislation is in force now but will be enforced from May 2018 with significant fines applied in cases of non-compliance or breach.
Indeed in the sectors the company I work for (mostly Government and Charities) we're seeing this crop up more and more in RFP documents.
This has a potentially large impact on Sitecore's personalisation and the xDB going forward.
So finally to my question(s):
Does anyone have an idea of what Sitecore road-map is for GDPR? So I can explain back to customers how Sitecore will deal with this.
Are any partners looking at this at the moment? Both in terms of how Sitecore can be compliment now (perhaps purging users from xDB) or thinking about using pseudonymisation?
Finally is anyone aware of a detailed guide of what Personally Identifiable Information Sitecore stores in XDB out of the box
Big broad sweeping question, but one our InfoSec crew are increasingly curious about.
Update for Sitecore 9
The right to be forgotten - fulfilled by Sitecore 9 by allowing anonymisation of a contact - it will delete all personal identifiers for the user but keep an anonymous record.
Opt-outs - There is a solution to remove a contact from all email lists now (without removing them from service emails - password resets etc.)
Personal information - You can add an attribute for PII contact details now which stops it being indexed and searchable.
Update for Sitecore 6, 7, 8