GDPR News Center News for 07-26-2018


As of May 25, 2018, registrant information-name, organization, address, phone number, and email-will be considered personal data that can no longer be published in the public Whois. While the audience for registrant data may no longer be the entire public, it will still be sizable. The service also provides a way for third parties to contact the domain owner via the privacy service email address displayed in the Whois output, an option that will not be provided as a part of GDPR data protection. The personal data associated with a domain that is protected by Whois privacy will not be shared with registries. Here we will disclose all the uses of personal data that are required by contract in order for us to provide the requested domain service. 

At this time, we will also request consent from the data subject for those data uses where our legal basis is their consent. Request consent for any data elements that are not required by contract,. Certain registries require additional information in order to complete domain registrations, and in these cases, we will include in our contract a point about processing those additional pieces of registrant data. We give the option of processing any piece of personal data that isn’t essential or necessary to provide the service. For most domain registrations, we don’t require the registrant to provide their phone number, but by collecting this piece of data we are able to provide a backup verification method. 

The data is required by a third party, with whom we do not yet have a GDPR-compliant contract. If we don’t have a GDPR-compliant contract with this particular registry, we would have to request consent from the data subject to process and share this extra piece of personal data before completing the registration. 

Keywords: [“data”,”Whois”,”domain”]


GDPR is one of the most prominent regulatory changes coming up in 2018. Companies that breach the GDPR legislation will receive a fine of €20 million of 4% of annual turnover, whichever is higher. Businesses and other organisations will be required by law to prove their employees have received communication about the GDPR and that they understand what it means for them and the organisation they work for. As a function, we also need to be aware of the information we hold on our employees and ensure that we are complying with the new legislation too. Here are some key things to consider when preparing for the GDPR:. 

Find out who is overseeing the GDPR programme/process in your organisation and ask to join the project team, if you’re not already part of it. It’s important internal communication help to guide the strategy from the outset as cutting through the noise and ensuring all employees are aware of the changes will be a legal requirement. Start communicating regularly with your employees now to help them understand what the legislation means and what they are required to do around recognising and protecting information. The GDPR may affect how you manage internal communication. Remember, this information might be stored locally in paper, GDPR is not only about digital records. 

Internal communication need to understand the impact those changes might have on employees and share appropriate, targeted communication about policy changes, training on the new legislation etc. Now is the time to understand how they are being used and ensure employees understand how these channels are impacted by the GDPR and what their responsibility is to keep information secure. We strongly recommend that internal communicators start preparing for GDPR now. 

Keywords: [“GDPR”,”employees”,”information”]

GDPR Support

GDPR compliance is a worry for many businesses based in the EU. This free extension supports Cookie Compliance and Customer Data Anonymisation. The ZERO-1 GDPR Support module for Magento 1 adds some key features to aid your support in meeting the requirements set out in the new General Data Protection Regulation legislation which comes into effect throughout the EU on 25 May 2018. Key requirements under the new legislation include the removal of customer data on request. Magento Core code does not currently facilitate this therefore all sites without this extension will not be adhering to legal requirements, given Magento can store customer cart data and customer order data for failed orders. 

Both these should not be retained by Magento under new laws. The ‘Express Consent’ law also requires that you refrain from setting ALL non-essential cookies from operating UNTIL express consent has been granted. Features: Cookie Notification Popup requesting ‘express consent’ from your website visitors upon entering your website. Delete Customer & Anonymise Data from Admin or Front-end – Although legally a business is permitted to retain customer information if the customer has purchased from you, Magento does have functionality to record sales data even if the order has not technically resulted in a completed sale. This extension allows you to fully anonymise customer data from Customer, Sales, Quotes tables so that you can feel assured that you have met your GDPR obligations. 

ZERO-1 have also partnered up with a law firm specialising in supporting the other requirements which must be met. These include onsite documentation such as Privacy, Terms & Conditions and Cookie Policy. This extension requires a basic understanding of Google Tag Manager. 

Keywords: [“Customer”,”Data”,”Magento”]

Leave a Reply

Your email address will not be published. Required fields are marked *