Changes

===GDPR and Registration Data Complaints===

===GDPR and Registration Data Complaints===

As the EU's [[General Data Protection Regulation]] came into effect, Contractual Compliance shifted its focus around and response to complaints related to inaccuracies or misrepresentations in registration data.<ref name="gdpr">[https://www.icann.org/resources/pages/registration-data-accuracy-obligations-gdpr-2021-06-14-en ICANN.org - Registration Data Accuracy Obligations Before and After GDPR], June 14, 2021</ref> The department noted that the shifts in registrar and registry policies resulting from the implementation of GDPR resulted in changes in the number and relevance of complaints:

As the EU's [[General Data Protection Regulation]] came into effect, Contractual Compliance shifted its focus around and response to complaints related to inaccuracies or misrepresentations in registration data.<ref name="gdpr">[https://www.icann.org/resources/pages/registration-data-accuracy-obligations-gdpr-2021-06-14-en ICANN.org - Registration Data Accuracy Obligations Before and After GDPR], June 14, 2021</ref> The department noted that the shifts in registrar and registry policies resulting from the implementation of GDPR resulted in changes in the number and relevance of complaints:

<blockquote>The decrease in complaint volume from a monthly average of 2,774 pre-GDPR to 1,003 post-GDPR resulted from a significant reduction in external complaints and from ICANN org no longer releasing WHOIS ARS reports beginning in June 2018.

<blockquote>The decrease in complaint volume from a monthly average of 2,774 pre-GDPR to 1,003 post-GDPR resulted from a significant reduction in external complaints and from ICANN org no longer releasing WHOIS ARS reports beginning in June 2018.<br />

In addition, the percentage of complaints received that lacked evidence of noncompliance or fell outside of ICANN org's contractual scope increased. For example, many complainants believe that the registration data is "missing" from the public Registration Data Directory Service (or WHOIS service), privacy or proxy service data are redactions, or all non-European data should be displayed. While Contractual Compliance efforts to educate complainants on contractual requirements increased, the number of actual investigations into registrars' compliance with registration data accuracy obligations decreased.<ref name="gdpr" /></blockquote>

In addition, the percentage of complaints received that lacked evidence of noncompliance or fell outside of ICANN org's contractual scope increased. For example, many complainants believe that the registration data is "missing" from the public Registration Data Directory Service (or WHOIS service), privacy or proxy service data are redactions, or all non-European data should be displayed. While Contractual Compliance efforts to educate complainants on contractual requirements increased, the number of actual investigations into registrars' compliance with registration data accuracy obligations decreased.<ref name="gdpr" /></blockquote>