Case 2:17-cv-00514-JRG Document 161-17 Filed 02/13/19 Page 1 of 4 PageID #: 14387
`Case 2:17-cv-00514—JRG Document 161-17 Filed 02/13/19 Page 1 of 4 PageID #: 14387
`
`EXHIBIT 16
`
`EXHIBIT 16
`
`

`

`Case 2:17-cv-00514-JRG Document 161-17 Filed 02/13/19 Page 2 of 4 PageID #: 14388
`
`Iturralde, Enrique W.
`Bombach, Miguel J. (SDO)
`Bernstein, Matthew C. (SDO); Hurt, James (SDO); Canavera, Kyle Ryan (SDO); bcraft@findlaycraft.com; efindlay@findlaycraft.com; *Perkins Service HTC-AGIS; AGIS-Lit
`Re: AGIS - HTC"s source code
`Tuesday, October 02, 2018 10:42:11 AM
`
`From:
`To:
`Cc:
`Subject:
`Date:
`
`Miguel,
`
`We are disappointed that you would not extend the professional courtesy of expediting Mr. Vijh’s clearance.
`
`Omid Kia will review the code on October 3rd (and October 4th if necessary to review code for “dozens of accused products”). You raised no objection to his disclosure in August.
`
`Since we notified you of our intention to use source code to examine the witness in advance of 3 days before of the 10/5 deposition, you are correct in that HTC (as the producing party) may choose to bring a
`source code computer or paper printouts.
`
`Regardless of which option you elect for Friday, the production purportedly consists of HTC’s own source code which (by your own repeated admissions) has been set aside as relevant to this case “for over fourth
`months.” So not only is this HTC’s code, but HTC knows specifically about its relevance to this case and has known about it for “nearly half a year.” There is simply no excuse for HTC’s corporate designee on
`technical topics to lack the knowledge and preparation necessary to testify about HTC’s own source code, and we expect that the witness will be prepared to offer meaningful and substantive testimony to that end.
`
`Regards,
`Enrique
`
`From: "mbombach@perkinscoie.com" <MBombach@perkinscoie.com>
`Date: Tuesday, October 2, 2018 at 11:37 PM
`To: "Iturralde, Enrique W." <EIturralde@brownrudnick.com>
`Cc: "MBernstein@perkinscoie.com" <MBernstein@perkinscoie.com>, James Hurt <JHurt@perkinscoie.com>, "kcanavera@perkinscoie.com" <KCanavera@perkinscoie.com>, "bcraft@findlaycraft.com"
`<bcraft@findlaycraft.com>, "'efindlay@findlaycraft. com'" <efindlay@findlaycraft.com>, "PerkinsServiceHTC-AGIS@perkinscoie.com" <PerkinsServiceHTC-AGIS@perkinscoie.com>, AGIS-Lit
`<agislit@brownrudnick.com>
`Subject: RE: AGIS - HTC's source code
`
`Enrique,
`
`On October 1st, for the first time AGIS identified Mr. Vijh as an expert in this case. Prior to that date, AGIS had not disclosed him to HTC nor provided a copy of his CV, nor had Mr. Vijh signed an undertaking
`to be bound by the protective order in this case as evidenced by the October 1, 2018 date on his undertaking. Plainly put, prior to October 1st, we had no idea who Mr. Vijh was or that AGIS was attempting to use
`him as an expert.
`
`As you know, the Protective Order unequivocally states at paragraph 11(e) that HTC has seven days to raise an objection to any expert disclosed by AGIS. Your request that HTC immediately approve of Mr. Vijh
`under the protective order is both unreasonable and inappropriate, especially where Mr. Vijah would be given access to HTC’s highly confidential source code. HTC cannot put its source code at risk in such a
`manner, and it will take the time to review Mr. Vijay. It is unclear to us why AGIS waited until now to review code that’s been available for over four months, or why AGIS waited until this week to disclose Mr.
`Vijah, but HTC’s cannot be prejudiced by AGIS’ tactical decisions. Until HTC completes its review of Mr. Vijah, HTC cannot allow him to review its source code. However, we have no problem with a Brown
`Rudnick attorney reviewing the code on October 3rd, and the code will still be made available on that day. Please let us know if somebody from your office wants to review it.
`
`Regarding the use of source code at deposition, the Protective Order in this case does not require that a source code computer be made available at any deposition as your email implies. Paragraph 16(n) states HTC
`can provide printed copies of selected source code files if it so chooses. Again, HTC made its source code available on May 16th. AGIS chose not to review that code. AGIS did not even request review of the code
`until October 2nd (local Taiwan time), on the eve of the depositions—depositions that had been scheduled for over a month. Under these circumstances, having HTC load source code for dozens of accused
`products onto a source code computer is not reasonable, and HTC will not do it. However, should the Brown Rudnick attorney reviewing the source code at Perkins’ San Diego office on October 3rd identify lines
`of code, we would make every effort to have printed copies of that code available at the deposition on October 5th. Of course, AGIS’s last minute conduct means the witness will not be able to review or otherwise
`prepare to testify on the lines of code given he will not have an opportunity to see it before the deposition because of AGIS’s delay. This problem is solely of AGIS’s making, and HTC will not be prejudiced by
`AGIS’s dilatory conduct.
`
`Regards, Miguel
`
`Miguel Bombach | Perkins Coie LLP
`11988 El Camino Real Suite 350
`San Diego, CA 92130-2594
`D. +1.858.720.5747
`C: +1 646.469.1474
`F. +1.858.720.5847
`E. MBombach@perkinscoie.com<mailto:%20MBombach@perkinscoie.com>
`
`From: Iturralde, Enrique W. <EIturralde@brownrudnick.com>
`Sent: Tuesday, October 02, 2018 1:41 AM
`To: Bombach, Miguel J. (SDO) <MBombach@perkinscoie.com>
`Cc: Bernstein, Matthew C. (SDO) <MBernstein@perkinscoie.com>; Hurt, James (SDO) <JHurt@perkinscoie.com>; Canavera, Kyle Ryan (SDO) <KCanavera@perkinscoie.com>; bcraft@findlaycraft.com;
`efindlay@findlaycraft.com; *Perkins Service HTC-AGIS <PerkinsServiceHTC-AGIS@perkinscoie.com>; AGIS-Lit <agislit@brownrudnick.com>
`Subject: Re: AGIS - HTC's source code
`
`Miguel,
`
`As promised, I am confirming that Rahul Vijh will be reviewing the code at 10 AM PT on Wednesday 10/3. Given our process through the three steps of consolidation (pre-consolidation, consolidation, and
`unconsolidation) and with numerous POs floating around, I want to make sure Rahul is cleared for this case. So I have attached Mr. Vijh’s CV and signed undertakings for this and previous cases. Mr. Vijh does
`not have any pending patent applications, nor does he help prosecute, advise, or otherwise work on any pending patent applications. Mr. Vijh has not testified at trial in the past five years. Mr. Vijh has given
`deposition testimony in the following matter which is listed in greater detail in his CV: Plano Encryption Technologies, LLC v. Alkami Technology, Inc., 2:16-cv-01032, EDTX (Lead Case). Please confirm that
`you do not object to Mr. Vijh ahead of Wednesday’s review.
`
`In previous discussions, you asked me to let you know if we expected overlap of any of the two depositions. In order to facilitate logistics on your end, I am confirming that we will not overlap and that we will
`take the depositions consecutively. We also withdraw our request that you reconfigure the depositions; we will accept the schedule as is. Of course, we reserve our right to recall any of the witnesses if we need the
`full seven hours and the circumstances do not permit the full seven hours.
`
`Thanks,
`Enrique
`
`From: "Iturralde, Enrique W." <EIturralde@brownrudnick.com<mailto:EIturralde@brownrudnick.com>>
`Date: Tuesday, October 2, 2018 at 12:27 PM
`To: "mbombach@perkinscoie.com<mailto:mbombach@perkinscoie.com>" <mbombach@perkinscoie.com<mailto:mbombach@perkinscoie.com>>
`Cc: "MBernstein@perkinscoie.com<mailto:MBernstein@perkinscoie.com>" <MBernstein@perkinscoie.com<mailto:MBernstein@perkinscoie.com>>, James Hurt
`<JHurt@perkinscoie.com<mailto:JHurt@perkinscoie.com>>, "kcanavera@perkinscoie.com<mailto:kcanavera@perkinscoie.com>" <KCanavera@perkinscoie.com<mailto:KCanavera@perkinscoie.com>>,
`"bcraft@findlaycraft.com<mailto:bcraft@findlaycraft.com>" <bcraft@findlaycraft.com<mailto:bcraft@findlaycraft.com>>, "'efindlay@findlaycraft. com'"
`<efindlay@findlaycraft.com<mailto:efindlay@findlaycraft.com>>, "PerkinsServiceHTC-AGIS@perkinscoie.com<mailto:PerkinsServiceHTC-AGIS@perkinscoie.com>" <PerkinsServiceHTC-
`AGIS@perkinscoie.com<mailto:PerkinsServiceHTC-AGIS@perkinscoie.com>>, AGIS-Lit <agislit@brownrudnick.com<mailto:agislit@brownrudnick.com>>
`Subject: Re: AGIS - HTC's source code
`
`Miguel,
`
`Thank you for reverting to us quickly and letting us know tonight about the source code computer’s availability.
`
`Please also bring a source code computer to the technical witness’s deposition, and confirm that the witness testifying to the source code will be Mr. Steven Teng.
`
`Given the time, I will follow up Tuesday morning/afternoon with a confirmation for Mr. Rahul Vijh’s expected arrival time at your San Diego office on Wednesday, October 3rd.
`
`Thanks,
`Enrique
`
`

`

`Case 2:17-cv-00514-JRG Document 161-17 Filed 02/13/19 Page 3 of 4 PageID #: 14389
`
`From: "Iturralde, Enrique W." <EIturralde@brownrudnick.com<mailto:EIturralde@brownrudnick.com>>
`Date: Monday, October 1, 2018 at 11:56 PM
`To: "MBernstein@perkinscoie.com<mailto:MBernstein@perkinscoie.com>" <MBernstein@perkinscoie.com<mailto:MBernstein@perkinscoie.com>>
`Cc: "mbombach@perkinscoie.com<mailto:mbombach@perkinscoie.com>" <MBombach@perkinscoie.com<mailto:MBombach@perkinscoie.com>>, James Hurt
`<JHurt@perkinscoie.com<mailto:JHurt@perkinscoie.com>>, "kcanavera@perkinscoie.com<mailto:kcanavera@perkinscoie.com>" <KCanavera@perkinscoie.com<mailto:KCanavera@perkinscoie.com>>,
`"bcraft@findlaycraft.com<mailto:bcraft@findlaycraft.com>" <bcraft@findlaycraft.com<mailto:bcraft@findlaycraft.com>>, "'efindlay@findlaycraft. com'"
`<efindlay@findlaycraft.com<mailto:efindlay@findlaycraft.com>>, "PerkinsServiceHTC-AGIS@perkinscoie.com<mailto:PerkinsServiceHTC-AGIS@perkinscoie.com>" <PerkinsServiceHTC-
`AGIS@perkinscoie.com<mailto:PerkinsServiceHTC-AGIS@perkinscoie.com>>, AGIS-Lit <agislit@brownrudnick.com<mailto:agislit@brownrudnick.com>>
`Subject: Re: AGIS - HTC's source code
`
`Matt,
`
`Buried in a May 16th correspondence about HTC’s discovery deficiencies, we received a vague statement concerning source code which would be made available at a future date for an initial inspection. We were
`diligent in requesting an update from Miguel (and you were copied on the July 28 e-mail below) about the availability of the source code. We received no response from you and your team. Whether it’s oversight
`or gamesmanship on your part, I propose that we move the ball forward without the documenting/etc.
`
`By the looks of your e-mail below, it appears that the source code is available for review. Please confirm immediately that you will host the source code inspection at Perkins Coie’s San Diego office starting on
`Wednesday, October 3, 2018 starting at 10 AM PT. For your security list, our source code reviewer is Rahul Vijh.
`
`Thanks,
`Enrique
`
`From: "MBernstein@perkinscoie.com<mailto:MBernstein@perkinscoie.com>" <MBernstein@perkinscoie.com<mailto:MBernstein@perkinscoie.com>>
`Date: Monday, October 1, 2018 at 10:33 PM
`To: "Iturralde, Enrique W." <EIturralde@brownrudnick.com<mailto:EIturralde@brownrudnick.com>>
`Cc: "mbombach@perkinscoie.com<mailto:mbombach@perkinscoie.com>" <MBombach@perkinscoie.com<mailto:MBombach@perkinscoie.com>>, James Hurt
`<JHurt@perkinscoie.com<mailto:JHurt@perkinscoie.com>>, "kcanavera@perkinscoie.com<mailto:kcanavera@perkinscoie.com>" <KCanavera@perkinscoie.com<mailto:KCanavera@perkinscoie.com>>,
`"bcraft@findlaycraft.com<mailto:bcraft@findlaycraft.com>" <bcraft@findlaycraft.com<mailto:bcraft@findlaycraft.com>>, "'efindlay@findlaycraft. com'"
`<efindlay@findlaycraft.com<mailto:efindlay@findlaycraft.com>>, "PerkinsServiceHTC-AGIS@perkinscoie.com<mailto:PerkinsServiceHTC-AGIS@perkinscoie.com>" <PerkinsServiceHTC-
`AGIS@perkinscoie.com<mailto:PerkinsServiceHTC-AGIS@perkinscoie.com>>, AGIS-Lit <agislit@brownrudnick.com<mailto:agislit@brownrudnick.com>>
`Subject: Re: AGIS - HTC's source code
`
`Resend your email making the code available. And also every other email or letter where we mentioned it. Document the crap out of their bullshit. And then lay into them for playing games and otherwise being
`disingenuous. Send in the morning.
`Sent from my mobile device
`
`Matthew Bernstein | Perkins Coie LLP
`SAN DIEGO MANAGING PARTNER
`TAIPEI CO-MANAGING PARTNER
`11988 El Camino Real Suite 350
`San Diego, CA 92130-2594
`D. 1.858.720.5721
`M. 1.619.254.3273
`F. 1.858.720.5821
`E. MBernstein@perkinscoie.com<mailto:%20MBernstein@perkinscoie.com<mailto:MBernstein@perkinscoie.com%3cmailto:%20MBernstein@perkinscoie.com>>
`
`On Oct 1, 2018, at 10:02 PM, Iturralde, Enrique W. <EIturralde@brownrudnick.com<mailto:EIturralde@brownrudnick.com<mailto:EIturralde@brownrudnick.com%3cmailto:EIturralde@brownrudnick.com>>>
`wrote:
`
`Miguel,
`
`We did not receive any response to the below e-mail or any update about the availability of HTC source code. Please confirm that HTC no longer intends to produce any source code in this case.
`
`Thanks,
`Enrique
`
`From: "Iturralde, Enrique W." <EIturralde@brownrudnick.com<mailto:EIturralde@brownrudnick.com<mailto:EIturralde@brownrudnick.com%3cmailto:EIturralde@brownrudnick.com>>>
`Date: Saturday, July 28, 2018 at 5:31 AM
`To: "mbombach@perkinscoie.com<mailto:mbombach@perkinscoie.com><mailto:mbombach@perkinscoie.com%3cmailto:mbombach@perkinscoie.com%3e>"
`<MBombach@perkinscoie.com<mailto:MBombach@perkinscoie.com<mailto:MBombach@perkinscoie.com%3cmailto:MBombach@perkinscoie.com>>>,
`"MBernstein@perkinscoie.com<mailto:MBernstein@perkinscoie.com><mailto:MBernstein@perkinscoie.com%3cmailto:MBernstein@perkinscoie.com%3e>"
`<MBernstein@perkinscoie.com<mailto:MBernstein@perkinscoie.com<mailto:MBernstein@perkinscoie.com%3cmailto:MBernstein@perkinscoie.com>>>, James Hurt
`<jhurt@perkinscoie.com<mailto:jhurt@perkinscoie.com<mailto:jhurt@perkinscoie.com%3cmailto:jhurt@perkinscoie.com>>>, "kcanavera@perkinscoie.com<mailto:kcanavera@perkinscoie.com>
`<mailto:kcanavera@perkinscoie.com%3cmailto:kcanavera@perkinscoie.com%3e>"
`<kcanavera@perkinscoie.com<mailto:kcanavera@perkinscoie.com<mailto:kcanavera@perkinscoie.com%3cmailto:kcanavera@perkinscoie.com>>>, "bcraft@findlaycraft.com<mailto:bcraft@findlaycraft.com>
`<mailto:bcraft@findlaycraft.com%3cmailto:bcraft@findlaycraft.com%3e>" <bcraft@findlaycraft.com<mailto:bcraft@findlaycraft.com<mailto:bcraft@findlaycraft.com%3cmailto:bcraft@findlaycraft.com>>>,
`"'efindlay@findlaycraft. com'" <efindlay@findlaycraft.com<mailto:efindlay@findlaycraft.com<mailto:efindlay@findlaycraft.com%3cmailto:efindlay@findlaycraft.com>>>, "PerkinsServiceHTC-
`AGIS@perkinscoie.com<mailto:PerkinsServiceHTC-AGIS@perkinscoie.com><mailto:PerkinsServiceHTC-AGIS@perkinscoie.com%3cmailto:PerkinsServiceHTC-AGIS@perkinscoie.com%3e>"
`<PerkinsServiceHTC-AGIS@perkinscoie.com<mailto:PerkinsServiceHTC-AGIS@perkinscoie.com<mailto:PerkinsServiceHTC-AGIS@perkinscoie.com%3cmailto:PerkinsServiceHTC-
`AGIS@perkinscoie.com>>>
`Cc: AGIS-Lit <agislit@brownrudnick.com<mailto:agislit@brownrudnick.com<mailto:agislit@brownrudnick.com%3cmailto:agislit@brownrudnick.com>>>
`Subject: AGIS - HTC's source code
`
`Miguel,
`
`Your May 16, 2018 letter states that "HTC Corp. will lay make its source code for its phones available for inspection." However, we have not received any further updates regarding the status of HTC's source code
`production. Please let us know when HTC's source code (for all HTC Accused Products) becomes available for inspection so that we can schedule a review. Please also let us know if you can make the code
`available for inspection at either one of Perkins Coie's NYC or DC offices.
`
`Regards,
`Enrique
`
`[http://www.brbi.dom/signature/Brown%20Rudnick.jpg]
`
`Enrique W. Iturralde
`
`Brown Rudnick LLP
`Seven Times Square
`New York, NY 10036
`T: 212-209-4936
`F: 212-938-2936
`eiturralde@brownrudnick.com<mailto:eiturralde@brownrudnick.com>
`<mailto:eiturralde@brownrudnick.com<mailto:eiturralde@brownrudnick.com%3cmailto:eiturralde@brownrudnick.com%3e%3cmailto:eiturralde@brownrudnick.com>>
`www.brownrudnick.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.brownrudnick.com&d=DwMFaQ&c=XRWvQHnpdBDRh-yzrHjqLpXuHNC_9nanQc6pPG_SpT0&r=LIjXtO-
`JmOL_bC65F8DEifOymOcEYu8dyS3JfqFBieGpVm9yGvoz1QfsLY2UAGnp&m=etczjxga70JbeKUMQFeQM7YkFXn3jovSESG5SymP15Y&s=4iZbbZZnpYgPmLX60v7t6OQUjUdsMuif3T3QtD3bgKU&e=>>
`<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.brownrudnick.com&d=DwMFaQ&c=XRWvQHnpdBDRh-yzrHjqLpXuHNC_9nanQc6pPG_SpT0&r=l1iCa248MWyU_ssrj2kv-
`9zvvNp9hsKnocNDz8EDb3g&m=zOHE_odaOH2jr0TwNKbKklgSCD0_oGFYPQwNDsMV_7M&s=KL7oDmKcVPJxIRzZBCnGUV2uzxqQg_jjhPElpr1B76k&e=>>
`<http://www.brownrudnick.com/<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.brownrudnick.com_&d=DwMFaQ&c=XRWvQHnpdBDRh-
`yzrHjqLpXuHNC_9nanQc6pPG_SpT0&r=l1iCa248MWyU_ssrj2kv-
`9zvvNp9hsKnocNDz8EDb3g&m=zOHE_odaOH2jr0TwNKbKklgSCD0_oGFYPQwNDsMV_7M&s=kSRcVxUA0sy637_wboH1mTr1DSQURPL8xx4BztGCPXU&e=>>
`<%3e%3chttp:/www.brownrudnick.com/%3chttps:/urldefense.proofpoint.com/v2/url?u=http-3A__www.brownrudnick.com_&d=DwMFaQ&c=XRWvQHnpdBDRh-
`yzrHjqLpXuHNC_9nanQc6pPG_SpT0&r=l1iCa248MWyU_ssrj2kv-
`9zvvNp9hsKnocNDz8EDb3g&m=zOHE_odaOH2jr0TwNKbKklgSCD0_oGFYPQwNDsMV_7M&s=kSRcVxUA0sy637_wboH1mTr1DSQURPL8xx4BztGCPXU&e=%3e%3e>
`
`

`

`Case 2:17-cv-00514-JRG Document 161-17 Filed 02/13/19 Page 4 of 4 PageID #: 14390
`
`Please consider the environment before printing this e-mail
`
`***********************************************************************************
`
`The information contained in this electronic message may be legally privileged and confidential under applicable law, and is intended only for the use of the individual or entity named above. If the recipient of this
`message is not the above-named intended recipient, you are hereby notified that any dissemination, copy or disclosure of this communication is strictly prohibited. If you have received this communication in error,
`please notify Brown Rudnick LLP, (617) 856-8200 (if dialing from outside the US, 001-(617)-856-8200) and purge the communication immediately without making any copy or distribution.
`
`To the extent Brown Rudnick is a "data controller" of the "personal data" (as each term is defined in the European General Data Protection Regulation) you have provided to us in this and other communications
`between us, please see our privacy statement and summary here<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.brownrudnick.com_privacy-2Dpolicy_&d=DwMFaQ&c=XRWvQHnpdBDRh-
`yzrHjqLpXuHNC_9nanQc6pPG_SpT0&r=l1iCa248MWyU_ssrj2kv-
`9zvvNp9hsKnocNDz8EDb3g&m=zOHE_odaOH2jr0TwNKbKklgSCD0_oGFYPQwNDsMV_7M&s=5urcuSItppy9KbzuRdADeiciC6kkXZPM4TtpxHUpIQM&e=> which sets out details of the data controller,
`the personal data we have collected, the purposes for which we use it (including any legitimate interests on which we rely), the persons to whom we may transfer the data and how we intend to transfer it outside
`the European Economic Area.
`
`***********************************************************************************
`
`________________________________
`
`NOTICE: This communication may contain privileged or other confidential information. If you have received it in error, please advise the sender by reply email and immediately delete the message and any
`attachments without copying or disclosing the contents. Thank you.
`
`***********************************************************************************
`
`The information contained in this electronic message may be legally privileged and confidential under applicable law, and is intended only for the use of the individual or entity named above. If the recipient of this
`message is not the above-named intended recipient, you are hereby notified that any dissemination, copy or disclosure of this communication is strictly prohibited. If you have received this communication in error,
`please notify Brown Rudnick LLP, (617) 856-8200 (if dialing from outside the US, 001-(617)-856-8200) and purge the communication immediately without making any copy or distribution.
`
`To the extent Brown Rudnick is a "data controller" of the "personal data" (as each term is defined in the European General Data Protection Regulation) you have provided to us in this and other communications
`between us, please see our privacy statement and summary here<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.brownrudnick.com_privacy-2Dpolicy_&d=DwMFaQ&c=XRWvQHnpdBDRh-
`yzrHjqLpXuHNC_9nanQc6pPG_SpT0&r=LIjXtO-
`JmOL_bC65F8DEifOymOcEYu8dyS3JfqFBieGpVm9yGvoz1QfsLY2UAGnp&m=etczjxga70JbeKUMQFeQM7YkFXn3jovSESG5SymP15Y&s=NvLaAtg_cWExEKrpkFygVhuRHGUlwA9sXna_f8cLsoM&e=>
`which sets out details of the data controller, the personal data we have collected, the purposes for which we use it (including any legitimate interests on which we rely), the persons to whom we may transfer the
`data and how we intend to transfer it outside the European Economic Area.
`
`***********************************************************************************
`
`________________________________
`
`NOTICE: This communication may contain privileged or other confidential information. If you have received it in error, please advise the sender by reply email and immediately delete the message and any
`attachments without copying or disclosing the contents. Thank you.
`
`***********************************************************************************
`
`The information contained in this electronic message may be legally privileged and confidential under applicable law, and is intended only for the use of the individual or entity named above. If the recipient of this message is not the above-named intended recipient, you are hereby
`notified that any dissemination, copy or disclosure of this communication is strictly prohibited. If you have received this communication in error, please notify Brown Rudnick LLP, (617) 856-8200 (if dialing from outside the US, 001-(617)-856-8200) and purge the communication
`immediately without making any copy or distribution.
`
`To the extent Brown Rudnick is a "data controller" of the "personal data" (as each term is defined in the European General Data Protection Regulation) you have provided to us in this and other communications between us, please see our privacy statement and summary here
`which sets out details of the data controller, the personal data we have collected, the purposes for which we use it (including any legitimate interests on which we rely), the persons to whom we may transfer the data and how we intend to transfer it outside the European Economic
`Area.
`
`***********************************************************************************
`
`