<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Dear colleagues,</div><div class=""><br class=""></div><div class="">You might be interested to hear that the California passed new data protection legislation last week, the 2018 Consumer Privacy Act. For those interested, the International Association of Privacy Professionals (IAPP) has produced a comprehensive overview of the new law: <a href="https://iapp.org/news/a/analysis-the-california-consumer-privacy-act-of-2018/" class="">https://iapp.org/news/a/analysis-the-california-consumer-privacy-act-of-2018/</a> </div><div class=""><span class="md"><p class="">I found the following excerpt from their analysis particularly relevant to ICANN:</p></span></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><span class="md"><p class="">"Some companies implemented many of their new privacy
protection measures worldwide in the hopes of being able to avoid
having to make further jurisdiction-specific updates for a while. The
passage of the California Consumer Privacy Act has now raised the
question as to whether these measures will be sufficient to the extent
they reach California residents with their GDPR-related compliance
measures. Unfortunately, the answer is largely, ‘No.’ </p><p class=""><i class="">Global companies can and should try to address the requirements of
the California Consumer Privacy Act, EU GDPR and other privacy regimes simultaneously and holistically in the interest of efficiency</i>.” </p></span></div></blockquote><div class=""><div class="">The <a href="https://www.icann.org/resources/pages/governance/bylaws-en" class="">Human Rights Bylaw</a> (which will come into effect when the WS2 recommendations are approved, likely in Q4 of this year) states that ICANN should be guided by the core value of “respecting internationally recognized human rights as required by applicable law.” </div><div class=""><br class=""></div><div class="">The <a href="https://community.icann.org/display/WEIA/Documents?preview=/59641302/79437270/CCWG-Accountability-WS2-HumanRight-FinalReport-20171106%5B1%5D.pdf" class="">HR FoI</a> recognizes that the notion of applicable law “is a dynamic concept inasmuch as laws, regulations, etcetera, change over time.” However, based on the GDPR experience, it seems like waiting for rights-related laws to become applicable may not be the best strategy in the long run. </div><div class=""><br class=""></div><div class="">Once the bylaw comes into effect, ICANN org and each SO and AC will be required to develop policies and frameworks to take human rights into account and avoid human rights violations in policy-development and decision-making processes. Some have perceived this as an additional administrative burden, though it’s hard to contest the bylaw's relevance given the amount of time the community has spent discussing access, accreditation, EPDPs, and other topics spawned by GDPR, a piece of privacy — and therefore human rights-related — legislation.</div><div class=""><br class=""></div><div class="">I therefore see <b class="">strategic potential in developing new compliance mechanisms for the human rights bylaw.</b> Just as corporate human rights impact assessments serve to identify gaps and mitigate risks, multistakeholder ICANN HRIAs should be devised and incorporated to promote more holistic, efficient, and proactive self-governance.</div><div class=""><br class=""></div><div class="">Thoughts and comments are certainly welcome! And as a reminder, you can find a few resources on related work on the ICANN Human Rights website, here: <a href="https://icannhumanrights.net/documents/" class="">https://icannhumanrights.net/documents/</a> </div><div class=""><br class=""></div><div class=""><br class="webkit-block-placeholder"></div><div class="">Warm regards,</div><div class="">Collin</div><div class="">
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><div class=""><br class="Apple-interchange-newline">--</div>Collin Kurre<br class=""><div class="">ARTICLE 19</div></div><div class=""><br class=""></div></div><br class="Apple-interchange-newline" style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><br class="Apple-interchange-newline">
</div>
<br class=""></div></body></html>