Hi guys! I don’t know why I am receiving this mails but I am not sure if I should be getting them. Just bringing it to your attention. Cheers! León Enviado desde mi iPhone

El oct. 9, 2019, a la(s) 1:53 p. m., James M. Bladel <jbladel@godaddy.com> escribió:

 Not sure about everyone, but I plan to read (after lunch, of course) and maybe tee up some question for Amr during our call tomorrow.

J.

------------- James Bladel GoDaddy

From: Gnso-epdp-team <gnso-epdp-team-bounces@icann.org> on behalf of Margie Milam <margiemilam@fb.com> Date: Wednesday, October 9, 2019 at 13:37 To: "Mark Svancarek (CELA) via Gnso-epdp-team" <gnso-epdp-team@icann.org>, "King, Brian" <Brian.King@markmonitor.com>, "alexATcolevalleyconsulting.com" <alex@colevalleyconsulting.com>, "sdelbiancoATnetchoice.org" <sdelbianco@netchoice.org>, Jennifer Gore <Jennifer@winterfeldt.law> Subject: [Gnso-epdp-team] FW: Updated Language Regarding Purposes

Notice: This email is from an external sender.

Ugh—suggestions for dealing with this?

From: Amr Elsadr <aelsadr@icannpolicy.ninja> Reply-To: Amr Elsadr <aelsadr@icannpolicy.ninja> Date: Wednesday, October 9, 2019 at 4:34 AM To: Margie Milam <margiemilam@fb.com> Subject: Re: Updated Language Regarding Purposes

Hi Margie,

Thanks for this. I’m still having trouble with the reference to Article 5.1.b, and its applicability here. The ICO guidance on the purpose limitation principle has only reinforced this (https://ico.org.uk/for-organisations/guide-to-data-protection/guide-to-the-g...). The explanation of what the principle is, as well as the checklist associated with it all indicate to me that it is applicable to the Data Controller, not a 3rd party/Requestor for disclosure/access.

My thinking is that if we are to proceed as you have suggested in your email below, the process needs to loop in the Data Controller, somehow. Some reasons why this might be necessary:

1. It shouldn’t be up to the 3rd party to determine what additional purposes are or are not compatible. Ultimately, the Data Controller and Processor will be held accountable by the data subject, and possibly liable by a DPA for errors in judgment on this, so should be looped in. 2. If the Controller is not (at a minimum) informed of additional purposes for which the personal data will be processed, I’m not sure how the Controller will track and keep records of how the data that was disclosed will be or was processed. 3. If the Data Subject requests access to a report on how its personal data has been processed, it would need to make this request to the Controller with which it is familiar (likely the registrar). If the Controller is not involved in the decision to process the personal data for additional compatible purposes, it will not be in a position to provide the Data Subject with a complete report on how the data was, or is being, processed, at least not until (or if) an audit is conducted.

So let’s say there is a scenario where a Requestor has been granted disclosure/access to the personal data for a specific purpose, then discovers that there is(are) additional purpose(s) for which the personal data needs to be processed further. This could be for compatible purposes, or other unrelated ones (but still fulfilling the requirements of a legitimate interest of the Requestor and supported by a legal basis).

It’d make sense to me, that in this kind of scenario, some follow-up to the original request for disclosure be available where the Requestor communicates the need for further processing in the SSAD, and that there is some need for the Controller to make a decision on wether to grant permission for this additional processing.

Also, since this would be a follow-up to a previously approved disclosure request, it might make sense that the follow-up is flagged for a quicker response time of the request for additional processing of the personal data for additional purposes (compatible or unrelated). This could possibly be reflected in Building Blocks G and K?

I know this adds an administrative layer, and slightly slows things down, but it provides more certainty in the process as a whole, doesn’t it? I believe it would be necessary in order to protect the rights of all parties involved, as well as provide the transparency in processing that you referred to in your proposed amendment to subsection C of Building Block D.

If you agree with any of this, in principle, we can try some wordsmithing of the proposed amendment. If you have concerns, let’s try to address them first.

Thanks again, Margie.

Amr

On Oct 8, 2019, at 6:53 PM, Margie Milam <margiemilam@fb.com> wrote:

Hi Amr – Following up on today’s homework – here’s a link to information from the UK Information Office that can help guide the drafting of this section:

https://ico.org.uk/for-organisations/guide-to-data-protection/guide-to-the-g...

Here’s what I suggest:

The building block should use this language:

“not incompatible with the original purpose, provided the new purpose is fair, lawful and transparent.”

The policy recommendation would also need to include specific disclosures to the registrant, describing the common purposes for 3rd party access, so that the transparency requirement is met.

Margie

_______________________________________________ Gnso-epdp-team mailing list Gnso-epdp-team@icann.org https://mm.icann.org/mailman/listinfo/gnso-epdp-team _______________________________________________ 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 (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). 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.