The European Union's General Data Protection Regulation (GDPR) lays out a new set of rules for how the personal data of people living within the European Union should be handled. That being said, it embodies some great principles and concepts that we believe in here at Enom, and we want to pass these protections and rights on to all of our customers, regardless of where they happen to live.
- The purpose of the GDPR
- GDPR when not in the European union
- Effects of GDPR
- The right to erasure
- Personal data
- Understanding consent for your personal data
- Obtaining your consent
- Enom process via contract
- Enom process via consent
- Asynchronous vs synchronous
- Data use consent settings page
- Consent options
- Withdrawing consent and refunds
- Order in which services are presented on the data us consent settings page
- Timeout consent request
- Consent request triggers
- Consent and verification emails
- Whois Information
- WHOIS changes
- Public WHOIS details
- Gated Whois vs ID Protect (Whois privacy)
- Displayed data in gated WHOIS
- Non-EU domain registrants
- Gated Whois for privacy-protected domains
- WHOIS information for privacy-protected domains
- ICANN policy
- Effects on incoming transfers
- Tiered Access Directory (gated Whois)
The purpose of the GDPR
The GDPR helps protect privacy in the digital age. The European Union views personal data protection as nothing less than a fundamental human right. Although other existing privacy laws are already in effect, the GDPR is different in its scope of applicability because significant fines may be levied for non-compliance.
The GDPR can be broken down into three main concepts:
| Consent and control | Your personal information belongs to you. Only you can decide where it gets used. To work with any of your data, we have to let you know what we need your information for and ask you for your consent to use it. We are obligated only to collect the minimum amount of information we need to get the job done. We can't use the information we've gathered for something else without asking you if that's ok. |
| Transparency | Transparency means that in the event of a security breach where your personal data may have been exposed, we have to let you know as soon as possible that it's happened and tell you what happened, what we're doing to fix it and what you should do protect yourself. This type of information empowers each person to respond in the way they think is best in each circumstance to protect their privacy. |
| The right to be forgotten | The right to be forgotten allows you to revoke your consent to access your personal information. Enom will have to erase all individual records, giving them a fresh start. This requirement is not without consequences or limitations. Some services can't be provided without personal information, and sometimes personal information must be kept for public interest or relating to legal claims. This right to erasure applies only to data that's used because we have consent and does not apply to data that's used because it's required as part of a contract. |
GDPR when not in the European union
While the rules outlined in GDPR apply only to EU-local individuals, changes to how data is collected and handled will happen globally as companies modify their existing practices to ensure they comply with these new regulations. Enom believes in the principles that the GDPR upholds, and we, along with other key players in our industry, feel that extending the benefits of the GDPR to registrants worldwide is simply the right thing to do.
We'll be empowering our clients to understand what information we hold and how it's used, to give consent to us for that use, and to request data erasure in cases where consent cannot be provided.
Effects of GDPR
These data privacy protections touch almost every domain onboarding process and lifecycle aspect. We're keeping two things in mind: our need to operate within the bounds of legal requirements and our commitment to keeping domain purchase and management as straightforward, simple, and instantaneous as possible for the end-user.
Enom does not share personal data beyond what's needed to provide your ordered service. We've never sold our clients' personal information, and we certainly aren't going to start now.
GDPR and my Enom registration agreement
One of the main ways we inform our clients about how their data is being used is through our contracts and end-user service agreements, which have been updated as part of our GDPR implementation efforts.
The right to erasure
Article 17 of the GDPR outlines the data subject's right to erasure, also known as the right to be forgotten. It gives each person the right to request that a controller like Enom erase their personal data. It also requires us to comply with any such request as long as one of six specific legal grounds applies. On top of this, it states that in cases where the controller has made personal data public, they must reach out to any other controller who is processing the data and inform them about the request for erasure so that the appropriate steps can be taken. Finally, Article 17 lays out several exceptions where the right to erasure does not apply. These include instances when the processing of data is necessary for exercising the right of freedom of expression and information, for compliance with a legal obligation, or the establishment, exercise or defence of legal claims.
Personal data
Personal data is any information related to an identified or identifiable living individual. Different pieces of information collected together can lead to the identification of a particular person and constitute personal data. Personal data that has been de-identified, encrypted or pseudonymized but can be used to re-identify a person remains personal data and falls within the scope of the law.
- Examples of personal data: Name, surname, address, email address, IP, personal ID, cookie ID; firstname.lastname@company.com
- These are not considered personal data: info@company.com, company name, or legal entities.
Data processed as part of fulfilling our service contract will be kept for the lifetime of the service, plus up to ten years after the service's termination.
Enom will hold any data that we process under the legal basis of consent for the same period as the contract-based data unless that consent is withdrawn, in which case the erasure process begins at the time of withdrawal of consent and may take up to 60 days to complete.
Note: for asynchronous services, Enom will direct you to cancel services. Upon cancelling the service, your choice to withdraw consent will take effect.
Understanding consent for your personal data
Obtaining your consent
We will send every domain owner a consent request as part of the domain registration, transfer, or owner update process unless we already have consent on file for that consent group. In the consent request, we will disclose all the uses of your personal data that are required by a contract for us to provide the requested domain service. We will also request consent from you for those data uses where our legal basis is your consent. In cases where we already have consent on file, we will process the new registration based on those existing consent choices.
Once you've provided consent, you will be given access to a consent management page where you can review and modify your consent choices on an ongoing basis or revoke your consent at any time.
Enom process via contract
Any data that must be processed to register a domain, or provide any other type of service, will be covered under a contract.
- First name
- Last name
- Organization (if provided)
- Email address
- Country
Certain domain registries require additional information to complete domain registrations, and in these cases, we will include a point about processing those additional pieces of registrant data in our contract.
Enom process via consent
We will request consent from someone when:
- We give the option of processing any piece of personal data that isn't essential to provide the service. For example, for most domain registrations, we don't require the owner to provide their phone number. Still, 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. For example, a registry might require that the domain owner's postal address be on file to complete a domain registration. If we don't have a GDPR-compliant contract with this particular registry, we would have to request consent from you to process and share this extra piece of personal data before completing the registration.
Asynchronous vs synchronous
The data elements that Enom or the GDPR-compliant provider requires are collected and processed under the legal basis of a contract. However, for some TLDs and services, the provider requests additional pieces of data for which there is no legal, contractual basis to process. When this is the case, we will ask you for consent to share these additional pieces of data with the provider.
In most cases, even if you, the registrant, should withhold or fail to provide consent, Enom can still immediately register the domain by sending the registry a combination of the contractual data and placeholders for any data elements that can only be processed with consent. We refer to such services as "synchronous"—they can be registered immediately, without using additional personal data beyond what is covered in the contract.
For some TLDs, however, the registry will not accept placeholder data. Because we don't have assurance from the registry that the data will only be used in ways that conform with modern data privacy regulations such as the GDPR, Enom cannot in good conscience provide the actual data to the registry without your consent. We refer to these types of services as "asynchronous" — because the service cannot be provided without sharing certain pieces of the registrant's personal data with the service provider, and there is no GDPR-compliant contract to protect the data, we need the registrant's permission to share it before we proceed. This permission must be provided in the form of affirmative consent.
Data use consent settings page
Each service or product offered through Enom falls into a particular consent group within our system. Once the consent preference is logged for a group, that choice is applied to any future purchases of products within that same group.
For two (or more) products to fall within the same consent group, they must be:
- Offered through the same service provider
- Contractually require the same data elements
- And must request the same consent-based data elements
A registry might operate multiple TLDs, and each contractually requires the owner's name, email, and country, but also request consent to process the owner's phone number. These TLDs would fall into the same consent group, and once you set your consent preferences for one of these TLDs, your choice would be applied to all future purchases of other TLDs within this group. This means that no future consent request emails would be sent to you for purchases within this group. However, if this same registry offers another TLD for which they request consent to process the owner's postal address, in addition to their phone number, you would receive a consent request upon purchasing this TLD, as it would fall into a distinct consent group.
Pre-consented domains
For asynchronous domains and services which were active before the GDPR came into full effect on May 25, 2018, the consent status is set to "yes-consent" by default. This is because you were considered to have consented to the data processing by purchasing the service, as the GDPR's enhanced data protection requirements were not in effect at the time of purchase.
If you wish to revoke consent for a product which currently reflects a "yes-consent" status, you must uncheck the box and submit, at which point you will be prompted to cancel the service.
Consent options
If it is a synchronous service, where we can substitute placeholder data for any consent-based personal data, we will gladly do so, and you won't experience any change to your product or service.
There are some products where this substitution is not an option; these are what we call asynchronous, as the registry would reject the placeholder data. In these cases, we will inform you of this and explain that the only way to withdraw consent is to cancel that service. This is because, while Enom doesn't require this consent-based data, it is required by the registry or service provider. That registry or provider has not offered a GDPR-compliant data erasure request process. While ideally, we would replace this consent-based data with placeholder data, we are not permitted to do so by the registry or provider. So the service would need to be cancelled for the withdrawal of consent to have any real effect.
Withdrawing consent and refunds
Enom does not provide a refund in the cases where you decide to cancel an active service because you wish to revoke consent.
Enom will refund any cancelled, pending orders if you choose to withhold consent. Consent requests remain pending for ten days, after which the order will default to a non-consented status, and the pending order is cancelled.
Order in which services are presented on the data use consent settings page
The order in which services are shown on the Data use consent settings page is prioritized so that any actionable or important items are seen first. This means services will be listed in the following order as they apply to you:
- New, asynchronous products still require consent.
- New, synchronous products still require consent.
- Older, asynchronous products where the consent choice has been made.
- Older, synchronous products where the consent choice has been made.
Timeout consent requests
Though this only poses an issue for registrants of asynchronous services. Ten days following the initial consent request, your consent status will default to "non-consent" if we haven't received a response, and the order will be placed on hold and ultimately cancelled.
Synchronous services will be unaffected by this, as Enom will continue to use placeholders for any data elements that we process until consent is given. Pending orders for asynchronous services, however, will be cancelled at this 10-day mark if we haven't yet received a response from the registrant.
Consent request triggers
The initial consent request can be triggered by the domain registration, update, or transfer. When you, the registrant, set your consent preferences, your choices will be logged and applied to any future purchases of products within the same consent group. However, purchase a service for which the provider requests additional pieces of data beyond those for which you have already granted or withheld consent to process. You may receive another consent request.
The consent request will be sent to Enom's registrant email address on file for the domain or service.
Consent and verification emails
The consent requests will only be sent to the registrant's email address. Sending a consent request to an email address other than the owner would not be considered GDPR compliant. Enom will no longer process admin, billing, or technical contact information for legal reasons, except in cases where the registry specifically requires these contact points. Whenever possible, we will replace these fields with placeholder data.
At this time, the consent request email and Whois verification email will be sent to you as two separate requests.
Whois Information
Whois change
Enom implemented a gated Whois system. Under this system, registered domain registrant, admin, and technical contact information will no longer be visible in the public Whois database.
Whois data for registered domains will only be accessible to legitimate and accredited third parties, such as law enforcement, members of the security community, and intellectual property lawyers, through the gated Whois. This Whois data will be limited to those personal data elements that we have obtained permission to process, either via contract or via consent of the data subject.
Registrant information—name, organization, address, phone number, and email—will be considered personal data that can no longer be published in the public Whois. However, we feel authenticated access to this information, in a specific and limited manner, must be provided to those with legitimate reasons to request it. A gated Whois system will allow for this while also ensuring that private information remains guarded against the general public.
You can view a snapshot of what these changes will look like, or, for more context, you can read our full Whois Changes post. We've also curated a list of resources that provide helpful context and insight into how other key players are thinking about the future of Whois.
Public WHOIS details
Under the GDPR, personal data may be collected and processed only when there is a legal reason to do so. This means that the public Whois system as it exists today is incompatible with the data privacy principles that the GDPR affirms.
The technical data (the top section of the current Whois output) will appear in the public-facing lookup.
Gated Whois vs ID Protect (Whois privacy)
The gated Whois is a portal where accredited third parties can access Whois information, and the output available here includes personal data hidden from the public Whois. However, the Whois output for domains with ID protect (Whois Privacy) will remain the same as it was prior to May 2018, both in the public Whois and in the gated Whois. This means that contact privacy details, including a contact privacy email, will be displayed for domains with ID protect (Whois Privacy) in the gated Whois. Check out our Whois changes blog post for a helpful visual snapshot of the difference.
Displayed data in gated WHOIS
Registrant contact data which is held based on contract, and data for which we have consent, will be displayed in the gated Whois — unless the domain is privacy-protected. If the domain has ID protect, the privacy masking data will be displayed both publicly and within the gated Whois.
Non-EU domain registrants
We are applying all Whois-related changes platform-wide, meaning all registrants will receive the same data protection regardless of citizenship or location.
Gated Whois for privacy-protected domains
Access to the gated Whois will only reveal information which was public before May 25, 2018. It will not disclose the Whois information for privacy-protected domains. The Whois output for privacy-protected domains will be the same in both the public and gated Whois. We will continue to require a court order or other legal documentation for access to this information, as we do today.
Whois information for privacy-protected domains
Whois privacy will continue to remain a valuable service to registrants worldwide. Even when the public Whois "goes dark," there will still be a gated Whois, where registrant data will be made available to parties with a legitimate interest. So, while the audience for registrant data will no longer be the entire public, it will still be sizable. This is where Whois privacy comes in—if privacy is active on a domain, the personal data in the registration record will remain protected from those with access to the gated Whois. 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. In addition, the personal data associated with a domain protected by Whois privacy will not be shared with registries.
Here's a visual guide that illustrates these differences in Whois output. Our Whois impacts blog post also provides a more in-depth answer to this question.
ICANN policy
We will continue to comply with ICANN policy to the greatest extent possible, as we have always done. However, until ICANN policy has been updated in response to the GDPR and other similar worldwide data privacy legislation, we will be faced with many instances where the requirements that ICANN lays out for its registrars conflict with our legal obligations. In these instances, we will follow the law first and comply with ICANN as best we can.
Effects on incoming transfers
We have made some minor updates to our inbound transfer process. We will now rely on the EPP code (also known as the transfer authorization code) provided by the owner as the form of authorization for inbound transfers rather than requiring an additional transfer approval step. Additionally, for each completed transfer, a registrant verification email will be sent to the owner's email address to verify the accuracy of domain contact information. Our outbound transfer process will not change.
Tiered access directory (gated Whois)
The Tiered access directory is Enom's gated version of the Whois directory. It allows accredited third parties, such as members of law enforcement, to view the contact data of domain registrants who use our platform.
Comments
0 comments
Please sign in to leave a comment.