<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
I think ICANN will struggle to find a DPO who will work under the assertion that the disclosure of registration data is an activity covered under legitimate interest.
<div class="">Has the EPDP received external legal advise on any of these?<br class="">
<div><br class="">
<blockquote type="cite" class="">
<div class="">On 3 Feb 2019, at 16:56, Ayden Férdeline <<a href="mailto:icann@ferdeline.com" class="">icann@ferdeline.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">Hi James,<br class="">
</div>
<div class=""><br class="">
</div>
<div class="">For purpose 2, the EPDP team has completed four lawfulness of processing tests, one for each of the following activities:<br class="">
</div>
<ul class="">
<li class="">collection of registration data<br class="">
</li><li class="">transfer of registration data from registrar to registry<br class="">
</li><li class="">disclosure of non-public registration data to third parties<br class="">
</li><li class="">retention of registration data by registrar<br class="">
</li></ul>
<div class="">
<div class="">In the case of the disclosure of registration data to third parties, we are not relying on consent, therefore Article 7 does not apply. We have assessed this as being a 6(1)(f) (legitimate interest) processing activity. However, in recognition
of the fact that such a disclosure is not technically necessary to perform the registration contract between the registrant and registrar, the contracted party would still need to perform the requisite balancing test to ensure the third party's legitimate
interests override the fundamental rights and freedoms of the data subject, before registration data is disclosed.<br class="">
</div>
<div class=""><br class="">
</div>
<div class="">Best wishes,<br class="">
</div>
<div class=""><br class="">
</div>
</div>
<div class="protonmail_signature_block">
<div class="protonmail_signature_block-user">
<div class="">Ayden <br class="">
</div>
</div>
<div class="protonmail_signature_block-proton protonmail_signature_block-empty"><br class="">
</div>
</div>
<div class=""><br class="">
</div>
<div class="">‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐<br class="">
</div>
<div class="">On Sunday, February 3, 2019 4:08 AM, James Gannon <<a href="mailto:james@CYBERINVASION.NET" class="">james@CYBERINVASION.NET</a>> wrote:<br class="">
</div>
<div class=""><br class="">
</div>
<blockquote type="cite" class="protonmail_quote">
<div class="">Would love to know how purpose 2 is defined on a legal basis and also how it complies with Art 7 section 4.<br class="">
</div>
<div class=""><br class="">
</div>
<div class="">
<div class=""><br class="">
</div>
<blockquote type="cite" class="">
<div class="">On 3 Feb 2019, at 09:45, farzaneh badii <<a href="mailto:farzaneh.badii@gmail.com" class="">farzaneh.badii@gmail.com</a>> wrote:<br class="">
</div>
<div class=""><br class="">
</div>
<div class="">
<div dir="ltr" class="">
<div style="font-family:verdana,sans-serif" class="">Our update on EPDP work is overdue, so I thought I write my thoughts and report a bit on the developments, and others from EPDP team can chime in if they think I got something wrong. <br class="">
</div>
<div style="font-family:verdana,sans-serif" class=""><br class="">
</div>
<div style="font-family:verdana,sans-serif" class=""><b class="">where we are at:</b><br class="">
</div>
<div style="font-family:verdana,sans-serif" class="">we are now finalizing the preliminary report and need to come to a consensus quickly and send the report off to the council for approval. So pressure is high. We have to come up with an interim policy plan
to cover the gap between implementation and approval of the recs. <br class="">
</div>
<div style="font-family:verdana,sans-serif" class=""><br class="">
</div>
<div style="font-family:verdana,sans-serif" class=""><b class="">Our principles: </b><br class="">
</div>
<div style="font-family:verdana,sans-serif" class="">- Maximum data protection for domain name registrants globally<br class="">
</div>
<div style="font-family:verdana,sans-serif" class="">- Accountable disclosure and accountable receipt of domain name registrants personal info<br class="">
</div>
<div style="font-family:verdana,sans-serif" class="">- Side with providing data protection when in doubt whether GDPR applies<br class="">
</div>
<div style="font-family:verdana,sans-serif" class="">- Keep ICANN's mission limited <br class="">
</div>
<div style="font-family:verdana,sans-serif" class=""><br class="">
</div>
<div style="font-family:verdana,sans-serif" class="">I have attached a PDF with markation of what we have problems with or doubts for the moment. I am still working on it but it's attached. <br class="">
</div>
<div style="font-family:verdana,sans-serif" class=""><br class="">
</div>
<div style="font-family:verdana,sans-serif" class=""> <b class="">Purposes for domain name registrants data processing -</b><br class="">
</div>
<div style="font-family:verdana,sans-serif" class=""><br class="">
</div>
<div style="font-family:verdana,sans-serif" class=""><br class="">
</div>
<div style="font-family:verdana,sans-serif" class="">
<ol class="">
<li class="">Purpose 1. To establish registrants rights (generally is a good purpose, in favor of registrants). Note that some would like to add the word obligation of domain name registrants to this purpose which we have resisted and argued that if they want
to do that they need a standalone purpose. <br class="">
</li><li class="">Contributing to the maintenance of SSR through disclosure to lawful requests: we initially opposed this purpose because it's not a purpose for data processing. you don't collect data to disclose it later to third parties. Now the purpose has canged
to: "Contributing to the maintenance of the security, stability, and <span style="color:rgb(182, 8, 46)" class="">
<span style="font-family:Helvetica" class=""><span style="font-size:9px" class="">resiliency of the</span></span></span>Domain Name System in accordance with ICANN’s mission through enabling responses to lawful data disclosure requests." This is not a bad compromise.
But the footnotes are not very helpful. The first footnote says that this purpose does not preclude IP based requests. Though this was a compromise makes me very worried. We have always said that SSR does not include IP issues and this footnote can make it
easier to include IP in SSR in the future. My solution would be to re-word this and say: This purpose does not preclude lawful disclosure for non-SSR issues i.e. trademark infringement (in accordance with ICANN bylaws). The details of the disclosure will be
discussed in phase two. <br class="">
</li></ol>
<div class="">What we have achieved so far (relatively):<br class="">
</div>
<div class="">1. there might be no differentiation between legal and natural persons <br class="">
</div>
<div class="">2.Tech admin contact might become optional <br class="">
</div>
<div class="">3. There might be no differentiation in treating domain name registrants based on their geographical location<br class="">
</div>
<div class="">4. Thin registries might not have to implement thick registries policy (unsure about that, please correct me if I am wrong)<br class="">
</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
</div>
<div style="font-family:verdana,sans-serif" class=""><br class="">
</div>
<div style="font-family:verdana,sans-serif" class=""><br class="">
</div>
<div style="font-family:verdana,sans-serif" class=""><br class="">
</div>
<div class="">
<div dir="ltr" data-smartmail="gmail_signature" class="">
<div dir="ltr" class="">
<div class=""><span style="font-family:verdana, sans-serif" class="">Farzaneh</span><br class="">
</div>
</div>
</div>
</div>
</div>
<div class=""><span class=""><EPDP Team Draft Final Report - Annotated.pdf></span><br class="">
</div>
</div>
</blockquote>
</div>
</blockquote>
<div class=""><br class="">
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</body>
</html>