<html><head></head><body>Hi,<div class=""><br class=""/></div><div class="">There is more than one type of review involved in decisions to disclose registration data to a third-party. The review Franck refers to reads to me like a review that takes place as part of the audit function after disclosure has been granted. That is clearly not what Milton was referring to at all.</div><div class=""><br class=""/></div><div class="">As several members of this Team have repeatedly pointed out, in cases where the legal basis for disclosure is GDPR Article 6.1.f, a balancing test needs to be conducted in order to ensure that the legitimate interests of the third party or the data Controller are not outweighed by the personal rights and freedoms of the data subject/registrant. We seem to be ignoring this legal obligation, or are proceeding to work on policy recommendations allowing automation of decisions to disclose registration data with the hope/expectation that we will receive some kind of legal advice that effectively says, <i class="">“sure, there’s a legal obligation to conduct a balancing test, but here’s a loophole ICANN can exploit in favor of third-party interests over those of the data subjects’, which will protect ICANN and Contracted Parties from liability”</i>.</div><div class=""><br class=""/></div><div class="">This has unfortunately been the general theme of our work since Phase 2 began; how to chip away, piece by piece, as many rights afforded by law to data subjects to further the interests of disclosure requestors. If after all these months, the NCSG’s discomfort with this is still insufficiently clear, we are happy to explain them as many times as it takes to change that.</div><div class=""><br class=""/></div><div class="">So when Milton said “any accredited user to get personal data without reviews”, this was a pretty well-grounded assertion. Sure, reviews will be done after-the-fact during audits, but no meaningful balancing test (review) will be conducted as part of the process to decide wether to grant disclosure, or not. This will effectively result in requests for disclosure by accredited SSAD users to always be granted, assuming they tick all the right pre-populated boxes in the request…, which is basically what Milton said.</div><div class=""><br class=""/></div><div class="">Thanks.</div><div class=""><br class=""/></div><div class="">Amr</div><div class=""><br class=""/><div class=""><div><blockquote type="cite" class=""><div class="">On Feb 21, 2020, at 12:49 AM, Journoud, Franck <<a href="mailto:Franck_Journoud@motionpictures.org" class="">Franck_Journoud@motionpictures.org</a>> wrote:</div><br class="Apple-interchange-newline"/><div class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: TrebuchetMS; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">Milton, I do agree that it’s not sufficiently clear what is meant by “centralization” in the blog post.<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">However, I think your assertion that centralization and automation allow “any accredited user to get personal data without reviews” is not well grounded:<o:p class=""></o:p></span></div><ul type="disc" style="margin-bottom: 0in; margin-top: 0in;" class=""><li class="MsoListParagraph" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">centralization would make oversight of decision-making infinitely easier and thus more effective than ICANN Compliance having to chase thousands of CPs;<o:p class=""></o:p></span></li><li class="MsoListParagraph" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">automation would provide an authoritative and detailed view of each decision and of the criteria used: what are the algorithm’s inputs, how are they weighted/organized, what’s the decision-tree, etc.;<o:p class=""></o:p></span></li><li class="MsoListParagraph" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">it’s not “any accredited user” who would get access, but only those who (in themselves and in their requests) satisfy all the elements of the policy;<o:p class=""></o:p></span></li><li class="MsoListParagraph" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">so in summary we’re talking about more and better, not fewer and worse, reviews.<o:p class=""></o:p></span></li></ul><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">One thing is for sure: these divergent interpretations of a short blog post only reinforce in my mind the need for a fuller and more detailed account of the meeting!<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></span></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><i class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">-Franck<o:p class=""></o:p></span></i></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 18.65pt;" class=""><b class=""><span style="font-size: 11pt; font-family: Arial, sans-serif;" class="">Franck Journoud | VP, Tech Policy | MPA</span></b><b class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="Apple-converted-space"> </span>| E</span></b><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="Apple-converted-space"> </span><a href="mailto:franck_journoud@motionpictures.org" style="color: purple; text-decoration: underline;" class=""><span style="color: windowtext;" class="">franck_journoud@motionpictures.org</span></a><span class="Apple-converted-space"> </span>|<span class="Apple-converted-space"> </span><b class="">O<span class="Apple-converted-space"> </span></b>(202) 378-9127<b class=""><span class="Apple-converted-space"> </span>| M<span class="Apple-converted-space"> </span></b>(202) 285-7322</span><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""></o:p></span></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></span></div><div class=""><div style="border-style: solid none none; border-top-width: 1pt; border-top-color: rgb(225, 225, 225); padding: 3pt 0in 0in;" class=""><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><b class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">From:</span></b><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="Apple-converted-space"> </span>Gnso-epdp-team <<a href="mailto:gnso-epdp-team-bounces@icann.org" style="color: purple; text-decoration: underline;" class="">gnso-epdp-team-bounces@icann.org</a>><span class="Apple-converted-space"> </span><b class="">On Behalf Of<span class="Apple-converted-space"> </span></b>Mueller, Milton L<br class=""/><b class="">Sent:</b><span class="Apple-converted-space"> </span>Thursday, February 20, 2020 4:48 PM<br class=""/><b class="">To:</b><span class="Apple-converted-space"> </span><a href="mailto:gnso-epdp-team@icann.org" style="color: purple; text-decoration: underline;" class="">gnso-epdp-team@icann.org</a><br class=""/><b class="">Subject:</b><span class="Apple-converted-space"> </span>Re: [Gnso-epdp-team] ICANN Meets with Belgian Data Protection Authority<o:p class=""></o:p></span></div></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><o:p class=""> </o:p></div><div class=""><p class=""><b class=""><span style="font-family: veranda;" class="">WARNING – External Sender<span class="Apple-converted-space"> </span><o:p class=""></o:p></span></b></p><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 9pt; font-family: Helvetica, sans-serif;" class=""><o:p class=""> </o:p></span></div><div class="MsoNormal" align="center" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif; text-align: center;"><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class=""><hr size="3" width="100%" align="center" class=""/></span></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">Colleagues:<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">I really have to push back against Hadia’s interpretation of the ICANN blog post, and the blog post itself.<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">As others pointed out, the blog’s claim that “a centralized model” is better for security is just the writer’s opinion. The claim is seriously undermined by the fact that we do not know whether they were talking about centralization of requests, or centralization of disclosure, or both. In this respect, the discussion within EPDP, which makes a clear distinction between request and disclosure centralization, is a far more advanced than ICANN’s old UAM concept. So merely on the basis of its ambiguity, this alleged principle is meaningless. And from a cybersecurity standpoint, it should be obvious that centralization/automation of disclosure is very bad for the privacy of the data subject, because it allows any accredited user to get private data without any reviews. I have a hard time believing that any DPA would sanction something like that if they were presented with a clear explanation of it.<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">As for the second alleged principle, it is a worthless tautology. In essence, it says: Automated decision making is allowed under GDPR as long as the GDPR allows it. Well, thank you very much. <o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">The problem is that automated disclosure decisions does not permit one to see whether the request actually conforms to the criteria that would authorize disclosure. Automation thus massively increases the risk that disclosures that are not compliant will be made.<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">This whole episode is just another demonstration of why ICANN org’s insistence on mediating between us and the DPAs is unhelpful; I wish they would stop. No issue we face has been clarified; no part of our work has been advanced by this exchange. We just debate different interpretations of these meetings based on different policy preferences. Worst of all, we do not know how ICANN org presents issues to the DPAs in these private meetings.<span class="Apple-converted-space"> </span><o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">Can we call a moratorium on these unwanted and unneeded parallel interventions?<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">And if not, can we at least teach Goran and his staff to say “SSAD” instead of “UAM,” so that we are sure we are talking about the same thing? It’s only one more letter, it shouldn’t be hard.<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">Dr. Milton L Mueller<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">School of Public Policy<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">Georgia Institute of Technology<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><span id="cid:image001.jpg@01D5E815.27EB58B0"><image001.jpg></span><o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div class=""><div style="border-style: solid none none; border-top-width: 1pt; border-top-color: rgb(225, 225, 225); padding: 3pt 0in 0in;" class=""><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><b class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">From:</span></b><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="Apple-converted-space"> </span>Gnso-epdp-team <<a href="mailto:gnso-epdp-team-bounces@icann.org" style="color: purple; text-decoration: underline;" class="">gnso-epdp-team-bounces@icann.org</a>><span class="Apple-converted-space"> </span><b class="">On Behalf Of<span class="Apple-converted-space"> </span></b>Hadia Abdelsalam Mokhtar EL miniawi<br class=""/><b class="">Sent:</b><span class="Apple-converted-space"> </span>Thursday, February 20, 2020 11:00 AM<br class=""/><b class="">To:</b><span class="Apple-converted-space"> </span>Journoud, Franck <<a href="mailto:Franck_Journoud@motionpictures.org" style="color: purple; text-decoration: underline;" class="">Franck_Journoud@motionpictures.org</a>>; Johan Helsingius <<a href="mailto:julf@julf.com" style="color: purple; text-decoration: underline;" class="">julf@julf.com</a>>;<span class="Apple-converted-space"> </span><a href="mailto:gnso-epdp-team@icann.org" style="color: purple; text-decoration: underline;" class="">gnso-epdp-team@icann.org</a><br class=""/><b class="">Subject:</b><span class="Apple-converted-space"> </span>Re: [Gnso-epdp-team] ICANN Meets with Belgian Data Protection Authority<o:p class=""></o:p></span></div></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">Dear All,<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">As I have said on the call today I also found the blog useful, it highlighted two main principles. First, a centralized model is better in terms of security and in relation to the data subjects and second, an algorithm that automates decision making is allowed under GDPR as long as it can demonstrate the decision was taken in accordance with the criteria set by GDPR. We keep thinking about the liability, but given the limited time we have, we need to focus on having a workable, efficient system that is compliant with GDPR. <o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">Best<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">Hadia<o:p class=""></o:p></span></div><div class=""><div style="border-style: solid none none; border-top-width: 1pt; border-top-color: rgb(181, 196, 223); padding: 3pt 0in 0in;" class=""><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><b class=""><span style="font-size: 10pt; font-family: Tahoma, sans-serif;" class="">From:</span></b><span style="font-size: 10pt; font-family: Tahoma, sans-serif;" class=""><span class="Apple-converted-space"> </span>Gnso-epdp-team [<a href="mailto:gnso-epdp-team-bounces@icann.org" style="color: purple; text-decoration: underline;" class="">mailto:gnso-epdp-team-bounces@icann.org</a>]<span class="Apple-converted-space"> </span><b class="">On Behalf Of<span class="Apple-converted-space"> </span></b>Journoud, Franck<br class=""/><b class="">Sent:</b><span class="Apple-converted-space"> </span>Thursday, February 20, 2020 4:55 PM<br class=""/><b class="">To:</b><span class="Apple-converted-space"> </span>Johan Helsingius;<span class="Apple-converted-space"> </span><a href="mailto:gnso-epdp-team@icann.org" style="color: purple; text-decoration: underline;" class="">gnso-epdp-team@icann.org</a><br class=""/><b class="">Subject:</b><span class="Apple-converted-space"> </span>Re: [Gnso-epdp-team] ICANN Meets with Belgian Data Protection Authority<o:p class=""></o:p></span></div></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><o:p class=""> </o:p></div><p class="MsoNormal" style="margin: 0in 0in 12pt; font-size: 12pt; font-family: "Times New Roman", serif;">Dear Janis, ICANN org liaisons and EC EPDP members,<br class=""/><br class=""/>I'd like to reiterate the point that I made on the EPDP call today. I have found the blog post very helpful and sincerely thank Göran for writing it - and yet it is insufficient. I appreciate that this was a meeting rather than formal legal guidance, but it'd still be helpful if all 'our' attendees (ICANN org staff, Janis, EC) could pool their notes and analysis to produce as detailed as possible an account of what the Belgian DPA reps said. This should be followed by these attendees attending an EPDP call so that we can ask follow-up questions. Surely we can get more our of that extremely important interaction than informative and useful, but short couple of substantive paragraphs.<br class=""/><br class=""/>-Franck<br class=""/><br class=""/>Franck Journoud | VP, Tech Policy | MPA | E<span class="Apple-converted-space"> </span><a href="mailto:franck_journoud@motionpictures.org" style="color: purple; text-decoration: underline;" class="">franck_journoud@motionpictures.org</a><span class="Apple-converted-space"> </span>| O (202) 378-9127 | M (202) 285-7322<br class=""/><br class=""/>-----Original Message-----<br class=""/>From: Gnso-epdp-team <<a href="mailto:gnso-epdp-team-bounces@icann.org" style="color: purple; text-decoration: underline;" class="">gnso-epdp-team-bounces@icann.org</a>> On Behalf Of Johan Helsingius<br class=""/>Sent: Wednesday, February 19, 2020 4:49 PM<br class=""/>To:<span class="Apple-converted-space"> </span><a href="mailto:gnso-epdp-team@icann.org" style="color: purple; text-decoration: underline;" class="">gnso-epdp-team@icann.org</a><br class=""/>Subject: [Gnso-epdp-team] ICANN Meets with Belgian Data Protection Authority<br class=""/><br class=""/>WARNING - External Sender<br class=""/><br class=""/><a href="https://www.icann.org/news/blog/icann-meets-with-belgian-data-protection-authority" target="_blank" style="color: purple; text-decoration: underline;" class="">https://www.icann.org/news/blog/icann-meets-with-belgian-data-protection-authority</a><br class=""/>_______________________________________________<br class=""/>Gnso-epdp-team mailing list<br class=""/><a href="mailto:Gnso-epdp-team@icann.org" style="color: purple; text-decoration: underline;" class="">Gnso-epdp-team@icann.org</a><br class=""/><a href="https://mm.icann.org/mailman/listinfo/gnso-epdp-team" target="_blank" style="color: purple; text-decoration: underline;" class="">https://mm.icann.org/mailman/listinfo/gnso-epdp-team</a><br class=""/>_______________________________________________<br class=""/>By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://www.icann.org/privacy/policy" style="color: purple; text-decoration: underline;" class="">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" style="color: purple; text-decoration: underline;" class="">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.<o:p class=""></o:p></p><p class=""><span style="font-size: 8pt; font-family: Verdana, sans-serif; color: rgb(102, 102, 102);" class="">CONFIDENTIALITY NOTICE: This e-mail communication and any attachments may contain confidential and privileged information for the use of the designated recipients named above. If you are not the intended recipient, you are hereby notified that you have received this communication in error and that any review, disclosure, dissemination, distribution or copying of it or its contents is strictly prohibited. If you have received this communication in error, please notify the sender by return e-mail and delete and/or destroy all copies of this communication and any attachments.</span></p></div></div></blockquote></div><br class=""/></div></div></body></html>