{"id":37979,"date":"2017-11-29T08:06:38","date_gmt":"2017-11-29T08:06:38","guid":{"rendered":"https:\/\/www.xmpie.com\/new-normal-data-privacy-part-2-ensuring-compliance-gdpr\/"},"modified":"2017-11-29T08:06:38","modified_gmt":"2017-11-29T08:06:38","slug":"new-normal-data-privacy-part-2-ensuring-compliance-gdpr","status":"publish","type":"post","link":"https:\/\/www.xmpie.com\/fr\/new-normal-data-privacy-part-2-ensuring-compliance-gdpr\/","title":{"rendered":"The New Normal for Data Privacy: Part 2 \u2013 How We Are Ensuring Compliance with GDPR"},"content":{"rendered":"

In my last blog post<\/a>, I spoke about what GDPR was and how it will affect anyone who is handling or processing any data relating to EU Citizens. Naturally, this kind of legislation prompts many new challenges for vendors to address and XMPie is no different. XMPie products allow for the storage and processing of customer data, so we\u2019ll need to make changes to how our products and services operate to help our customers be compliant with the new law.<\/p>\n

 <\/p>\n

Over the past few months, we have been identifying the areas within both our software and our services that will be affected and we are committed to ensuring compliance in accordance with the GDPR before the legislation comes into force in May 2018.

\n\t\t\t\t\n\t\t\t\t

We are committed to ensuring compliance in accordance with the GDPR before the legislation comes into force in May 2018.<\/p>\n\t\t\t\t

<\/i>Click To Tweet<\/span><\/div>\n\t\t\t\t<\/a>\n\t\t\t\t<\/div><\/p>\n

 <\/p>\n

I have found GDPR to be a really interesting exercise for XMPie, although I am not sure that my colleagues in R&D will agree with me! Simple clauses like a Consumer’s Right to Erasure could cause ripple effects throughout the platform. A consumer\u2019s data could exist within a single print piece or across an entire journey of touchpoints so identifying and deleting them is not a simple process. And what if that consumer also exists within a purchase campaign on a uStore site? The problem lies with the fact that we need to identify an individual, not just by RecipientID and delete that data, or pull all of the recipient\u2019s information, including tracking data.<\/p>\n

 <\/p>\n

XMPie\u2019s solutions will be compliant when we act directly as the Data Processor and we will also identify and make clear those areas that are out-of-scope and which will remain the responsibility of the Data Controllers directly. Thus, both the Data-Controllers and that Data Processors will have the tools to comply with the regulation.<\/p>\n

 <\/p>\n

In relation to XMPie as the Data Processor, we are working towards three things:<\/p>\n