Federal Trade Commission v. Amazon.com Inc

Opinion

1 2 3

4 5 UNITED STATES DISTRICT COURT 6 WESTERN DISTRICT OF WASHINGTON AT SEATTLE 7 FEDERAL TRADE COMMISSION, CASE NO. 2:23-cv-00932-JHC 8

ORDER 9 Plaintiff, 10 v. 11 AMAZON.COM, INC; NEIL LINDSAY, individually and as an officer of 12 Amazon.com, Inc.; RUSSELL GRANDINETTI, individually and as an 13 officer of Amazon.com, Inc.; JAMIL GHANI, individually and as an officer of 14 Amazon.com, Inc.,

15 Defendants. 16

17 I 18 INTRODUCTION 19 20 This matter comes before the Court on the FTC’s motion to compel production of 17 21 documents that Amazon clawed back. Dkt. ## 139 (sealed), 140 (redacted). Amazon produced 22 the documents at issue to the FTC either in the FTC’s investigation underlying this case or in 23 other investigations. See Dkt. ## 140-2 at 3–5; 90-2 at 27–28. Then, in the investigation 24 1 underlying this case, Amazon asserted privilege regarding the documents and clawed them back. 2 Id. 3 Amazon argues that the attorney-client privilege and work-product doctrine protect the

4 documents. Dkt. # 142 at 5. The FTC disputes this, and also says that Amazon waived any 5 privilege. Dkt. # 140-1 at 3. The Court agrees that Amazon has waived its privilege regarding 6 all but six of the documents at issue by producing some documents intentionally with redactions 7 and by failing to promptly claw back some of the unintentionally produced documents. The 8 Court concludes that the remaining documents warrant in camera review. Thus, the Court 9 GRANTS the motion to compel as to 11 of the documents and GRANTS the FTC’s request for 10 in camera review of the remaining documents. 11 12 II

13 BACKGROUND 14 The FTC began investigating Amazon in this matter on March 16, 2021. Dkt. ## 90-2 at 15 27; 53 at 2. The FTC calls this investigation the Dark Patterns Investigation. Dkt. # 90-2 at 27. 16 During this investigation, Amazon produced 29,998 documents. Dkt. ## 90-2 at 29; 53 at 2. 17 Amazon produced 8,826 documents between April 15, 2021, and February 18, 2022, and 19,154 18 documents between October 7, 2022, and February 13, 2023. Dkt. # 90-2 at 29. The FTC also 19 investigated Amazon in two matters unrelated to this case, which the FTC refers to as 20 Investigations 1 and 2. Dkt. # 90-2 at 28. Amazon has produced more than 1.7 million 21 documents across the three FTC investigations. Dkt. # 143 at 1. Amazon produced 11 of the 22 documents at issue in the Dark Patterns Investigation and the remaining six in Investigations 1 23 and 2. Dkt. # 142 at 6. 24 1 The documents at issue are as follows: 2 • IC-11 and IC-36 are copies of the same memo prepared for a meeting on May 6, 2021. Dkt. ## 90-2 at 31; 139-1 at 3. The parties call this the 3 “May 4 memo.” Id.

4 • IC-4, IC-6, IC-17, IC-22, IC-31, and IC-48, are copies of the same memo prepared for a meeting on July 14, 2021. Dkt. ## 90-2 at 32–34; 140-2 at 5 3; 142 at 9. IC-5, IC-18, IC-19, IC-20, and IC-21, are copies of the same presentation for the same meeting on July 14, 2021. Dkt. # 142 at 13–14. 6 The parties call these two sets of documents the “July 14 memo and presentation.” Id. 7

• IC-37 is a document prepared for a meeting among members of the 8 Amazon Prime team on May 10, 2021, which followed up on the discussion at the May 6 meeting. Dkt. # 52 at 5. 9

• IC-9 is a chat thread between two Amazon employees. Id. at 9. 10

• IC-27 is an “early draft” of an Amazon Prime update that “reflect[s] 11 determinations made during the May 6 Meeting.” Id. at 7–8.

12 • IC-40 was used to prepare an Amazon employee for testimony before the 13 FTC. Id. at 9.

14 The FTC filed this case on June 21, 2023. Dkt. # 1. At the start of this case, the FTC 15 moved to desequester 54 clawed-back documents. Dkt. ## 4 at 3 (sealed); 90-2 at 6 (redacted). 16 The Court denied the motion “without prejudice to Plaintiff’s ability to seek these documents 17 through discovery in this matter.” Dkt. # 89 at 1. The parties have resolved their dispute over 18 some documents, and only 16 of the original 54 documents are now at issue. Dkt. # 140-1 at 9. 19 The parties’ dispute over IC-37 arose after the FTC’s motion to desequester. Id. at 10–11. 20 A. May 4 Memo 21 22 23

24 1 IC stands for “In Camera.” 1 Amazon produced two copies of the May 4 memo with redactions in Investigations 1 and 2 2 (IC-1 and IC-36).2 The FTC used the May 4 memo at a December 2, 2022, hearing during the 3 Dark Patterns Investigation, and Amazon’s attorneys did not object. Dkt. # 90-2 at 30. The FTC 4 then used the documents at a January 11, 2023, hearing during the same investigation, at which 5 time Amazon’s counsel claimed privilege and expressed their intention to claw back the 6 documents. Id. at 30–31. Amazon clawed back these two documents on January 13, 2023. Id. 7 at 326, 332. The FTC argues that the memo is not protected by attorney-client privilege, and 8 even if it is, Amazon waived the privilege by producing the memo twice with redactions. Dkt. # 9 140-1 at 10, 13–16. 10 B. July 14 Memo and Presentation 11 Overall, Amazon produced six copies of the July 14 memo (IC-4, IC-6, IC-17, C-22, IC- 12 31, IC-48) and five copies of the July 14 presentation (IC-5, IC-18, IC-19, IC-20, IC-21). Dkt. # 13 90-2 at 34. In the Dark Patterns Investigation Amazon produced one copy of the July 14 memo 14 (IC-6) without redactions, and two copies of the memo with redactions (IC-17, IC-22). Id. In 15 Investigation 1, Amazon produced one copy of the memo without redactions (IC-48). Id. In 16 Investigations 1 and 2, Amazon produced one copy of the memo without redactions (IC-31). Id. 17 Amazon first withheld IC-4 as privileged in the Dark Patterns Investigation. Id. at 277. But on 18 January 5, 2023, Amazon produced a redacted version of IC-4, explaining that upon review of its 19 production, it determined that “six previously withheld documents[,]” including IC-4, were “not 20 privileged or partially privileged.” Id. All five versions of the July 14 presentation—IC-5, IC- 21 22 23 2 Amazon produced the documents in two separate investigations for a total of four productions. Dkt. # 90-2 at 28. 24 1 18, IC-19, IC-20, IC-21—were produced without redactions in the Dark Patterns Investigation. 2 Dkt. # 140-2 at 3. 3 At a hearing during the Dark Patterns Investigation on January 20, 2023, the FTC marked

4 an unredacted version of the July 14 memo (IC-31) as an exhibit and Amazon claimed privilege. 5 Dkt. # 90-2 at 33. Amazon clawed back the July 14 memo and presentation on February 7, 2023. 6 Dkt. # 90-2 at 33. The FTC argues that the memo is not protected by attorney-client privilege, 7 and even if it is, Amazon waived the privilege by producing the memo with redactions. Dkt. # 8 140-1 at 11, 13–16. 9 C. IC-37 10 Amazon produced IC-37 once without redactions in Investigation 1. Dkt. ## 90-2 at 28, 11 330; 140-2 at 5. In the Dark Patterns Investigation, Amazon clawed the document back on 12 February 7, 2023, and produced a redacted version on February 14, 2023. Dkt. # 90-2 at 35–36, 13 102. Then, in this matter, Amazon clawed back IC-37 again on January 22, 2024, and produced 14 the document with more privilege redactions. Dkt. # 140-2 at 81. The FTC argues that Amazon 15 waived its privilege in its second round of redactions to IC-37. Dkt. # 140-1 at 14–16. The FTC 16 ask the Court to compel Amazon to produce the document as it was produced on February 14, 17 2023. Id. at 3, 17. 18 19 D. Other documents 20 On November 22, 2022, in the Dark Patterns Investigation, the FTC identified three 21 messages in IC-9 as potentially privileged, and informed Amazon. Dkt. ## 140-2 at 3; 90-2 at 22 247. Amazon clawed the document back on November 29, 2022, and then produced it with 23 redactions. Dkt. # 90-2 at 35. Amazon redacted 13 messages from the chat. Dkt. # 140-2 at 4. 24 1 The FTC challenges the 10 redactions beyond those the FTC identified as proper. Dkt. # 140-1 2 at 13. The FTC says that it has reason to believe that Amazon redacted messages that are not 3 privileged and asks the Court to conduct in camera review. Id.

4 Amazon produced IC-40 in Investigation 1. See Dkt. # 90-2 at 28, 330. The FTC 5 marked IC-40 as an exhibit at a hearing in the Dark Patterns Investigation on December 20, 6 2022, and Amazon’s attorney reserved the right to claw it back after review. Id. at 35. Amazon 7 clawed the document back on February 7, 2023. Id. Amazon produced IC-27 in the Dark 8 Patterns Investigation. Id. at 28, 328. The FTC marked IC-27 as an exhibit at a hearing in the 9 Dark Patterns Investigation on January 17, 2023. Dkt. # 140-2 at 4. Amazon clawed the IC-27 10 back on February 7, 2023. Id. The FTC says that IC-40 and IC-27 are not privileged, and even 11 if they are, Amazon waived the privilege by not promptly clawing the documents back. Dkt. # 12 140-1 at 3.

13 14 III 15 DISCUSSION 16 A. Waiver 17 Generally, a party waives privilege with respect to a document if they produce it. United 18 States v. Sanmina Corp., 968 F.3d 1107, 1116–17 (9th Cir. 2020). Federal Rule of Evidence 19 502(b) provides an exception for inadvertent disclosures. And Federal Rule of Evidence 502(d) 20 provides that a federal court may order that the privilege is not waived as a result of production. 21 “[W]aiver of any privilege [i]s the threshold issue” when determining whether a clawed back 22 document is privileged. In re Qualcomm Litig., No. 3:17-CV-108-GPC-MDD, 2018 WL 23 24 1 6617294, at *4 (S.D. Cal. Dec. 18, 2018). The party asserting privilege bears the burden of 2 proving that privilege is not waived. Id. 3 The FTC says that Amazon waived its privilege for some documents at issue here

4 because it did not satisfy any of the three elements of Rule 502(b). Dkt. ## 140-1 at 13; 145 at 6. 5 First, the FTC says that production was intentional. Id. Second, the FTC says that even if the 6 production were unintentional, Amazon did not take “reasonable steps to prevent” the production 7 and it did not “promptly” remedy the production. Dkt. ## 140-1 at 15; 145 at 6–7. 8 Amazon responds that it did not waive privilege because all the documents at issue are 9 protected by the stipulated order that the Court entered under Federal Rule of Evidence 502(d) at 10 Dkt. # 123. Dkt. # 142 at 15. Amazon also argues that even if that order does not apply, under 11 Rule 502(b), it took reasonable steps to prevent production where it has produced more than 1.7 12 million documents across two cases with the FTC and attempted to remedy the disclosures as 13 soon as it learned about them. Dkt. # 142 at 16–17. 14 1. The stipulated Rule 502(d) order 15 16 Rule 502(d) provides that a “federal court may order that the privilege or protection is not 17 waived by disclosure connected with the litigation pending before the court.” The order at issue 18 provides: 19 [P]ursuant to Fed. R. Evid. 502(d), the production of any documents, electronically stored information (ESI) or information, whether inadvertent or otherwise, in this 20 proceeding shall not, for the purposes of this proceeding or any other federal or state proceeding, constitute a waiver by the producing party of any privilege 21 applicable to those documents, including the attorney-client privilege, attorney work-product protection, or any other privilege or protection recognized by law. 22 Dkt. # 123 at 1 (emphasis added). 23 24 1 The documents at issue were produced during the FTC’s investigation underlying this 2 case and other FTC investigations.3 Amazon argues that the order applies to documents 3 produced during the pre-suit investigation, and thus Amazon’s production of these documents 4 does not waive privilege. Dkt. # 142 at 15. The FTC argues that, by its plain terms “this 5 proceeding” refers to documents produced during this lawsuit and not to documents produced 6 during the investigation. Dkt. # 145 at 4. 7 The Court agrees with the FTC. The order applies to documents produced during this 8 lawsuit, and not documents produced during the pre-suit investigation.4 Neither side cites legal 9 authority on what constitutes a “proceeding” under a Rule 502(d) order. Black’s Law Dictionary 10 provides as its primary definition of the term: “[t]he regular and orderly progression of a lawsuit, 11 including all acts and events between the time of commencement and the entry of judgment.” 12 Proceeding, Black’s Law Dictionary (12th ed. 2024). It does not provide a definition that would

13 cover a lawsuit and its underlying investigation. Id. The order applies to documents produced 14 during this litigation and does not apply to documents produced in the underlying investigation 15 16

17 3 The parties seem to disagree as to whether the redacted version of IC-37 was produced before this litigation. Dkt. ## 142 at 15 n.7; 145 at 4 n.2. The FTC says that Amazon produced IC-37 in 18 February 2023, before this lawsuit was filed. Dkt. ## 145 at 4 n.2; 140-1 at 6. FTC investigator Adam Rottner says, “On February 7, 2023, Amazon clawed back Amazon-FTC-CID_09389533 (IC-37), which originally had been produced without redactions. My understanding is that on February 14, 2023, 19 Amazon produced a new copy of this document, with privilege redactions.” Dkt. # 140-2 at 5. Amazon says that “IC-37 was clawed back and produced to the FTC on January 22, 2024—after the start of this 20 case.” Dkt. # 142 n.7; Dkt. # 143 at 50. This case was filed on June 21, 2023. See Dkt. # 1. While Amazon is correct that the current redacted version of the document was clawed back during this 21 litigation, the document was produced, clawed back, and produced with redactions during the Dark Patterns Investigation, and thus the order under Rule 502(d) does not apply to IC-37. 22 4 Even if the Rule 502(d) order applied to documents produced in the Dark Patterns Investigation, it clearly does not apply to documents produced in Investigations 1 and 2. Some versions of the May 4 23 memo, the July 14 memo, IC-37, and IC-40 were produced in Investigations 1 and 2. The only categories of documents that were produced solely in the Dark Pattern Investigation were IC-27, IC-9, and the July 24 14 presentation. 1 or in other proceedings. This tracks the Court’s intention with respect to the order. Thus, the 2 order does not protect Amazon’s disclosures from waiver. 3 2. Rule 502(b) Exception to Waiver

4 When a party inadvertently discloses a document, that “disclosure does not operate as a 5 waiver” if “(1) the disclosure is inadvertent; (2) the holder of the privilege or protection took 6 reasonable steps to prevent disclosure; and (3) the holder promptly took reasonable steps to 7 rectify the error.” Fed. R. of Evid. 502(b). Each of the requirements of Rule 502(b) “are 8 separate and should not be conflated in the analysis.” Datel Holdings Ltd. V. Microsoft Corp., 9 No. C-09-05535 EDL, 2011 WL 866993, at *2 (N.D. Cal. Mar. 11, 2011). “The disclosing party 10 has the burden of proving that the elements of the rule have been met.” Columbia Cmty. Credit 11 Union v. Chicago Title Ins. Co., No. C09-5290RJB, 2009 WL 10688219, at *4 (W.D. Wash. 12 Dec. 22, 2009). 13 Amazon says that in determining whether privilege was waived, the Court should apply a 14 “totality of the circumstances” test, under which courts consider: “(1) the reasonableness of the 15 precautions to prevent inadvertent disclosure; (2) the time taken to rectify the error; (3) the scope 16 of the discovery; (4) the extent of the disclosure; and (5) the ‘overriding issue of fairness.’” U.S. 17 ex rel. Bagley v. TRW, Inc., 204 F.R.D. 170, 177 (C.D. Cal. 2001) (quoting Hartford Fire 18 Insurance Co. v. Garvey, 109 F.R.D. 323, 332 (N.D. Cal. 1985)). This test derives from cases 19 pre-dating the adoption of Rule 502(b) in 2008. Rule 502(b) takes the same “middle of the road” 20 approach as the “totality of the circumstances” test pre-dating the Rule and “the pre–2008 case 21 law remains pertinent to application of this rule.” 8 Charles Alan Wright & Arthur R. Miller, 22 Privileged Matter—Inadvertent Production of Privileged Material in Discovery, Federal Practice 23 & Procedure § 2016.3 (3d ed. 2024). But the Advisory Committee Notes for Rule 502(b) 24 1 caution that “[t]he rule does not explicitly codify [the totality of the circumstances] test, because 2 it is really a set of non-determinative guidelines that vary from case to case.” Fed. R. Evid. 502, 3 Explanatory Notes. Thus, while the Court may consider the factors laid out in the “totality of the

4 circumstances” test, it must first consider whether disclosure was in fact inadvertent. See 5 Hanson v. Wells Fargo Home Mortg., Inc., No. C13-0939JLR, 2013 WL 5674997, at *6 (W.D. 6 Wash. Oct. 17, 2013) (“The court will apply the standard codified in Federal Rule of Evidence 7 502(b) and also utilize some of the factors from the ‘totality of the circumstances approach’ in its 8 analysis.”). 9 a. Whether the disclosures were inadvertent 10 The FTC says that the disclosures of the May 4 memo (IC-1 and IC-36), the July 14 11 memo and presentation (IC-4, IC-5, IC-6, IC-17, IC-18, IC-19, IC-20, IC-21, IC-22, IC-31, and 12 IC-48), and IC-37 were not inadvertent because Amazon produced some of these documents

13 multiple times and produced the documents with redactions.5 Dkt. # 139 at 13–14. 14 Rule 502(b) does not define “inadvertent.” Courts have developed two approaches to the 15 issue. See T&W Holding Co., LLC v. City of Kemah, Texas, 641 F. Supp. 3d 378, 382 (S.D. Tex. 16 2022); Thermoset Corp. v. Bldg. Materials Corp. of Am., No. 14-60268-CIV, 2015 WL 1565310, 17 at *8 (S.D. Fla. Apr. 8, 2015). Under the first, the court simply looks to “whether the party 18 intended a privileged or work-product protected document to be produced or whether the 19 production was a mistake.’” T&W Holding Co., LLC, 641 F. Supp. 3d at 382. Under the second, 20 the court looks at factors along with a party’s subjective intent, “including the total number of 21 22 23

5 The FTC does not dispute that Amazon inadvertently produced IC-9, IC-27, and IC-40. Dkt. # 24 140-1 at 14 n.8. 1 documents reviewed, the procedures used to review the documents before production, and the 2 actions of the producing party after discovering that the documents had been produced.” Id. 3 District courts in the Ninth Circuit take the first approach. See, e.g., B&G Foods N. Am.,

4 Inc. v. Embry, No. 2:20-CV-0526 KJM DB, 2024 WL 922900, at *2 (E.D. Cal. Mar. 4, 2024) 5 (“An ‘inadvertent disclosure’ is simply where the work-product protected document was 6 produced as the result of a mistake.”); Datel Holdings Ltd., 2011 WL 866993, at *2 7 (“[I]nadvertence under the first prong does not turn on the reasonable steps taken to prevent 8 mistaken disclosure addressed in the second prong.”). The Court adopts this approach because it 9 aligns with other courts in the Circuit as well as the structure and purpose of Rule 502(b). See 10 Coburn Grp., LLC v. Whitecap Advisors LLC, 640 F. Supp. 2d 1032, 1038 (N.D. Ill. 2009) 11 (“[T]he structure of Rule 502 suggests that the analysis under subpart (b)(1) is intended to be 12 much simpler, essentially asking whether the party intended a privileged or work-product

13 protected document to be produced or whether the production was a mistake.”). 14 The FTC says that under the first approach, “a party’s having produced a document with 15 redactions is evidence of an intentional production.” Dkt. # 140-1 at 14 (citing ePlus Inc. v. 16 Lawson Software, Inc., 280 F.R.D. 247, 255 (E.D. Va. 2012)). The Court agrees. In Brown v. 17 Google LLC, the court determined that Google’s production was intentional, and not inadvertent, 18 when it “initially claim[ed] a document as privileged, then determine[d] part of the document 19 [was] not privileged and produce[d] the document in redacted form,” and later tried to claw the 20 document back. No. 20CV03664YGRSVK, 2022 WL 12039375, at *5–6 (N.D. Cal. Oct. 20, 21 2022). In ePlus Inc. v. Lawson Software, Inc., the court determined that disclosure of privileged 22 documents was not inadvertent for several reasons, including that at least one of the documents 23 was redacted. 280 F.R.D. at 255 (“The record shows that Lawson intentionally produced these 24 1 documents after reviewing them, and then realized it had mistakenly produced them.”). When a 2 party makes a strategic decision that it later regrets, such as redacting a document rather than 3 withholding it completely as privileged, it cannot later claim inadvertence to shield itself from

4 the consequences of its own judgment call. See T&W Holding Co., LLC, 641 F. Supp. 3d at 383 5 (“Kemah’s lawyers made a conscious decision to identify certain documents as those they may 6 rely on in this case, and they cannot now run away from that decision claiming mistake or 7 inadvertence.”). 8 Amazon produced three copies of the July 14 memo with redactions (IC-4, IC-17, IC-22). 9 Dkt. # 90-2 at 326–31. In one case, Amazon first withheld IC-4 completely before identifying it 10 as a document that was improperly withheld and producing it with redactions. Id. at 32–33, 277. 11 It then clawed back IC-4, along with other versions of the July 14 memo and presentation. Id. at 12 33. These actions show that Amazon’s production of this memo was purposeful.

13 Similarly, Amazon clawed back IC-37 and produced it again with redactions on February 14 14, 2023. Dkt. # 140-2 at 5. Amazon then clawed back IC-37 again on January 22, 2024, and 15 produced the document with more privilege redactions. Id. at 81. Amazon’s production of IC- 16 37 with redactions on February 14, 2023, was purposeful. Indeed, Amazon’s actions show that it 17 specifically reviewed IC-37 for privilege a second time, and made additional redactions; this 18 second production with redactions cannot be characterized as inadvertent. 19 As to the May 4 memo, Amazon produced it four times with redactions. Dkt. # 90 at 20 326–332. Amazon says that it has “claimed privilege over almost 20 copies of identical or near- 21 identical versions of the” the May 4 memo in this litigation. Dkt. # 142 at 8 (emphasis in 22 original). But Amazon cites no case in which a court considered how many versions of a 23 24 1 document were withheld when determining whether the document was produced inadvertently.6 2 In fact, Amazon does not spend any time in its brief addressing or rebutting the FTC’s arguments 3 that its disclosures were inadvertent, instead focusing on factors laid out in the totality of the 4 circumstances test. 5 Given that these documents were produced with redactions, the Court cannot determine 6 that these disclosures were merely an accident. If the party asserting privilege fails to show that 7 it meets any of the elements of Rule 502(b), then it is not entitled to the protection of Rule 8 502(b). In re Qualcomm Litig., 2018 WL 6617294, at *4. Thus, Amazon has waived its 9 privilege over the previously produced redacted versions of the May 4 memo (IC-1, IC-36), the 10 July 14 memo (IC-4, IC-17, IC-22), and IC-37. 11 Amazon produced three copies of the July 14 memo without redactions (IC-6, IC-31, IC- 12 48). Dkt. # 90-2 at 326–31. Similarly, Amazon produced all five copies of the July 14 13 presentation without redactions (IC-5, IC-18, IC-19, IC-20, IC-21). Id. at 326–28. The FTC 14 says that “a party that produces the same document multiple times generally cannot establish 15 inadvertence.” Dkt. # 140-1 at 13–14 (citing T&W Holding Co., LLC, 641 F. Supp. 3d at 380). 16 But Rule 502(b) was intended to allow for some mistakes, especially with the large volume of 17 documents produced with the rise of electronic discovery. See Fed. R. Evid. 502, Explanatory 18 19 6 The Court identified one case, In re Zetia (Ezetimibe) Antitrust Litigation, in which a court 20 determined that disclosure of redacted documents was inadvertent because the party “withheld as entirely privileged several other documents that were identical or similar to the [clawed back documents at 21 issue].” No. 2:18MD2836, 2019 WL 6122012, at *8 (E.D. Va. July 16, 2019). There, the court noted that “it is logically inconsistent to conclude that [the party] both intentionally produced and withheld the same 22 document.” Id. “[B]ecause [the party] withheld all but one such copy, the most reasonable explanation is that the single production was contrary to [the party’s] intent – or inadvertent.” Id. But this case explicitly takes the second approach to the inadvertence analysis, which courts in the Ninth Circuit do not 23 use. In addition, Amazon, as the party asserting privilege bears the burden of proving that its disclosures were inadvertent under Rule 502(b). Amazon does not meet its burden of showing that its disclosures of 24 the May 4 memo was inadvertent. 1 Notes; see also Amobi v. D.C. Dep’t of Corr., 262 F.R.D. 45, 53 (D.D.C. 2009) (defining 2 “inadvertent” “to mean an unintended disclosure,” but declining to determine that a disclosure 3 was intentional just because the disclosure was reviewed by an attorney because attorneys can

4 make mistakes). In this case, where more than 1.7 million documents were produced, the mere 5 fact that a document was produced more than once does not show that the disclosure was 6 purposeful. 7 b. Whether Amazon took reasonable steps to prevent the disclosures 8 The FTC says that Amazon did not take reasonable steps to prevent production of one 9 copy of July 14 memo, IC-31, and IC-37. Dkt. # 145 at 6, Dkt. # 139 at 15. 10 The FTC says that Amazon did not take reasonable steps to prevent disclosure of IC-31 11 because Amazon produced the document in a set of six documents. Dkt. # 140-1 at 15. The 12 FTC argues that because this production was small, Amazon cannot show that it took reasonable 13 steps to prevent inadvertent disclosure. Id. (citing Williams v. D.C., 806 F. Supp. 2d 44, 49 14 (D.D.C. 2011)). 15 16 But courts look at the overall context of production when determining whether the 17 disclosing party took reasonable steps to prevent disclosure. See Fed. R. Evid. 502, Explanatory 18 Notes (“Other considerations bearing on the reasonableness of a producing party’s efforts 19 include the number of documents to be reviewed and the time constraints for production.”); 20 Datel Holdings Ltd., 2011 WL 866993, at *4 (“Inadvertent production of a relatively low 21 proportion of documents in a large production under a short timetable due to mistake should be 22 and usually is excused.”). 23 24 1 Amazon explains that it “‘implemented a thorough, multi-step review process’ to review 2 documents for responsiveness and privilege, and followed a ‘holistic approach to assessing 3 privilege’ that ‘did not rely on any single indicia of privilege, such as the inclusion of the words

4 ‘privileged and confidential,’ to determine whether to withhold or redact a document.’” Dkt. # 5 142 at 16 (quoting Dkt. # 53 at 2). Further, Amazon produced IC-31 in Investigations 1 and 2, 6 where it produced over a million documents. Dkt. # 90-2 at 34. Given the overall scope of this 7 production and Amazon’s description of its efforts to review each document for privilege, 8 Amazon demonstrates that it took reasonable steps to prevent the disclosure of IC-31. 9 As for IC-37, the Court has already determined that Amazon’s disclosure was not 10 inadvertent, so it need not consider whether Amazon took reasonable steps to prevent disclosure 11 of that document. The FTC does not argue that Amazon did not take reasonable steps to prevent 12 disclosure of IC-9, IC-27, IC-40, and the July 14 presentation (IC-5, IC-18, IC-19, IC-20, IC-21).

13 c. Whether Amazon took prompt action 14 The FTC says that Amazon waived privilege over IC-31, IC-40, and IC-27 by waiting too 15 long to claw the documents back after it became aware that the materials had been produced.7 16 Dkt. # 140-1 at 16. 17 Rule 502(b)(3) requires the party asserting privilege to “promptly take reasonable steps to 18 rectify the error.” The party must “follow up on any obvious indications that a protected 19 20 7 The FTC also argues that Amazon did not claw back the July 14 presentation quickly enough. 21 Dkt. # 140-1 at 16. Amazon waited 18 days to claw back the memo after the FTC used IC-31 at an investigational hearing. Id.; Dkt. # 90-2 at 33–34. Amazon says that during its review process of the July 22 14 memo, it discovered that the July 14 presentation had also been produced. Dkt. # 142 at 10. Amazon says that its review to determine whether other privileged documents were inadvertently disclosed “took, at most, several weeks to complete.” Dkt. # 143 at 23. Thus, although the Court does not know the exact 23 date that Amazon discovered that it disclosed the July 14 presentation, Amazon has met its burden of showing that it “promptly took reasonable steps to rectify the error” in disclosing the July 14 presentation. 24 Fed. R. of Evidence 502(b). 1 communication or information has been produced inadvertently.” AdTrader, Inc. v. Google 2 LLC, 405 F. Supp. 3d 862, 866 (N.D. Cal. 2019) (quoting Fed. R. Evid. 502, Explanatory Notes). 3 Courts in the Ninth Circuit “have emphasized that claw back requests should be made

4 immediately, with delays of even a few weeks determined to be too long.” Skansgaard v. Bank 5 of Am., N.A., No. C11-0988 RJB, 2013 WL 828210, at *3 (W.D. Wash. Mar. 6, 2013) 6 (determining that a two-month delay was not prompt); see also AdTrader, Inc. v. Google LLC, 7 405 F. Supp. 3d 862, 866 (N.D. Cal. 2019) (determining that a seven-month delay was not 8 prompt); Contreraz v. City of Tacoma, No. 3:22-CV-5106, 2023 WL 4174659, at *5 (W.D. 9 Wash. June 26, 2023) (determining that 175-day delay was not prompt); Xu v. FibroGen, Inc., 10 No. 21-CV-02623-EMC, 2023 WL 3475722, at *3 (N.D. Cal. May 15, 2023) (determining that 11 an 11-day delay was not prompt); Mycone Dental Supply Co Inc v. Creative Nail Design Inc, No. 12 C-12-00747-RS (DMR), 2013 WL 4758053, at *3 (N.D. Cal. Sept. 4, 2013) (determining that a

13 49-day delay was not prompt). 14 But the “waiver analysis is not mechanical; rather, it considers the entire circumstances 15 surrounding the inadvertent disclosure.” Xu, 2023 WL 3475722, at *3. Further, courts “d[o] not 16 consider the time period in a vacuum,” and instead consider the circumstances surrounding the 17 time it takes a party to claw back a document, including whether the other party has relied on the 18 document when making its case. Weir v. United Airlines, Inc, No. 19 CV 7000, 2021 WL 19 1517975, at *15 (N.D. Ill. Apr. 16, 2021). 20 As for IC-31, Amazon waited 18 days after learning about the production at an 21 investigational hearing to claw the document back. Dkt. # 90 at 33–34. For IC-40, Amazon 22 waited 49 days after learning about the production at an investigational hearing to claw the

23 document back. Dkt. # 90-2 at 35. For IC-27, Amazon waited 21 days after learning about the 24 production at an investigational hearing to claw the document back. Dkt. # 140-2 at 4. Amazon 1 says that the time it took to claw back the documents was reasonable given the scale of 2 discovery—1.7 million documents across the various FTC investigations—and the condensed 3 timeline imposed by the FTC during the investigations. Dkt. # 142 at 18.

4 But the size of the overall production across multiple cases does not explain Amazon’s 5 long delays in clawing back IC-31, IC-40, and IC-27 since Amazon clawed back other 6 documents in this case within a few days. See Dkt. # 90-2 at 31 (clawing back the May 4 memo 7 within two days of learning that it was produced). Amazon also argues that the FTC did not 8 allow counsel to screen documents used at the hearings for privilege before the hearings. Dkt. # 9 142 at 18. But this would not have changed the timing for the claw back, it would only have 10 changed the date that the attorneys learned about the inadvertent disclosure. Thus, Amazon has 11 not met its burden of showing that delays of 18, 49, and 21 days were reasonable under the 12 circumstances. See Mycone Dental Supply Co Inc v. Creative Nail Design Inc, No. C-12-00747- 13 RS (DMR), 2013 WL 4758053, at *3 (N.D. Cal. Sept. 4, 2013) (“[A]t the least, Gel should have 14 recalled the document that was used in the deposition immediately after the deposition and then 15 conducted a more thorough and timely investigation into the rest of the production after the 16 initial clawback request.”). Because “[a]ll three elements set forth in Rule 502(b) must be met to 17 prevent a waiver of a privilege,” Amazon has waived its privilege over IC-31, IC-40 and IC-27. 18 In re Qualcomm Litig., 2018 WL 6617294, at *4 (quoting Liles v. Stuart Weitzman, LLC, No. 19 09-61448-CIV, 2010 11505149, at *2 (S.D. Fla June 15, 2010)).8 20 21 22

23 8 Amazon’s waiver of privilege for IC-31 extends to IC-6 and IC-48. When Amazon clawed these unredacted versions of the July 14 memo back, it characterized IC-6 and IC-48 as “the same (or a 24 substantially similar) document” to IC-31. Dkt. # 90-2 at 101. 1 B. In Camera Review 2 The only documents for which Amazon did not waive privilege are IC-9 and the July 14 3 presentation (IC-5, IC-18, IC-19, IC-20, IC-21).

4 The FTC argues that the Court should conduct an in camera review of the documents to 5 determine whether they are privileged. Dkt. # 140-1 at 12–13. The Ninth Circuit “has [] found 6 that in camera review is an acceptable means to determine whether disputed materials fit within 7 the privilege.” In re Grand Jury Investigation, 974 F.2d 1068, 1074 (9th Cir. 1992). Courts 8 have discretion to conduct an in camera review if the non-moving party shows a factual basis to 9 support “a reasonable, good faith belief that in camera inspection may reveal evidence that 10 information in the materials is not privileged.” Id. at 1075. 11 As for IC-9, at issue are 10 messages that Amazon redacted from a chat between two 12 non-attorneys. Dkt. ## 140-2 at 3; 52 at 9. Both sides agree that at least some messages in this 13 chat are privileged because the individuals are discussing legal advice that they received from 14 Amazon’s attorneys. Dkt. # 140-1 at 8. The FTC originally identified this document as 15 containing potentially privileged information and flagged to Amazon that it thought three of the 16 messages contained privileged information. Id. Amazon later redacted 13 messages. Id. 17 Amazon challenges these redactions based on its earlier assessment that those 10 messages were 18 not privileged. Id. at 9, 13. Amazon describes IC-9 as a chat between two non-lawyer Amazon 19 employees discussing “legal advice that [they] received from Amazon attorneys . . . relating to 20 the scope of the attorney-client privilege.” Dkt. # 52 at 9. Neither party devotes much briefing 21 to whether IC-9 is privileged. 22 23 The FTC has examined the chat and determined that some, but not all, of the messages 24 contain privileged materials. The FTC has shown a factual basis for a good-faith belief that at 1 least some of the messages that Amazon redacted from IC-9 are not privileged. The Court will 2 thus exercise its discretion to conduct an in camera review of the unredacted version of IC-9 to 3 determine whether the messages are privileged.

4 As for the July 14 presentation, the FTC says that the document’s primary purpose was to 5 make a business decision. Dkt. # 140-1 at 11. Amazon responds that the primary purpose was to 6 solicit legal advice. Dkt. # 142 at 13–14. Mark England, one of Amazon’s in-house attorneys, 7 says that the presentation was prepared to provide him and another attorney “with information 8 about specific changes that the Prime team was contemplating, so that we could provide legal 9 advice during the July 14 Meeting regarding those contemplated changes.” Dkt. # 52 at 4. But 10 the presentation was sent to 28 non-attorneys and two attorneys, and 20 non-attorneys and two 11 attorneys attended the meeting. Dkt. # 140-2 at 6. In an electronic chat between two Amazon 12 employees leading the meeting, one employee said that the purpose of the meeting was to “get

13 alignment on plan and timing of changes we have already agreed on. [W]e are trying to keep 14 things as simple as possible to get the [customer experience] to par and mainly want to get 15 feedback on approach and timing.” Dkt. # 140-2 at 140. These facts show a reasonable, good- 16 faith belief that, while two attorneys attended the meeting and may have offered legal advice, the 17 primary purpose of the meeting may not have been to solicit legal advice. See In re Grand Jury, 18 23 F.4th 1088, 1094 (9th Cir. 2021) (holding “that the ‘primary purpose’ test applies to dual- 19 purpose communications” when determining whether a document is protected by attorney-client 20 privilege). The Court will exercise its discretion to conduct an in camera review of the July 14 21 presentation to determine whether the document is privileged (IC-5, IC-18, IC-19, IC-20, IC-21). 22

24 | IV 2 CONCLUSION 3 The Court GRANTS the FTC’s Motion to Compel as to the May 4 memo, the July 14 4 memo, IC-37, IC-40, and IC-27. The Court GRANTS the FTC’s request for in camera review as 5 || to IC-9 and the July 14 presentation. The Court ORDERS Amazon to produce, by August 9, 6 |) 2024: 7 A. The May 4 memo (IC-1 and IC- 36) with the redactions that Amazon originally 8 applied when it produced those documents; 9 B. The July 14 memo (IC-4, IC-6, IC-17, IC-22, IC-31, IC-48) with the redactions that 10 Amazon originally applied when it produced those documents; 11 C. IC-37 with the redactions that Amazon applied when it produced the document on 12 February 14, 2023; and 13 D. IC-40 and IC-27 as Amazon originally produced the documents. 14 The Court further ORDERS Amazon to submit IC-9 without redactions, and the July 14 15 || presentation (IC-5, IC-18, IC-19, IC-20, IC-21), to the Court for in camera review by Wednesday 16 || August 8, 2024. 17 Dated this 1st day of August, 2024. cL ch 4. Char 19 John H. Chun United States District Judge

21 22 23 24