OPINION AND ORDER
This lawsuit began when Ashot Egiazaryan sued Peter Zalmayev for defamation and injurious falsehood. In a counterclaim, Zalmayev alleged that the suit was a “strategic lawsuit against public participation” in violation of N.Y. Civ. Rights Law §§ 70-a, 76-a (the “anti-SLAPP” statute), and also asserted a defamation claim. Following rulings on the parties’ motions to dismiss, the only remaining claim in this lawsuit is Zalmayev’s anti-SLAPP counterclaim against Egiazaryan. See Egiazaryan v. Zalmayev,
In this motion, Zalmayev seeks the production of 50 e-mails that were sent or received by BGR Garbara Limited (“BGR”), a public relations firm Egiazaryan hired, and that have been withheld on the basis of attorney-client privilege and the work product doctrine.
I. BACKGROUND
A. Relationship Between BGR, Egiazaryan, and Egiazaryan’s Attorneys
BGR is a public relations firm with offices in London, England. See Cohen Decl. ¶2. In February 2011, before this suit was filed, Egiazaryan’s London counsel, Gibson Dunn & Crutcher LLP (“Gibson Dunn”), retained BGR to “assist with [Gibson Dunn’s] representation of [Egiazaryan] in connection with certain arbitration proceedings.” See Letter from Ivo Ilic Gabara, President, BGR, to Laurence Shore, Partner, Gibson Dunn, dated Mar. 14, 2011 (annexed as Ex. 4 to Golden Decl.) (“BGR Agreement”), at 1. BGR’s scope of work encompassed “all global communication and United States government relations needs” that Egiazaryan required. Id. BGR was to “[d]evelop and implement a global
According to Egiazaryan’s attorney, BGR “facilitated the rendition of legal services” with respect to “a London arbitration, this defamation lawsuit and Mr. Egiazaryan’s efforts to remain in the United States.” Cohen Deel. ¶2. Lough states that “BGR advised counsel for Mr. Egiazaryan as to what might be effectively done on the public relations front ... so [counsel] could properly advise their client as to the appropriate course of action in light of his wider litigation interests.” Lough Deel. ¶ 2. BGR believed it was part of “Egiazaryan’s overall litigation team and expected that its privileged communications would remain privileged.” Id.
Starting in March 2011, BGR collected and facilitated the production of “documents” in this lawsuit, Cohen Deel. ¶ 4, though it is not suggested that these documents involved anything other than BGR’s own documents. Egiazaryan’s attorney states that BGR also “participated in the development of legal strategy in combating Mr. Zalmayev’s malicious black public relations campaign against Mr. Egiazaryan, including with regard to Mr. Egiazaryan’s lawsuit.” Id. BGR conferred with Drew Holiner, Egiazaryan’s personal attorney, regarding Egiazaryan’s “legal activities.” Id. ¶ 5.
On July 18, 2011, Zalmayev served document requests on Egiazaryan, which included requests for documents relating to BGR. See Peter Zalmayev’s Request for Documents Directed to Ashot Egiazaryan, dated July 18, 2011 (annexed as Ex. 1 to Lough Deel.) (“July 18 Doc. Requests”) (Document Request # # 42-45, 47-49, 56, 78, 89, 99). In response, BGR “undertook a significant effort to assist” Egiazaryan’s attorney on this case—Flemming Zulack Williamson Zauderer LLP (“FZWZ”)—in collecting “documents from BGR and relevant affiliates.... ” Lough Deck ¶ 3. BGR states that at that point in time it “reasonably expected that its communications and document-sharing with FZWZ were confidential and protected in order to promote the legal interests of our shared client, Mr. Egiazaryan.” Id. (citing Privilege Log for PosWComplaint BGR E-mails (annexed as Ex. 3 to Cohen Deck) (“Revised Privilege Log”), Document # # 4,14-16).
On August 19, 2011, Zalmayev served BGR’s affiliate in Washington, D.C. with subpoenas. See “History of Mr. Zalmayev’s Attempts to Obtain Documents from BGR” (annexed as Ex. 12 to Golden Deck) (“Procedural History”), at 1. At an unspecified date—presumably in August 2011-when it became “apparent” that Zalmayev sought to serve BGR with subpoenas, BGR “retained” FZWZ to represent it as a non-party witness. Cohen Deck ¶ 6; see also Lough Deck ¶ 4 (referring to BGR “continuing]” with FZWZ as its “outside legal counsel”). On September 6, 2011, BGR signed a retainer agreement with FZWZ under which FZWZ would “рrovide representation in connection with the subpoenas issued” to BGR in this case. Letter from Jonathan Lupkin, Esq., FZWZ, to Gabara & Lough, dated Sept. 6, 2011 (annexed as Ex. 4 to Lough Deck) (“Engagement Letter”), at 1. In signing the Engagement Letter, “BGR believed that it was merely documenting the privileged attorney-client relationship that had been established in July 2011.” Lough Deck ¶ 6. With the assistance of counsel, BGR produced over 3,200 pages of documents to Zalmayev. Cohen Deck ¶ 6.
B. Procedural History of the Instant Motion
As noted, Zalmayev served the BGR-related document requests on Egiazaryan on July
On May 9, 2012, Zalmayev served requests on BGR in London pursuant to the Hague Convention on the Service Abroad of Judicial and Extrajudicial Documents demanding, among other things, that it produce all responsive non-privileged documents. Procedural History at 3. Egiazaryan moved to strike the Hague requests on the grounds that they were duplicative of document requests served upon him. Id. During a telephone conference with the Court on May 23, 2012, Egiazaryan’s counsel represented that all responsive non-privileged BGR documents would be produced to Zalmayev. Id. As a result, Zalmayev withdrew his Hague requests insofar as they sought documents from BGR in London. Id. at 3-4.
At a conference held on August 24, 2012, the Court ordered that a privilege log be created for BGR documents generated after April 19, 2011. Transcript of Aug. 24, 2012 Proceeding, filed Sept. 6, 2012 (Docket # 183), at 24:9-25:11. In October 2012, Egiazaryan submitted a privilege log withholding 48 BGR e-mails sent after April 19, 2011. See Privilege Log for Post-Complaint BGR E-mails (annexed as Ex. 7 to Golden Decl.); Procedural History at 4. Then, on October 26, 2012, Egiazaryan submitted a revised privilege log which asserted attorney-client privilege and work produсt protection as to 50 BGR e-mails. See Revised Privilege Log.
II. DISCUSSION
Egiazaryan relies on four grounds to withhold the BGR e-mails: (1) attorney-client privilege arising out of FZWZ’s representation of BGR as a non-party, Opp. at 5-7; (2) attorney-client privilege under the agency exception for communications among BGR, FZWZ, and other counsel for Egiazaryan, id. at 7-11; (3) attorney-client privilege under the “common interest” doctrine, id. at 12-13; and (4) work product protection, id. at 13-15. Each of these grounds is discussed next.
To begin with, we must determine what party is asserting the claim of privilege arising out of BGR’s representation. The only brief filed on the topic is Egiazaryan’s, which explicitly states that the attorneys who filed it are appearing only on behalf of Egiazaryan without referencing BGR. See Opp. at 18. Nonetheless, the brief argues that an attorney-client privilege arose out of PZWZ’s representation of BGR and that this privilege protects a number of documents on the Revised Privilege Log. See Opp. at 5-7 (specifying Revised Privilege Log Document # # 4, 14-16, 24-29, 31-34, 36-38, 40, 46-49). Egiazaryan does not explain in the brief why he has standing to assert BGR’s claim of privilege. But inasmuch as the discrepancy has not been raised by Zalmayev, the Court will assume that the arguments in the brief relating to BGR’s privilege are in fact being raised by BGR—and not by Egiazaryan— given that the attorneys representing Egiazaryan are also representing BGR. See Engagement Letter; Lough Decl. ¶ 5.
Because this Court’s subject matter jurisdiction is based upon diversity, see Amended Counterclaim, filed Aug. 5, 2011 (Docket # 27), ¶ 3, state law provides the rule of decision concerning the claim of attorney-client privilege. See Fed.R.Evid. 501; In re Am. Tobacco Co.,
[A]n attorney or his or her employee, or any person who obtains without the knowledge of the client evidence of a confidential communication made between the attorney or his or her employee and the client in the course of professional employment, shall not disclose, or be allowed to disclose such communication, nor shall the client be compelled to disclose such communication —
N.Y. C.P.L.R. § 4503(a)(1). “The attorney-client privilege protects confidential communications between a lawyer and client relating to legal advice sought by the client.” In re Nassau Cnty. Grand Jury Subpoena Duces Tecum Dated June 24 2003, 4 N.Y.3d 665, 678,
In order for the privilege to apply, there must first be an attorney-client rela
BGR’s affidavit on the question of when it formed an attorney-client relationship with FZWZ is vague. Lough, a Vice President of BGR, asserts that a “confidential and privileged working relationship” with FZWZ began on an unnamed date in July 2011, but he concedes that this “working relationship” was only to “promote the legal interests of ... Egiazaryan,” Lough Deck ¶ 3, and not to provide legal representation to BGR. Of course, the mere fact that BGR was helping Egiazaryan’s counsel collect documents in BGR’s possession—even if BGR thought its communications were “confidential,” id.—does not establish an attorney-client relationship. Indeed, it frequently happens that a party served with document requests uses an attorney to obtain responsive documents that are in the physical possession of a non-party because they are within the responding party’s “control.” See Fed.R.Civ.P. 34(a). There is no warrant in case law to conclude, however, that the non-party thereby develops an аttorney-client relationship with the responding party’s attorney. Lough goes on to state that in “August” 2011, BGR “continued with FZWZ as our outside legal counsel____” Id. ¶4. But he provides no detail as to what act or event precipitated the commencement of FZWZ becoming BGR’s “legal counsel.”
The lack of clarity on this question is puzzling given that the January 16, 2013 Order specifically cited the Pellegrino standard and directed the parties to provide affidavits that would allow it to determine “when the attorney-client relationship between BGR and FZWZ began.” Jan. 16 Order at 1. The Order required that a representative of BGR submit an affidavit “detailing the retention of FZWZ, describing when BGR believed that FZWZ represented it, and the reasons therefor.” Id. at 2. Lough’s affidavit fails to provide the information required by the Court because it does not explain when there was “an explicit undertaking [by FZWZ] to perform a specific task.” Pellegrino,
Nonetheless, in its January 24, 2013 letter, FZWZ has pointed to рarticular e-mails produced ex parte as reflecting the existence of an attorney-client relationship. See Jan. 24 Letter at 2 (referring to Revised Privilege Log Document # # 4, 14-16, 24-29). Accordingly, the Court has examined these documents to determine what information they offer on this question. We begin by noting that neither these e-mails nor anything in the affidavits submitted to the Court reflect that BGR retained FZWZ to represent it with respect to any subject area other than “in connection with the subpoenas” Zalmayev issued on August 19, 2011. See Engagement Letter at 1; Lough Deck ¶ 4. Based on an in camera review of the cited documents, the Court concludes that BGR became aware of subpoenas on August 20, 2011. See Revised Privilege Log Document # 24. Because the
Subsequent to learning that service of subpoenas was imminent, however, BGR had communications with FZWZ concerning how to respond, which are reflected in some of the withheld e-mails. See id. # # 24-25, 28-29. Although BGR did not execute a formal retainer agreement with FZWZ until September 6, 2011, the communications BGR had with FZWZ beginning on August 21, 2011—the content of which is reflected in the withheld e-mails—were for the purpose of obtaining legal advice on how to respond to the subpoenas. Because these e-mails were confidential communications related to BGR seeking legal advice, the attorney-client privilege protects these documents from disclosure. See Pellegrino, 49 AD.3d at 99,
Documents 26 and 27, while post-dating August 20, 2011, concern an internal BGR telephone conference about the retention of FZWZ. These e-mails do not reflect legal advice from FZWZ regarding the subpoenas. Nor is there any other suggestion that they relate to obtaining legal advice. Instead, they relate to fee arrangements. Consequently, these e-mails are not protected by the attorney-client privilege. Priest,
The remaining e-mails to which BGR asserts attorney-client privilege post-date the September 6, 2011 retention agreement and an in camera review reveals that they are confidential communications between representatives of FZWZ and BGR concerning BGR’s obligations to respond to subpoenas. Accordingly, BGR has established attorney-client privilege for documents 31-34, 36-38, 40, 46-49 on the Revised Privilege Log as well.
In sum, the attorney-client privilege arising from FZWZ’s representation of BGR shields documents 24-25, 28-29, 31-34, 36-38, 40, and 46-49 on the Revised Privilege Log from disclosure.
B. Attorney-Client Privilege and the Agency Exception
Egiazaryan asserts attorney-client privilege over a number of documents that were shared with BGR: specifically, documents 1-3, 7-9,11-12,17,19-21, 30, 35, 39, 41-42, and 50 on the Revised Privilege Log. Zalmayev contends that any attorney-client privilege that attached to these communications was waived. See Def. Mem. at 18-20; Reply at 3-4. Egiazaryan argues that the privilege was not waived because BGR was his “agent.” See Opp. at 8-11. For purposes of this argument, we assume arguendo that in the absence of these e-mails having been revealed to BGR, they otherwise would have been shielded by attorney-client privilege.
“Generally, communications made between a defendant and counsel in the known presence of a third party are not privileged.” People v. Osorio,
Egiazaryan’s assertion of attorney-client privilege must be denied as to attorney-client communications shared with BGR because he has failed to establish that the privilege was not waived. Specifically, he has failed to show that BGR’s participation in discussions regarding his legal strategy was “nearly indispensable” or otherwise necessary to facilitate his communications with his attorneys. While BGR was retained to, among other things, “[d]evelop a set of key messages and compelling narrative in support of the legal cases,” BGR Agreement at 1, and “participate[ ] in the develоpment of legal strategy,” Cohen Deel. ¶ 4, Egiazaryan has not shown that BGR’s involvement was necessary to facilitate communications between himself and his counsel, as in the case of a translator or an accountant clarifying communications between an attorney and client, see Osorio,
Case law makes clear that “[a] media campaign is not a litigation strategy.” Haugh v. Schroder Inv. Mgmt. N. Am. Inc.,
Egiazaryan cites to In re Grand Jury Subpoenas Dated March 2k, 2003,
Both cases are also distinguishable on their facts. In re Grand Jury Subpoenas Dated March 2k, 2003 involved a public relations firm hired by lawyers to assist them in generating favorable publicity during a high profile grand jury investigation in order to lessen pressure on the prosecutors to secure an indictment. See
Here, Egiazaryan has not shown that the activities BGR was performing were part of FZWZ’s efforts to conduct “public advocacy on behalf of’ Egiazaryan in relation to this lawsuit. Indeed, BGR was retained before this litigation began. Moreover, it was not called upon to perform a specific litigation task that the attorneys needed to accomplish in order to advance their litigation goals—let alone a task that could be characterized as relating to the “administration of justice.” Rather, it was involved in a wide variety of public relations activities aimed at burnishing Egiazaryan’s image. Thus, the reasoning of In re Grand Jury Subpoenas Dated March 2k, 2003 is inapplicable. See also Ravenell v. Avis Budget Grp., Inc.,
In re Copper Market Antitrust Litigation is also distinguishable. In that case, a corporation retained a “crisis management” firm in connection with ongoing litigation. See
In sum, any attorney-client privilege arising from Egiazaryan’s relationship with his attorneys that may have attached to these documents was waived through their disclosure to BGR because there has been no showing that BGR’s involvement was necessary to facilitate communications between FZWZ and Egiazaryan.
C. Attorney-Client Privilege and the Common Interest Doctrine
Egiazaryan asserts attorney-client privilege as to documents 9, 14-15, 19-20, 24-42, and 44-50 on the Revised Privilege Log— сonsisting of communications among BGR and Egiazaryan’s counsel—based on the “common interest” doctrine. Opp. at 12-13. Because we have already found privilege with respect to a number of these documents, see section II.A, the only documents actually at issue are 9,14-15, 19-20, 26-27, 30, 35, 39, 41-42, 44-45, and 50.
As an initial matter, we note that Egiazaryan argues that “FZWZ” and BGR share a common legal interest. Opp. at 12-13. But the common interest doctrine does not call for the consideration of an attorney’s interest. Instead, it evaluates the interests of parties and/or nonparties—that is, clients. See, e.g., 330 Acquisition Co., LLC v. Regency Sav. Bank, F.S.B.,
New York courts applying the common interest rule to civil proceedings have often looked to federal case law for guidance. See, e.g., U.S. Bank N.A. v. APP Int’l Fin. Co.,
The common interest rule is not a separate privilege but “ ‘an extension of the attorney client privilege.’ ” United States v. Schwimmer,
serves to protect the confidentiality of communications passing from one party to the attorney for another party where a joint defense effort or strategy has been decided upon and undertaken by the parties and their respective counsel.... Only those communications made in the course of an ongoing common enterprise and intended to further the enterprise are protected____ The need to protect the free flow of information from client to attorney logically exists whenever multiple clients share a common interest about a legal matter, ... and it is therefore unnecessary ____ for the attorney representing the communicating party to be present when the communication is made to the other party’s attorney.
Id. at 243^44 (citations and internal quotation marks omitted); accord Am. Re-Ins. Co. v. U.S. Fid. & Guar. Co.,
The common interest rule does not apply merely because two parties share the same attorney or because one party has an interest in a litigation involving another party. Rather “[t]here must be a substantial showing by parties attempting to invoke the protections of the privilege of the need for a common defense as opposed to the mere existence of a common problem.” Finkelman v. Klaus,
Here, assuming arguendo that the attorney-client privilege would otherwise protect the e-mails at issue, Egiazaryan offers no proof of a common interest between himself and BGR that would satisfy the doctrine. Egiazaryan argues that he and BGR had a common interest in “protecting [his] legal interests” and “formulating a legal strategy on [his] behalf....” Opp. at 13. But the doctrine does not contemplate that an agent’s desire for its principal to win a lawsuit is an interest sufficient to prevent waiver of privilege inasmuch as it does not reflect a common defense or legal strategy. See, e.g., Sokol v. Wyeth, Inc.,
D. Work Product Doctrine
Egiazaryan seeks work product protection for documents 1-18, 21^42, 44^45, and 47-50. Opp. at 13-15. In light of our ruling upholding some claims of attorney-client privilege, see section II.A, the only documents at issue are 1-18, 21-23, 26-27, 30, 35, 39, 41-42, 44-45, and 50.
While state law governs the question of attorney-client privilege in a diversity action, federal law governs the application of the work product doctrine. Allied Irish Banks, P.L.C.,
Because the protection arises only for materials “prepared in anticipation of litigation,” it is not enough to show merely that the material was prepared at the behest of a lawyer or was provided to a lawyer. Rather, the materials must result from the conduct of “investigative or analytical tasks to aid counsel in preparing for litigation.” Costabile,
Egiazaryan’s papers provide little explanation of why the e-mails exchanged with BGR related to an attorney’s efforts to prepare for litigation as opposed to BGR’s efforts to implement Egiazaryan’s public relations campaign—a campaign that was certainly not limited to assisting attorneys in preparing for litigation. See BGR Agreement at 1. Instead, Egiazaryan conclusorily states that the materials “contain FZWZ’s legal strategy and attorney impressions,” and that because of this, they are necessarily protected. Opp. at 14. It was because of this lack оf detail that the Court directed the in camera review of the e-mails at issue. Upon reviewing these e-mails, the Court has identified a number that on their face relate solely to public relations strategy and contain no discussion of legal strategy or attorney opinions or impressions: specifically, documents 1, 3, 5-13, 17-18, 21-23, 35, 39, 44-45, and 50 on the Revised Privilege Log.
For example, a number of the emails concern BGR’s efforts to lobby Congress. See Revised Privilege Log Document # # 6-12. Materials prepared in furtherance of lobbying activities, even when conducted by a lawyer, are generally unprotected under the work product doctrine. See In re Grand Jury Subpoenas dated Mar. 9, 2001,
On the other hand, it is clear from the content of the remaining e-mails that they were prepared for purposes of litigation and therefore are within the scope of Fed. R.Civ.P. 26(b)(3). See Haugh,
A finding that a document was prepared in anticipation of litigation does not end the inquiry, however. The proponent of the protection must also show that work product has not been waived. See Allied Irish Banks, P.L.C.,
While the protections accorded to documents prepared in anticipation of litigation may be overcome through a showing of “substantial need for the document and an inability to obtain its contents elsewhere without undue hardship,” Adlman,
Finally, BGR asserts work product protection to e-mails related to its obligations under the subpoenas. See Opp. at 13 (asserting work product to Revised Privilege Log Document # # 24-29, 31-34, 36-38, 40, 46-49). In light of the Court’s prior rulings permitting the withholding of documents based on attorney-client рrivilege, the only documents at issue within this category are documents 26 and 27. There is no suggestion that these documents were prepared at the direction of FZWZ in its capacity as Egiazaryan’s law firm. Rather, they relate to BGR in its capacity as a non-party. Because Fed.R.Civ.P. 26(b)(3) does not apply to nonparties, see Ricoh Co. v. Aeroflex Inc.,
In sum, Egiazaryan has established that documents 2, 4, 14-16, 30, and 41^12 on the Revised Privilege Log are protected by the work product doctrine and Zalmayev has made no showing of substantial need or undue hardship to overcome the doctrine’s applicability. However, documents 1, 3, 5-13, 17-18, 21-23, 26-27, 35, 39, 44-45, and 50 on the Revised Privilege Log are not protected.
IV. CONCLUSION
For the foregoing reasons, Zalmayev’s motion to compel (Docket # 195) is granted in part and denied in part. Egiazaryan shall produce documents 1, 3, 5-13, 17-23, 26-27, 35, 39, 43-45, and 50 from the Revised Privilege Log.
SO ORDERED.
Notes
. See Peter Zalmayev’s Notice of Motion to Compel Ashot Egiazaryan’s Production of BGR Documents, filed Nov. 28, 2012 (Docket # 195) ("Notice"); Peter Zalmayev’s Memorandum of Law in Support of Motion to Compel Ashot Egiazaryan’s Production of BGR Documents, filed Nov. 28, 2012 (Docket # 196) ("Def. Mem.”); Declaration of James P. Golden, filed Nov. 28, 2012 (Docket # 197) ("Golden Deck”); Declaration of Jason T. Cohen, filed Dec. 10, 2012 (Docket # 200) ("Cohen Deck”); Memorandum of Law in Opposition to Defendant’s Motion to Compel Ashot Egiazaryan’s Production of BGR Documents, filed Dec. 10, 2012 (Docket # 201) ("Opp.”); Peter Zalmayev’s Reply Memоrandum of Law in Support of Motion to Compel Ashot Egiazaryan’s Production of BGR Documents, filed Dec. 17, 2012 (Docket # 202) ("Reply”); Declaration of James P. Golden, filed Dec. 17, 2012 (Docket #203); Declaration of John Lough, filed Jan. 30, 2013 (Docket #211) (“Lough Deck”); Letter from Jason T. Cohen, Esq., Flemming Zulack Williamson Zauderer LLP, to Honorable Gabriel W. Gorenstein, filed Feb. 28, 2013 (Docket #214) ("Jan. 24 Letter’’); Letter from James P. Golden, Esq., Golden & Hamburg, P.C., to Judge Gorenstein, filed Feb. 28, 2013 (Docket # 215).
. Zalmayev complains that the descriptions on the Revised Privilege Log are insufficiently detailed and asks that the Court order it supplemented. Notice at 2; Def. Mem. at 15-17. While the Court agrees that there are some scattered deficiencies, the underlying documents have now been produced to the Court and it would be an empty exercise to require supplementation of the log. See, e.g., Allied Irish Banks, P.L.C. v. Bank of Am., N.A.,
. Zalmayev contends that Egiazaryan’s privilege claims should not be heard now because Egiazaryan promised in March 2011 to provide BGR documents in exchange for Zalmayev withdrawing a prior motion. See Def. Mem. at 5, 7, 11, 14; Reply at 4-5. The record is hardly clear, however, that this promise meant that BGR was agreeing not to assert valid claims of privilege for documents post-dating the filing of this lawsuit. See Letter from Lupkin to Golden & Andrew Ryan, Esq., Salisbury & Ryan LLP, dated Apr. 19, 2012 (annexed as part of Ex. 5 to Cohen Decl.); Letter from Cohen to Golden & Ryan, dated May 30, 2012 (annexed as part of Ex. 5 to Cohen Decl.); E-mail from Cohen to Golden & Ryan (Oct. 5, 2012, 16:52 EST) (annexed as part of Ex. 5 to Cohen Decl.). Accordingly, we do not
On a separate point, Zalmayev’s notice of motion seeks not only production of documents but an order that BGR remove any redactions, except for personal identifiers, from previously produced documents. Notice at 1. However, the motion to compel does not identify which documents have been improperly redacted. Moreover, Zalmayev’s memorandum of law states only that this motion concerns the "documents dated after the filing of the complaint on April 19, 2011, which were asserted to be privileged but not put on a privilege log.” Def. Mem. at 5. Given that Zalmayev has not identified which documents were improperly redacted and has not given reasons why the redactions are improper, the Court rules only as to the 50 e-mails listed on the Revised Privilege Log.
. Egiazaryan also argues that he and BGR shared "a common legal interest in orchestrating BGR's document production as a subpoenaed non-party” and "formulating their document
. Egiazaryan has not adduced any argument as to why document # 43 should be protected.
