Burris v. J.P. Morgan Chase & Company

• Court: District Court, D. Arizona
• Decided: October 7, 2021
• Docket: 2:18-cv-03012
• Status: Unknown

Opinion

1 WO 2 3 4 5 6 IN THE UNITED STATES DISTRICT COURT 7 FOR THE DISTRICT OF ARIZONA

9 Johnny E Burris, No. CV-18-03012-PHX-DWL

10 Plaintiff, ORDER

11 v.

12 JPMorgan Chase & Company, et al.,

13 Defendants. 14 15 INTRODUCTION 16 Plaintiff Johnny Burris (“Plaintiff”) worked as a financial advisor for J.P. Morgan 17 Chase & Co. and J.P. Morgan Securities, LLC (together, “Defendants”) until November 18 2012, when he was terminated. In this action, which was filed in September 2018 19 (following an array of related proceedings between the parties in other forums), Plaintiff 20 contends that he was fired for complaining about Defendants’ efforts to push investors into 21 risky, “bank managed” financial products and then improperly blacklisted from the 22 financial industry, in violation of the whistleblower retaliation provisions of the Sarbanes- 23 Oxley Act of 2002 and the Dodd-Frank Act of 2010. 24 The current issues before the Court, however, have nothing to do with whistleblower 25 retaliation. Instead, they arise from Plaintiffs’ systematic efforts to destroy electronically 26 stored information (“ESI”) from an array of phones, laptops, email accounts, and external 27 storage devices. Plaintiff’s evidence-destruction efforts took a variety of forms, including 28 the repeated use of software programs called “BleachBit” and “iShredder,” and spanned a 1 period of years, beginning before (but in anticipation of) this litigation and accelerating as 2 the litigation unfolded. Eventually, a court-appointed forensic expert was tasked with 3 investigating the scope of Plaintiff’s efforts to destroy ESI, but the day before Plaintiff 4 produced certain devices to the expert, he used wiping software on them, too. Based on 5 this and other conduct, the expert concluded, “to a reasonable degree of scientific certainty, 6 that [Plaintiff] caused Potentially Relevant ESI to be irrevocably lost from his Electronic 7 Media.” (Doc. 73-1 at 3.) 8 Following the issuance of the expert’s report, Defendants filed a motion for 9 terminating sanctions. (Docs. 78 [sealed], 84 [unsealed].) That motion, as well as 10 Plaintiff’s motion for leave to belatedly submit certain exhibits in opposition to the 11 sanctions motion (Doc. 92), are now fully briefed and ripe for resolution. For the reasons 12 that follow, Defendants’ motion is granted, Plaintiff’s motion is denied, and this action is 13 terminated. 14 BACKGROUND 15 I. Background Allegations 16 The background details of this case, which taken from Plaintiff’s complaint (Doc. 17 1) and the parties’ Rule 26(f) report (Doc. 19), are as follows. 18 On June 21, 2010, Plaintiff was hired as a financial advisor associate in Defendants’ 19 Sun City West, Arizona branch. (Doc. 1 ¶ 10.) After his hiring, Plaintiff contends that he 20 was “directly pressured by several managers” to sell certain financial products that 21 Defendants managed. (Id. ¶ 14.) Specifically, Plaintiff contends that, in or before January 22 2012, he “raised concerns” to his superiors that “Defendants were misleading customers 23 by falsely claiming that sales advice to client[s] was based on suitability for their portfolios 24 rather than on Defendants’ own self-interests.” (Id. ¶¶ 30-31.) Plaintiff further contends 25 that, in June and July 2012, he raised concerns about the appropriateness of certain 26 financial products for “his elderly and conservative clients.” (Id. ¶¶ 32-34.) Plaintiff also 27 contends that, in October 2012, he “informed” a superior “that bank-managed products 28 were not appropriate for his clients.” (Id. ¶ 35.) 1 In November 2012, Plaintiff was suspended and then terminated by Defendants. 2 (Id. ¶¶ 40-41.) Plaintiff contends that, “[a]fter being terminated from his employment, [he] 3 made disclosures to the SEC of comprehensive information describing how [Defendants 4 were] ‘pushing’ or ‘steering’ clients into [Defendants’] mutual funds. Plaintiff did so 5 through his Tip, Complaint, and Referral form (TCR) dated December 6, 2012, and 6 subsequent supplementations on and after February 6, 2013.” (Id. ¶ 66.) 7 Plaintiff contends that, at an unspecified point, Defendants acted “outside company 8 procedures” by “inappropriately reduc[ing] three oral customer complaints [against 9 Plaintiff] to writing.” (Id. ¶ 42.) Plaintiff further contends that, in June 2013, Defendants 10 listed at least one of those complaints “in Plaintiff’s FINRA BrokerCheck records.” (Id.) 11 According to Plaintiff, this “had the effect of blacklisting Plaintiff and causing him 12 reputational harm because BrokerCheck reports are publicly available information to 13 potential investors and employers regarding alleged misconduct by a broker or sales agent 14 such as Plaintiff.” (Id.) 15 Based on these and other allegations, Plaintiff asserts the following claims against 16 Defendants: (1) discrimination in violation of § 806 of the Sarbanes-Oxley Act of 2002 (id. 17 ¶¶ 54-64); and (2) discrimination in violation of § 922 of the Dodd-Frank Act of 2010 (id. 18 ¶¶ 65-67.) In the Rule 26(f) report, Plaintiff summarizes his theory of liability as follows: 19 Plaintiff alleges that he was wrongfully terminated from his employment, and thereafter blacklisted by the Defendants. Plaintiff alleges his termination 20 and blacklisting were motivated in whole or in part because Plaintiff objected 21 to pushing proprietary J.P. Morgan Private Bank Managed Accounts, Chase Strategic Portfolio Managed Accounts, and proprietary mutual funds into his 22 clients’ portfolios on the grounds that he viewed such “bank managed 23 products” as not always suitable for his retired clients. After he was wrongfully terminated, Defendants blacklisted Plaintiff by drafting three 24 false customer complaints that were then sent to the Financial Industry 25 Regulatory Authority (FINRA) and made public. 26 (Doc. 19 at 2.) As remedies, Plaintiff seeks, inter alia, reinstatement or front pay, back 27 pay, economic damages of at least $1 million, and non-economic damages of $1 million. 28 (Doc. 1 at 21-22.) 1 II. Related Proceedings 2 A. The FINRA Arbitration 3 In January 2013—that is, about two months after his termination—Plaintiff filed a 4 statement of claim against Defendants with FINRA. (Doc. 78-39 at 2.) In that proceeding, 5 Plaintiff eventually asserted claims for wrongful termination, breach of contract, 6 defamation, and intentional interference with contract/prospective economic advantage. 7 (Id. at 3.) 8 In August 2014, following a two-week arbitration proceeding, the FINRA 9 arbitration panel denied Plaintiff’s claims in their entirety. (Id. at 4-9.) 10 B. The OSHA Proceeding 11 In April 2013, Plaintiff filed a whistleblower claim against Defendants with the 12 Occupational Safety and Health Administration (“OSHA”). (Doc. 1 ¶¶ 2, 4; Doc. 84 at 4 13 n.5.) 14 In January 2017, an OSHA administrator made a preliminary finding in Plaintiff’s 15 favor, which Plaintiff characterizes as a finding of “reasonable cause to believe that 16 Defendants violated SOX in both terminating and blacklisting the Plaintiff” (Doc. 1 ¶ 2) 17 and which Defendants characterize as “a non-binding, preliminary determination in favor 18 of [Plaintiff]” (Doc. 84 at 5 n.4). According to Defendants, the OSHA administrator “also 19 determined that Defendants would have been justified in terminating [Plaintiff] by March 20 2013.” (Doc. 84 at 4 n.5.) 21 Following the OSHA administrator’s ruling, “[a]ll parties appealed, but [Plaintiff] 22 opted to bring his claims before this Court.” (Id.) 23 C. The FINRA Disciplinary Proceeding 24 In September 2016, FINRA initiated a disciplinary proceeding against Plaintiff. 25 (Doc. 78-40 at 2.) The complaint alleged that Plaintiff engaged in the following forms of 26 misconduct while employed by Defendants: (1) failing to execute a customer trade request; 27 (2) attempting to settle a customer complaint related to the unexecuted trade without 28 notifying Defendants; and (3) engaging in unauthorized communications in the course of 1 the settlement effort by sending letters to customers and the IRS using “letterhead that 2 appeared to be official, firm-sanctioned . . . letterhead even though it was not.” (Id. at 3- 3 9.) 4 In April 2017, Plaintiff submitted an offer of settlement in which he “consented, 5 without admitting or denying the allegations . . . , to the entry of findings and violations 6 consistent with the allegations.” (Id. at 2.) FINRA accepted Plaintiff’s offer, entered 7 findings consistent with its allegations, and imposed sanctions against Plaintiff. (Id. at 9.) 8 III. Relevant Procedural Background 9 On September 24, 2018, Plaintiff initiated this action by filing the complaint. (Doc. 10 1.) 11 On October 1, 2019, the Court granted the parties’ stipulated protective order, which 12 sought to “facilitate document production and disclosure and to protect the respective 13 interests of the parties in their confidential information.” (Doc. 30 at 1.) 14 On March 18, 2020, the Court granted the parties’ request to adopt the first 15 addendum to the stipulated protective order, which allowed third-party service providers 16 to produce certain records and information pertaining to Plaintiff. (Doc. 35.) 17 On October 29, 2020, the Court granted the parties’ request to adopt the second 18 addendum to the stipulated protective order. (Doc. 61.) The second addendum called for 19 the appointment of “an independent expert qualified in digital forensics and electronic 20 discovery” to “serve as an Officer of the Court.” (Doc. 61 at 3.) It also ordered Plaintiff 21 to “provide the expert and Defendants a list identifying all his Electronic Media that at any 22 point contained Potentially Relevant ESI.” (Id. at 4.) The expert was instructed, upon 23 Defendants’ request, to “investigate and advise the parties and/or the Court whether . . . 24 Potentially Relevant ESI was deleted, manipulated, removed from, or concealed from 25 detection on Plaintiff’s Electronic Media.” (Id. at 5-6.) Plaintiff was warned that 26 “Defendants may seek . . . appropriate sanctions up to and including default . . . if Plaintiff: 27 unreasonably fails to identify or provides misleading information concerning his Electronic 28 Media and Potentially Relevant ESI; obstructs, attempts to evade, or unduly delays the . . . 1 efforts as provided herein; deleted or failed to preserve Potentially Relevant ESI while 2 under a duty to preserve it; or engaged in any other discovery misconduct.” (Id. at 8.) 3 On April 22, 2021, the parties submitted the forensic report from the court- 4 appointed expert. (Doc. 73-1.) The report had last been updated on April 8, 2021. (Id. at 5 1.) The parties also advised the Court that Defendants would be filing an opposed motion 6 for case-terminating sanctions based on the findings in the report. (Doc. 73 at 2.) 7 On April 29, 2021, the Court issued the revised Rule 16 case management order. 8 (Doc. 77.) Among other things, it provided that “Defendants’ Motion for Sanctions shall 9 be filed no later than July 9, 2021; Response shall be filed no later than July 30, 2021; 10 Reply shall be filed no later than August 13, 2021.” (Id. at 3.) 11 On July 9, 2021, Defendants filed their motion for sanctions. (Doc. 78.) Although 12 it was initially filed with redactions, an unsealed version was later filed. (Doc. 84.) 13 On August 3, 2021, after obtaining an extension (Docs. 86, 87), Plaintiff filed an 14 opposition to the motion for sanctions. (Doc. 89.) 15 On August 15, 2021, Plaintiff filed a motion for leave to file omitted exhibits. (Doc. 16 92.) 17 On August 16, 2021, Defendants filed an opposition to the motion for leave to file 18 omitted exhibits. (Doc. 97.) That same day, Plaintiff filed a reply in support of the motion 19 for leave to file omitted exhibits. (Doc. 98.) 20 On August 17, 2021, Defendants filed a reply in support of their motion for 21 sanctions. (Doc. 99.) Neither side requested oral argument or an evidentiary hearing as to 22 either of the motions. 23 DISCUSSION 24 I. Motion To File Omitted Exhibits 25 Although the sanctions motion was filed first, Plaintiff’s motion for leave to file 26 omitted exhibits will affect the evidence the Court can consider as part of the sanctions 27 motion. Thus, the Court begins there. 28 … 1 A. Background 2 During the forensic review process, over 700 document artifacts were recovered 3 from the “recycle bin” folders of Plaintiff’s electronic devices. (Doc. 73-1 at 21.) Notably, 4 “many of the original files that generated these artifacts had file names and pathing that 5 made them likely relevant and responsive to [Defendants’] discovery requests.” (Id.) As 6 a result, Defendants asked the court-appointed expert to answer a series of questions and 7 conduct additional analysis concerning the recovered artifacts. (Id. at 21-23.) Among 8 other things, Defendants asked if the expert could “recover the original files in [Plaintiff’s] 9 $Recycle.Bin . . . and re-run our [list of keyword] searches across the recovered files.” 10 (Id.) 11 In the updated report issued on April 8, 2021, the expert answered this question as 12 follows: (1) the 700+ artifacts were associated with “528 unique files”; (2) of the 528 13 unique files, 290 “were presumably already included in the searching that [was previously] 14 performed”; (3) of the remaining 238 files, “file record references were found to 206 that 15 were overwritten but had been present at one time on one or more of the devices. Those 16 206 items are noted in the ‘Overwritten’ Column”; and (4) as for the remaining 32 files, 17 they were “found only as references in the $Recycle.Bin folder and nowhere else on the 18 devices. These 32 items are noted in the ‘Not Found’ column.” (Id. at 23.) 19 In their motion for sanctions, filed on July 9, 2021, Defendants identified the 20 “recycle bin” evidence as one of the many grounds of which their sanctions request was 21 premised. Specifically, Defendants emphasized that Plaintiff “moved hundreds of files 22 that ‘hit’ on relevant case search terms into the Recycle Bin, many of which could never 23 be recovered and were later identifiable only by file name” and “‘recycled’ at least 49 files 24 [on October 30, 2020] that hit on searches for Potentially Relevant ESI and continued to 25 delete at least 289 other similar files through December 7, 2020, with many files 26 unrecoverable because they were ‘overwritten.’” (Doc. 84 at 6, 9.) 27 On August 3, 2021, Plaintiff filed his response to Defendants’ motion. (Doc. 89.) 28 In his statement of facts, Plaintiff included a section with the heading “The Files Recovered 1 Are Not Relevant ESI and [Defendants Offer] No Proof, Only Speculation, That They 2 Were.” (Id. at 10.) Underneath this hearing, Plaintiff alluded to a “Table 1” that was 3 purportedly attached to his brief. (Id.) Plaintiff described Table 1 as providing as follows:

4 Of those alleged “Overwritten” or “Not Found” files that were allegedly 5 “gone forever”, the vast majority of said files are either already produced to JPM or in fact not relevant ESI. Many of these documents were renamed or 6 misspelled, which made the material seem either overwritten or not found 7 but was in fact there. This Table shows this was not the product of some intentional act of Plaintiff to delete or hide files. 8

9 (Id.) However, Table 1 was not actually included as an exhibit to Plaintiff’s brief. 10 On August 15, 2021—two days before Defendants’ reply in support of the sanctions 11 motion was due—Plaintiff lodged a copy of Table 1 (as well as two other exhibits that were 12 referenced in Plaintiff’s response brief but not attached thereto) and asked that these 13 “omitted” exhibits be deemed timely filed. (Doc. 92.) 14 B. The Parties’ Arguments 15 Plaintiff’s only proffered justification for his failure to file Table 1 by the August 3, 16 2021 deadline is “good medical and logistical cause as described in the attached declaration 17 of lead counsel, Thad M. Guyer.” (Doc. 92 at 3.) In that declaration, Mr. Guyer 18 (“Counsel”) states that he “was diagnosed with a condition requiring a rebalancing of 19 medications which has resulted in a temporary diminution of the number of hours per week 20 [he can work] . . . . This has resulted in errors in projecting the number of days and hours 21 a case segment or legal project may require.” (Doc. 96 ¶ 2.) Counsel also states that 22 “[a]fter reviewing [Defendants’] Motion for Sanctions on July 10, 2021,” he discovered 23 flaws in the expert reports and “tasked [his co-counsel] Ms. Ayers to work with [Plaintiff] 24 to create a table” that would show those flaws. (Id. ¶ 4.) After Plaintiff submitted a first 25 draft of the table, Ms. Ayers “then timely submitted” a second draft. (Id.) Counsel believed 26 that the draft was “long and lack[ing] practical navigation and sorting capability” and 27 decided that an acceptable draft could not be “completed even by the extended filing due 28 date of August 3, 2021.” (Id. at 2-3). Counsel decided “it was better not to file . . . version 1 3 but to instead return it to Ms. Ayers to work with [Plaintiff] on version 4. After the 2 allegedly ‘missing’ files were located in duplicates within the ESI cache, [Counsel] 3 directed Ms. Ayers to work with [Plaintiff] to populate version 5.” (Id. ¶ 5.) Counsel then 4 transmitted a final version of Table 1, as well as the other two missing exhibits, to 5 Defendants. (Id. ¶ 6.) 6 Defendants oppose Plaintiff’s motion. (Doc. 97.) In a nutshell, Defendants argue 7 the motion should be denied because (1) Plaintiff cites “no procedural or substantive rule 8 or law allowing” a party to ignore a deadline simply because it wishes to keep working on 9 a document after the deadline has elapsed; (2) Plaintiff did not, upon missing the August 10 3, 2021 deadline, notify the Court or Defendants of his intention to seek leave to 11 supplement the record, and instead “spent . . . next two weeks clandestinely ‘working on’ 12 Table 1” before springing it on Defendants just before their reply was due; (3) Plaintiff 13 cannot establish good cause for failing to file Table 1 by August 3, 2021 because it is 14 responsive to a report that was issued in April 2021—meaning “Plaintiff has had months 15 to formulate his response on this issue”; and (4) at any rate, the proffered exhibits are 16 irrelevant because one doesn’t even relate to the issues raised in the sanctions motion, the 17 second is simply the full transcript of a meet-and-confer session as to which Defendants 18 previously filed a transcript except, and as for the third, “nothing in Table 1 . . . justifies, 19 or even addresses, the undisputed evidence of spoliation.” (Id. at 1-4.) 20 C. Analysis 21 Because the August 3, 2021 deadline for Plaintiff to submit his response to 22 Defendants’ sanctions motion (which was necessarily, if implicitly, also the deadline for 23 Plaintiff to submit any supporting exhibits) was established via a Rule 16 scheduling order, 24 Plaintiff’s current request—which is functionally an extension request—is governed by 25 Rule 16(b)’s “good cause” standard. Johnson v. Mammoth Recreations, Inc., 975 F.2d 26 604, 607-08 (9th Cir. 1992). “Rule 16(b)’s ‘good cause’ standard primarily considers the 27 diligence of the party seeking the amendment. . . . [C]arelessness is not compatible with a 28 finding of diligence and offers no reason for a grant of relief. . . . [T]he focus of the inquiry 1 is upon the moving party's reasons for seeking modification. If that party was not diligent, 2 the inquiry should end.” Id. at 609. 3 Here, Plaintiff was not diligent, so his request to belatedly file the three missing 4 exhibits is denied. Although the Court is sympathetic to Counsel’s health issues, Counsel’s 5 declaration does not establish that those issues were the root cause of the belated 6 submission. To the contrary, the declaration establishes that Counsel possessed a draft of 7 Table 1 before August 3, 2021, knew that the deadline was about to expire, yet still decided 8 against filing Table 1 in favor of continued drafting. This is not diligent conduct. 9 The absence of diligence is underscored by the broader context of this case. As 10 discussed above, the “recycle bin” issues were addressed at length in the court-appointed 11 expert’s report. An updated version of that report was issued in early April 2021, nearly 12 four months before Plaintiff’s opposition brief and exhibits were due. This was ample time 13 for Plaintiff to prepare a table setting forth his view of the disputed issues. 14 Nor is there any merit to Plaintiff’s contention that he “could not have anticipated” 15 the need to prepare Table 1 until he reviewed Defendants’ sanctions motion, which 16 purportedly contained an “inapposite characterization” of whether “a subset of the 528 17 recycle bin files [w]as ‘irrevocably lost.” (Doc. 92 at 4.) Plaintiff had fair notice, based on 18 the findings and statements in the expert’s report, that he would need to be prepared to 19 address the “recycle bin” issues by the time he responded to Defendants’ sanctions motion, 20 regardless of the precise nature of the claims they made in that motion. It was not diligent 21 for Plaintiff to wait until the very end of this four-month window to begin preparing the 22 table, then decline to file it on the filing deadline (even though a version was available for 23 filing) simply because he believed it could profit from some additional fine-tuning. 24 Counsel’s otherwise-admirable perfectionism is not an excuse, much less “good 25 cause,” for ignoring a deadline without requesting an extension of time. Most lawyers 26 would appreciate more time to hone an argument or perfect an exhibit, but granting an 27 exception on those grounds would swallow the rule. 28 Finally, in an abundance of caution, the Court notes that it has reviewed the lodged 1 exhibits (Docs. 92, 93, 94) alongside the court-appointed expert’s second memorandum of 2 findings. (Doc. 101-1.) In the second memorandum, the expert opines that Table 1 does 3 not materially change any of the conclusions set forth in the earlier report. (Id. at 2.) The 4 Court agrees. Thus, even Plaintiff had been allowed to belatedly submit the missing 5 exhibits, the Court’s ultimate conclusions set forth in Part II below would not change. 6 II. Motion For Sanctions 7 A. Facts Regarding Spoliation 8 As noted, the court-appointed expert issued his updated report on April 8, 2021. 9 (Doc. 73-1.) It includes the following summary of Plaintiff’s spoliation-related conduct, 10 grouped here by device type: 11 ▪ iPhones: The report concludes that Plaintiff “factory reset every one of his [six] 12 previous iPhones, thereby permanently deleting the content of each device. [Plaintiff] 13 stated that he did this on all of his prior iPhones so that other family members could use 14 the devices, despite the fact that none of these devices appear to have been used after their 15 factory reset. Had [Plaintiff] simply stored the phones without resetting them, we would 16 be able to access all historical text messages (and other data) contained on the devices.” 17 (Id. at 2.) The report identifies the dates of the factory resets for Plaintiff’s six iPhones as 18 (1) December 29, 2016; (2) January 1, 2017; (3) September 16, 2017; (4) October 14, 2018; 19 (5) November 19, 2020; and (6) February 7, 2021. (Id. at 5.) In addition to these factory- 20 reset efforts, the report concludes that Plaintiff purchased and used iShredder, “a program 21 specifically designed to destroy data,”1 on his iPhone “possibly as early as [August 27, 22 2018] and as recently as [December 7, 2020].” (Id. at 2.) 23 ▪ Laptops: The report concludes that Plaintiff “performed resets of both of the 24 laptops he provided for imaging in this matter. These resets likely occurred in September 25 and October of 2020.” (Id. at 2.) The report also notes that, in addition to these factory- 26 1 The report explains that iShredder “advertises that it can ‘Securely Erase iPhone® 27 and iPad® incl. temporary data cleaner’ and that it will ‘securely overwrite the free space using patented security standards, making it impossible to recover any deleted data.’ This 28 iShredder iOS 4 software, like a factory reset, is designed to permanently destroy data contained on iPhones.” (Id. at 5.) 1 reset efforts, Plaintiff repeatedly used commercial software programs in an attempt to 2 delete ESI from the older of his two laptops—specifically, in August 2018, Plaintiff 3 installed and ran Bleachbit2 and iShredder (id. at 5, 16); in March 2020, Plaintiff ran “anti- 4 forensics feature of Bleachbit called ‘chaff,’ whereby the Bleachbit program creates a user 5 defined amount of gibberish files designed to fill space on the hard drive [of the older 6 laptop] and overwrite existing data” (id. at 17); and in December 2020, Plaintiff again ran 7 iShredder (id. at 5). Finally, the report concludes that Plaintiff attempted to deceive the 8 forensic examiners by passing off a laptop he did not purchase until September 2020 (and 9 which was not commercially available until June 2020) as the one of the laptops that was 10 discussed during Plaintiff’s March 2020 deposition. (Id. at 2, 14-15.) 11 ▪ Email Account: The report concludes that Plaintiff “purged the content of his 12 invst4u@cox.net email account” on several occasions after the initiation of this lawsuit, 13 with the purging occurring “as recently as ‘2 or 3 months’ prior to . . . December 5, 2020 14 . . . and likely also prior to the April 21, 2020 Cox Subpoena response.” (Id. at 2.) The 15 report further identifies various “instances where email PST files had been moved to the 16 Recycle Bin,” with one such move occurring in May 2019 and another in February 2020. 17 (Id. at 13.) Finally, the report concludes that Plaintiff made false representations during a 18 December 2020 conversation related to the forensic review, by claiming that “he stopped 19 using the invst4u@cox.net email account in 2017,” because other pieces of evidence 20 established that Plaintiff “was using the invst4u@cox.net email address” until at least 21 February 2, 2020 and possibly as late as August 26, 2020. (Id. at 14.) 22 ▪ External Storage Devices: The report explains that “[d]uring the forensic 23 examination of the two laptops that [Plaintiff] provided . . . , a number of USB drive[s] 24 were identified that had not been provided for examination.” (Id. at 2.) Plaintiff 25 2 The report explains that Bleachbit “is advertised as a privacy solution that erases 26 many tracks left by a user on his computer and has features specifically designed to thwart forensic examinations. Bleachbit has a file/folder shredding capability, as well as the 27 ability to wipe the entire unused space of a hard drive, thereby removing all previously deleted data. BleachBit has a particularly troubling anti forensics feature that allows a user, 28 when running Bleach Bit, to have the program erase any indications that it was ever run . . . .” (Doc. 73-1 at 15-16.) 1 subsequently provided two USB drives on March 16, 2021. (Id.) The ensuing forensic 2 review of these USB drives revealed that the “unused space . . . where previously deleted 3 data/files would normally reside (and generally be available for forensic examination) was 4 wiped using software designed to destroy data.” (Id. at 2-3.) Both devices were wiped on 5 March 15, 2021—that is, the day before Plaintiff produced them for examination. (Id.) 6 ▪ Text Messages: The report concludes that Plaintiff “failed to preserve any of his 7 text messages from prior to [October 30, 2020]. This was due to either intentional deletion 8 or a lack of confirmation by [Plaintiff] that his messages were being completely transferred 9 from one device to the next. . . . [Plaintiff also] failed to provide the correct password to 10 open an ITunes backup of his iPhone 11 created on [October 30, 2018]. This backup would 11 likely contain historical text messages from prior to [October 30, 2020].” (Id. at 2.) 12 Defendants proffer the factual findings in the expert’s report, which they describe 13 as “unchallenged,” in support of their sanctions motion. (Doc. 84 at 1, 2, 7-9.) Plaintiff, 14 in turn, does not address (let alone dispute) most of the facts set forth above. To the 15 contrary, and as discussed in more detail below, Plaintiff seems to acknowledge that he 16 engaged in the conduct described in the expert’s report and simply argues that his conduct 17 was not sanctionable because the devices at issue did not contain ESI that was potentially 18 relevant to this litigation. (See, e.g., Doc. 89 at 4 [“[Plaintiff] was not under any prohibition 19 from deleting, moving, or renaming his own personal or professional information, and he 20 had no obligation to produce equipment that was not involved in housing or creating 21 potentially relevant ESI.”]; id. at 7 [“Because he neither created nor stored any potentially 22 relevant ESI on his phones, there was no requirement to preserve their storage functions.”]; 23 id. at 8 [“The Use of Data Reduction Methods Are [sic] Neither Prohibited Nor 24 Nefarious.”]; id. at 10 [“The bulk of Plaintiff’s alleged ESI preservation violations argued 25 in the motion are diversionary . . . .”].) 26 Given this backdrop, the Court adopts the undisputed facts in the expert’s report and 27 makes the following factual findings: (1) Plaintiff performed factory resets of six personal 28 iPhones between December 2016 and February 2021, including several resets after the 1 commencement of this litigation in September 2018; (2) Plaintiff used iShredder on one of 2 his iPhones as early as August 2018 and as late as December 2020; (3) Plaintiff performed 3 factory resets on both of the laptops he provided for imaging in this matter, with the resets 4 likely occurring in September and October 2020; (4) Plaintiff ran Bleachbit and iShredder 5 on the older laptop in August 2018; (5) Plaintiff ran an anti-forensics feature of Bleachbit 6 called “chaff,” whereby Bleachbit creates a user defined amount of gibberish files designed 7 to fill space on the hard drive and overwrite existing data, on the older laptop in March 8 2020; (6) Plaintiff again ran iShredder on the older laptop in December 2020; (7) Plaintiff 9 attempted to deceive the forensic examiners by passing off a laptop he did not purchase 10 until September 2020 (and which was not commercially available until June 2020) as the 11 newer of the two laptops that was discussed during his March 2020 deposition; (8) Plaintiff 12 purged the content of his invst4u@cox.net email account on several occasions after the 13 initiation of this lawsuit; (9) Plaintiff moved files from the invst4u@cox.net email account 14 into his recycle bin in May 2019 and again in February 2020; (10) Plaintiff made false 15 representations during a December 2020 conversation related to the forensic examination, 16 by claiming that he stopped using the invst4u@cox.net email account in 2017, because he 17 was actually using that email address until at least February 2020 and possibly as late as 18 August 2020; (11) Plaintiff used “wiping” software on the two USB drives he provided for 19 forensic examination on March 16, 2021, including wiping both devices on March 15, 20 2021, the day before the production; (12) Plaintiff failed to preserve any of his text 21 messages from before October 30, 2020; and (13) Plaintiff failed to provide the correct 22 password to open an iTunes backup of his iPhone 11 created on October 30, 2018. 23 In the following sections of this order, the Court addresses the additional facts 24 bearing on whether this undisputed conduct may (and should) give rise to sanctions. 25 B. The Parties’ Arguments 26 Defendants seek the imposition of terminating sanctions against Plaintiff pursuant 27 to Rules 37(b)(2) and 37(e)(2) of the Federal Rules of Civil Procedure. (Doc. 84 at 1, 11- 28 17.) Defendants characterize Plaintiff’s conduct as the “mass destruction of electronically 1 stored information” and argue that the presence of bad faith can be inferred from Plaintiff’s 2 efforts to continue destroying ESI even after he was admonished by his own counsel not to 3 destroy evidence (id. at 1-2) and after a forensic expert was appointed to investigative his 4 conduct (id. at 2-3, 7-9); from Plaintiff’s use of commercial programs specifically designed 5 to hide evidence (id. at 2, 4-6); from Plaintiff’s admission, during his deposition, that one 6 of the reasons he destroyed the ESI was to prevent Defendants from obtaining his “client 7 data,” which was specifically designated as a potentially relevant subject area in a court 8 order (id. at 9-10); and from Plaintiff’s repeated lies under oath when questioned about his 9 spoliation of evidence (id. at 10-11). Defendants also note that, although Plaintiff testified 10 during his deposition that he engaged in the challenged conduct in an effort to hide 11 embarrassing, but irrelevant, information concerning pornography viewing and 12 extramarital affairs, those excuses ring hollow because information concerning those topics 13 would not have appeared on Plaintiff’s laptops and flash drives. (Id. at 10.) Defendants 14 conclude by identifying an array of cases in which terminating sanctions were imposed 15 under Rules 37(b)(2) and 37(e)(2) for similar conduct. (Id. at 11-17.) 16 In his response, Plaintiff does not seriously dispute that he deleted ESI from his cell 17 phones, laptops, and USB devices, purged his email account, and failed to preserve his text 18 messages. Instead, Plaintiff’s essential argument is that sanctions are unwarranted because 19 none of the deleted ESI was potentially relevant to this litigation and none of his actions 20 were taken in bad faith. According to Plaintiff, “ninety-five percent of the volume of 21 documents involved in this case were created in 2011-2012 and exchanged by both parties 22 at the time of the 2014 [FINRA] arbitration.” (Doc. 89 at 1-2.) In a related vein, Plaintiff 23 argues that the FINRA arbitration proceeding, OSHA proceeding, and other related 24 proceedings generated a huge volume of discovery materials, that Defendants expressed 25 satisfaction with Plaintiff’s disclosure efforts during those proceedings, and that 26 Defendants only “[s]uddenly” began raising concerns about discovery issues after they 27 failed to prevail in the OSHA proceeding. (Id. at 2-4.) Next, Plaintiff offers a series of 28 arguments in somewhat scattershot fashion. First, Plaintiff disputes the relevance of certain 1 deleted documents that were recovered during the forensic review, arguing that because 2 most of the documents were “dated post-termination,” they have “tangential, if not 3 questionable, relevance on their face to this Sarbanes-Oxley claim.” (Id. at 4-6.) Next, 4 Plaintiff contends that his good faith can be inferred from the fact that he voluntarily agreed 5 to the forensic examination of his devices, even though “his counsel advis[ed] he had a 6 good chance of defeating a compelled motion [for] forensic examination.” (Id. at 6-7.) 7 Next, Plaintiff emphasizes that the stipulated protected order did not require him to 8 “provide every piece of equipment he had,” and instead only compelled him “to produce 9 media that contained or previously contained ‘potentially relevant ESI,’” and suggests that 10 his phones did not contain any such material. (Id. at 7.) Plaintiff also takes issue with the 11 forensic expert’s failure to define certain terms in the report, such as the terms “unallocated 12 space” and “factory reset” (Id. at 7-8.) As for the use of BleachBit and iShredder, Plaintiff 13 characterizes them as “common space spacing and performance enhancing apps” and 14 criticizes the expert for “attempt[ing] to paint” his use of such apps as “nefarious.” (Id. at 15 8-9.) Next, as for whether the deleted ESI was potentially relevant to this litigation, 16 Plaintiff argues that neither the expert nor Defendants have “identified (a) any type of 17 employment documents, (b) category of protected activity, adverse action, causation or 18 employer knowledge or damages, or (c) post-arbitration date range of documents expected 19 to exist and be produced that have not been.” (Id. at 9.) Next, Plaintiff denies that his 20 attorneys took steps “to protect themselves” from the accusations of spoliation in this case 21 and criticizes the expert’s lack of responsiveness to Plaintiff’s criticisms of the initial draft 22 of the report. (Id.) Next, Plaintiff argues that Defendants’ spoliation allegations related to 23 his “Private iPhones and Email” are “Diversionary” because he didn’t use those devices to 24 transact business while employed by Defendants. (Id. at 10.) In a related vein, Plaintiff 25 disputes Defendants’ contention that recordings of relevant conversations were stored on 26 his phones. (Id. at 11.) Plaintiff concludes by arguing that the cases cited in Defendants’ 27 motion are distinguishable and that “[t]here is no precedent for an ESI dismissal sanction 28 as Defendants demand in this case.” (Id. at 11-13.) 1 In reply, Defendants argue that Plaintiff’s response “does not attempt to deny—or 2 address—the fact that, in violation of the Court’s Order setting the forensic exam, he 3 intentionally used anti-forensic software to destroy data, wiped multiple devices, failed to 4 turn in others, failed to retain any text messages predating the Court’s Order, discarded a 5 requested laptop and produced a new one in its place, and sold his iPhone on eBay and then 6 tried to pass off a new phone in its place.” (Doc. 99 at 1.) Defendants also contend that 7 although Plaintiff attempts to “replace[] his prior excuses for spoliation—i.e., destroying 8 evidence of his extramarital affair, pornography, and client data—with new excuses, such 9 as he was trying to ‘save space,’ . . . his new excuses make no sense and do not relieve him 10 of his duty to preserve and produce potentially relevant ESI.” (Id.) As for Plaintiff’s 11 assertions about the volume of discovery materials produced during the earlier 12 proceedings, Defendants contend that “[t]he totality of documents the parties collectively 13 exchanged (the vast majority of which were Defendants’ productions to [Plaintiff]) is 14 beside the point” because “the issue here is whether Burris failed to comply with this 15 Court’s orders to preserve and produce his potentially relevant ESI from his electronic 16 media in this lawsuit, as the Court’s October 29, 2020 Order, the MIDP, and the Civil Rules 17 all required him to do.” (Id. at 3, emphases omitted.) As for Plaintiff’s argument that the 18 handful of documents recovered during the forensic review were irrelevant, Defendants 19 respond that (1) the documents are relevant, and (2) their relevance is a non sequitur 20 because the other documents that Plaintiff successfully destroyed were relevant. (Id. at 3- 21 4.) As for Plaintiff’s claim of reliance on counsel, Defendants argue this claim is both 22 unsupported by the record and irrelevant. (Id. at 4.) As for Plaintiff’s “space saving” 23 explanation, Defendants argue it lacks merit because (1) Plaintiff offers no evidence that 24 his devices were running low on storage, (2) Plaintiff used the “chaff” feature of BleachBit 25 to fill the unused space on his laptops with gibberish, which is the opposite of saving space; 26 and (3) a party with preservation obligations is not, in any event, allowed to shirk those 27 obligations due to space-saving concerns. (Id. at 5.) Finally, as for Plaintiff’s claim that 28 the destroyed ESI was irrelevant, Defendants respond as follows: 1 [A]ccepting [Plaintiff’s] position that the documents he destroyed. . . were 2 not relevant would require the Court to turn a blind eye to the claims and 3 defenses at issue in this case. [Plaintiff] was terminated for violating multiple [of Defendants’] policies and FINRA Rules designed to protect customers, 4 including but not limited to concealing a customer complaint from JPMorgan 5 and attempting to resolve the complaint using fake company letterhead as well as mismarking as “unsolicited” trades that he suggested to customers. 6 After his termination, Burris continues to service some of the same clients 7 that he serviced while [employed by Defendants]. [Plaintiff] seeks damages in this lawsuit through 2033 on allegations that Defendants “caused future 8 clients . . . not to retain his services” by publicly reporting just some of the 9 customer issues that led to his termination. [Plaintiff] identified without limitation his “correspondence with clients” in his MIDP responses. Before 10 the forensic exam, he selectively produced customer statements and 11 complaints that he solicited after his termination (including after the 2014 FINRA arbitration) in an effort to bolster his claims and to undermine 12 Defendants’ reasons for terminating him in later proceedings. It defies 13 credulity for [Plaintiff] to pretend now that “client data” is not at issue in this case, and that his choice to systematically purge his devices of everything 14 but that which he alone deemed “relevant” did not prejudice Defendants. 15 (Id. at 8-9.) Put another way, Defendants argue that Plaintiff “claims that post-2012 16 documents are irrelevant, but he alleges retaliation after 2012 and damages through 2033. 17 He cannot have it both ways.” (Id. at 9.) 18 C. Legal Standard 19 As noted, Defendants seek the imposition of terminating sanctions under both Rule 20 37(b)(2) and Rule 37(e)(2). The Court will address Rule 37(e)(2) because it specifically 21 contemplates the imposition of sanctions based on the loss of ESI.3 22 Rule 37(e) was “completely rewritten” in 2015 to “provide[] a nationally uniform 23 standard for when courts can give an adverse inference instruction, or impose equally or 24 more severe sanctions, to remedy the loss of ESI.” 1 Gensler, Federal Rules of Civil 25 Procedure, Rules and Commentary, Rule 37, at 1194 (2021). The text of Rule 37(e)(2) 26

27 3 Because, as discussed below, the Court ultimately concludes that terminating sanctions are warranted under Rule 37(e)(2), this order does not separately address the 28 standards and elements applicable under Rule 37(b)(2). The Court clarifies, however, that it also would have imposed terminating sanctions under that provision. 1 now provides:

2 If electronically stored information that should have been preserved in the 3 anticipation or conduct of litigation is lost because a party failed to take reasonable steps to preserve it, and it cannot be restored or replaced through 4 additional discovery, the court: 5 . . . 6 (2) only upon finding that the party acted with the intent to deprive 7 another party of the information’s use in the litigation may: 8 (A) presume that the lost information was unfavorable to the 9 party; 10 (B) instruct the jury that it may or must presume the 11 information was unfavorable to the party; or 12 (C) dismiss the action or enter a default judgment. 13 14 A party seeking sanctions under Rule 37(e) has a threshold duty to show that the 15 ESI at issue was, in fact, lost or destroyed. Fed. R. Civ. P. 37(e) advisory committee’s note 16 to 2015 amendment (“The new rule applies only . . . when [ESI] is lost.”). If such a showing 17 has been made, the court must then determine whether “(1) the ESI should have been 18 preserved in the anticipation or conduct of litigation; (2) the ESI is lost because a party 19 failed to take reasonable steps to preserve it; and (3) the ESI cannot be restored or replaced 20 through additional discovery.” Porter v. City & Cnty. of San Francisco, 2018 WL 21 4215602, *3 (N.D. Cal. 2018) (cleaned up). See also Fed. R. Civ. P. 37(e) advisory 22 committee’s note to 2015 amendment (“The new rule applies only if the lost information 23 should have been preserved in the anticipation or conduct of litigation and the party failed 24 to take reasonable steps to preserve it.”). 25 If each of these questions is answered in the affirmative, the next inquiry under Rule 26 37(e)(2) is whether the nonmovant “acted with the intent to deprive another party of the 27 information’s use in the litigation.” Porter, 2018 WL 4215602 at *3. Unlike Rule 37(e)(1), 28 Rule 37(e)(2) “does not include a requirement that the court find prejudice to the party 1 deprived of the information. This is because the finding of intent required by the 2 subdivision can support not only an inference that the lost information was unfavorable to 3 the party that intentionally destroyed it, but also an inference that the opposing party was 4 prejudiced by the loss of information that would have favored its position. Subdivision 5 (e)(2) does not require any further finding of prejudice.” Fed. R. Civ. P. 37(e) advisory 6 committee’s note to 2015 amendment. 7 If such intent is found, the Court has discretion to impose any of the sanctions 8 authorized in subsections (e)(2)(A)-(C) (i.e., an adverse inference, an adverse-inference 9 jury instruction, or a terminating sanction). However, “[f]inding an intent to deprive 10 another party of the lost information’s use in the litigation does not require a court to adopt 11 any of the measures listed in subdivision (e)(2). The remedy should fit the wrong, and the 12 severe measures authorized by this subdivision should not be used when the information 13 lost was relatively unimportant or lesser measures such as those specified in subdivision 14 (e)(1) would be sufficient to redress the loss.” Id. 15 “[T]he applicable standard of proof for spoliation in the Ninth Circuit appears to be 16 by a preponderance of the evidence.” Compass Bank v. Morris Cerullo World Evangelism, 17 104 F. Supp. 3d 1040, 1052-53 (S.D. Cal. 2015). See also Singleton v. Kernan, 2018 WL 18 5761688, *2 (S.D. Cal. 2018) (“A party seeking sanctions for spoliation of evidence has 19 the burden of establishing [spoliation of nonelectronic records] by a preponderance of the 20 evidence[.]”). The Court is the appropriate finder of fact on a Rule 37(e) motion. Mannion 21 v. Ameri-Can Freight Sys. Inc., 2020 WL 417492, *4 (D. Ariz. 2020). See also Adriana 22 Int’l Corp. v. Thoeren, 913 F.2d 1406, 1408 (9th Cir. 1990) (“The imposition of discovery 23 sanctions pursuant to [Rule 37] is reviewed for abuse of discretion. Absent a definite and 24 firm conviction that the district court made a clear error in judgment, this court will not 25 overturn a Rule 37 sanction. Findings of fact related to a motion for discovery sanctions 26 are reviewed under the clearly erroneous standard. If the district court fails to make factual 27 findings, the decision on a motion for sanctions is reviewed de novo.”) (citations omitted). 28 … 1 D. Analysis 2 1. Whether ESI Was Lost 3 A party seeking sanctions under Rule 37(e) has a threshold duty to show that the 4 ESI at issue was, in fact, lost or destroyed. Fed. R. Civ. P. 37(e) advisory committee’s note 5 to 2015 amendment (“The new rule applies only . . . when [ESI] is lost.”). 6 Here, large volumes of ESI were lost. The Court has found (and Plaintiff does not 7 dispute) that Plaintiff deleted the ESI from six cell phones, two laptops, and two USB 8 devices, purged his email account, and failed to preserve his text messages. Although 9 Plaintiff disputes whether the deleted ESI was potentially relevant—an issue that is 10 addressed in Part II.D.2.b below—everybody agrees that it is gone.4 11 2. Duty to Preserve 12 Sanctions are available under Rule 37(e) only if the loss of ESI occurred at a time 13 when litigation was pending or reasonably foreseeable. Fed. R. Civ. P. Rule 37(e), 14 advisory committee’s note to 2015 amendment (“The new rule applies only if the lost 15 information should have been preserved in the anticipation or conduct of litigation . . . 16 Many court decisions hold that potential litigants have a duty to preserve relevant 17 information when litigation is reasonably foreseeable. Rule 37(e) is based on this common- 18 law duty; it does not attempt to create a new duty to preserve. The rule does not apply 19 when information is lost before a duty to preserve arises.”). Further, the ESI must have 20 been foreseeably relevant to the pending or foreseeable litigation. Id. (“Courts should 21 consider the extent to which a party was on notice that litigation was likely and that the 22 information would be relevant.”) (emphasis added). 23 a. Reasonable Foreseeability Of Litigation 24 As the Ninth Circuit has explained, parties “engage in spoliation of documents as a 25 matter of law only if they had ‘some notice that the documents were potentially relevant’ 26 4 As discussed in Part I above, Plaintiff attempted to submit evidence (in the form of 27 Table 1) to establish that some of the files found in his recycle bin could be found elsewhere. Table 1 is not properly before the Court, but even if it were, it would not change 28 the analysis—even accepting Plaintiff’s characterization of the ESI described in Table 1, there are still huge volumes of missing ESI. 1 to the litigation before they were destroyed.” United States v. Kitsap Physicians Serv., 314 2 F.3d 995, 1001 (9th Cir. 2002). “This is an objective standard, asking not whether the party 3 in fact reasonably foresaw litigation, but whether a reasonable party in the same factual 4 circumstances would have reasonably foreseen litigation.” Waymo LLC v. Uber Techs., 5 Inc., 2018 WL 646701, *14 (N.D. Cal. 2018) (internal quotation marks omitted). The 6 reasonable foreseeability of litigation “is a flexible fact-specific standard that allows a 7 district court to exercise the discretion necessary to confront the myriad factual situations 8 inherent in the spoliation inquiry. This standard does not trigger the duty to preserve 9 documents from the mere existence of a potential claim or the distant possibility of 10 litigation. However, it is not so inflexible as to require that litigation be ‘imminent, or 11 probable without significant contingencies.’” Id. at *15 (quoting Micron Tech., Inc. v. 12 Rambus, Inc., 645 F.3d 1311, 1320 (Fed. Cir. 2011)). 13 It is sometimes difficult to determine whether litigation was reasonably foreseeable 14 at the time of the challenged acts of ESI destruction. This is not such a case. Although 15 Defendants argue that Plaintiff’s “duty to preserve evidence triggered no later than Nov. 6, 16 2012,” which is the date on which Plaintiff was terminated (Doc. 84 at 14), the sanctions 17 analysis in this case ultimately does not turn on whether Plaintiff’s preservation obligations 18 arose pre-litigation. At a minimum, Plaintiff had a duty to preserve relevant documents 19 once he initiated this action in September 2018. (Doc. 1.) And as discussed in Part II.A 20 above, many of the challenged acts of spoliation occurred after that date—after the 21 initiation of litigation, Plaintiff performed factory resets on several of his phones and both 22 of his laptops; used iShredder on one of his phones; ran an anti-forensics feature of 23 Bleachbit called “chaff” on one of his laptops; ran iShredder on one of his laptops; 24 repeatedly purged the content of his invst4u@cox.net email account; repeatedly moved 25 files from the invst4u@cox.net email account into his recycle bin; used “wiping” software 26 on the two USB drives he provided for forensic examination; and failed to preserve any of 27 his text messages from before October 30, 2020. Indeed, Plaintiff engaged in much of this 28 undisputed conduct after the entry of the revised protective order on October 29, 2020 1 (Doc. 61), which gave express notice to Plaintiff that he could face sanctions based on the 2 deletion of ESI. 3 b. Reasonable Foreseeability Of The Relevance Of Lost 4 ESI 5 “A party’s destruction of evidence qualifies as willful spoliation if the party has 6 some notice that the documents were potentially relevant to the litigation before they were 7 destroyed.” Leon v. IDX Sys. Corp., 464 F.3d 951 (9th Cir. 2006). “Moreover, because 8 the relevance of . . . destroyed documents cannot be clearly ascertained because the 9 documents no longer exist, a party can hardly assert any presumption of irrelevance as to 10 the destroyed documents.” Id. (cleaned up). 11 As noted, Plaintiff’s primary argument is that the deleted ESI was irrelevant to the 12 claims and defenses in this litigation, which involves a whistleblower claim arising from 13 Plaintiff’s termination in November 2012, because it was generated after the date of his 14 termination (and/or after the conclusion of the FINRA arbitration in 2014). 15 This argument is easily rejected. In section 1.2 of the Second Addendum to the 16 stipulated protective order, the parties jointly defined the term “Potentially Relevant ESI” 17 as follows:

18 “Potentially Relevant ESI” means ESI within the scope of permissible 19 discovery as provided within Federal Rule of Civil Procedure 26 and 34, such as ESI that concerns, substantiates, refers or relates to: Plaintiff’s claims or 20 allegations against Defendants or any of Defendants’ current or former employees, whether asserted in this matter or in any other legal, 21 administrative, or investigatory proceeding; Defendants’ defenses to any of 22 those claims; Plaintiff’s employment with or separation from Defendants; customers that Plaintiff serviced while he was still employed with 23 Defendants; Plaintiff’s efforts to find other employment after his 24 employment with Defendants ended or otherwise mitigate his purported damages; Plaintiff’s tax returns and other statements of income for himself 25 individually and for Burris Wealth Management; J.P. Morgan Private Bank 26 Managed Accounts, Chase Strategic Portfolio Managed Accounts, and any other “proprietary mutual funds” and “bank managed products” offered by 27 Defendants; and/or communications or documents regarding Defendants or 28 any of Defendants’ current or former employees exchanged between Plaintiff and any third-party, including with any government or regulatory agency or 1 personnel, current or former employees of Defendants, current or former customers of Defendants, or news journalists and other members of the press 2 or media. 3 4 (Doc. 61 at 2-3.) As this definition makes clear, there was no temporal cutoff on the scope 5 of “potentially relevant ESI.” Indeed, because one of the categories of damages sought by 6 Plaintiff in this action is “[e]conomic damages for injury to Plaintiff’s career, professional 7 reputation and earning capacity” (Doc. 1 at 21), the definition of “potentially relevant ESI” 8 included “ESI that concerns, substantiates, refers or relates to . . . Plaintiff’s efforts to find 9 other employment after his employment with Defendants ended or otherwise mitigate his 10 purported damages.” Such ESI would necessarily post-date Plaintiff’s separation from 11 Defendants in November 2012. 12 Notably, Plaintiff admitted that some of the ESI he destroyed fell within this 13 category. During a deposition in March 2020, Plaintiff stated that he “wiped” his laptop 14 because “I had client data in it, so I don’t want that data to get into anybody’s hands.” 15 (Doc. 78-2 at 23.) Similarly, during another deposition in June 2021, Plaintiff stated that 16 he performed factory resets on each of his iPhones because “I am not going to give a device, 17 sell a device, transfer a device, whatever to anybody that has my client data in it. I’m just 18 not doing it.” (Doc. 78-3 at 21.) These admissions are damning because “client data,” in 19 context, refers to the clients that Plaintiff serviced after leaving Defendants’ employment. 20 Information regarding such clients (and the income that Plaintiff earned from them) was 21 directly relevant to Plaintiff’s claim for prospective economic damages, as recognized in 22 the parties’ joint definition of “potentially relevant ESI.” 23 To the extent the “clients” at issue were former clients of Defendants whom Plaintiff 24 took with him after he stopped working for Defendants, Plaintiff’s communications with 25 such clients would also fall within the parties’ joint definition of “potentially relevant ESI” 26 because they were “communications or documents regarding . . . current or former 27 customers of Defendants.” For these reasons, the Court has no trouble concluding that 28 Plaintiff had notice that the ESI he was destroying was potentially relevant to the litigation. 1 In reaching this conclusion, the Court notes that Defendants discussed the 2 destruction of “client data” at length in their motion and specifically argued that Plaintiff’s 3 “assertion that he wished to destroy ‘client data’ was a direct admission that he violated 4 the Order.” (Doc. 84 at 3, 6, 9-10, 15.) In response, Plaintiff argued in conclusory 5 fashion—in a section of his brief unadorned by any citations to the record—that he “was 6 not prohibited from any reasonable activity or data management that avoided providing 7 non-JPMC client records.” (Doc. 89 at 7.) But as discussed above, Plaintiff was prohibited 8 from deleting such information. 9 Another category of information falling within the parties’ joint definition of 10 “potentially relevant ESI” was “communications or documents regarding . . . any of 11 Defendants’ current or former employees exchanged between Plaintiff and any third-party, 12 including with any . . . current or former employees of Defendants.” Put another way, all 13 communications between Plaintiff and current or former employees of Defendants were 14 deemed potentially relevant, regardless of when they were sent. With this understanding 15 in mind, the Court easily concludes that Plaintiff had notice that he was destroying 16 potentially relevant ESI by purging the contents of his invst4u@cox.net email account. 17 Although Plaintiff falsely testified during his deposition that he never used that account to 18 communicate with current or former employees of Defendants about the subject matter of 19 this litigation,5 Defendants have submitted undisputed evidence that Plaintiff did, in fact, 20 use the invst4u@cox.net email account for that purpose. (Doc. 78-35 [October 2016 email, 21 entitled “JP Morgan” and sent by Plaintiff from his invst4u@cox.net account to one of 22 Defendants’ employees, setting forth a series of questions about Plaintiff’s termination and 23 Plaintiff’s whistleblowing theory].)6 24 Because the Court has now identified several categories of destroyed ESI that were 25 5 Doc. 78-3 at 57 (Q: “Now, after you left JPMorgan, did you use any of your personal 26 e-mail accounts to communicate with . . . any JPMorgan employees or former employees regarding the subject matter of this litigation?” A: “No.”). 27 6 Although the email itself doesn’t specify whether the recipient is one of Defendants’ 28 current or former employees, Defendants have submitted a declaration avowing that the recipient was Plaintiff’s “former boss’s assistant.” (Doc. 78-4 ¶ 84.) 1 potentially relevant in this litigation, it is unnecessary to resolve all of Defendants’ 2 additional theories as to why the destroyed ESI should be deemed potentially relevant. The 3 Court notes, however, that it is highly skeptical of Plaintiff’s contention that the remaining 4 destroyed ESI was irrelevant. When Plaintiff was initially asked to explain why he’d 5 engaged in such extensive evidence-destruction efforts, he stated that he was simply 6 attempting to eliminate embarrassing, but irrelevant, personal information. (Doc. 85 at 7- 7 8.) But as Defendants establish in their motion (and as Plaintiff fails to rebut in his 8 response), that embarrassing information would not have appeared on all of the devices 9 Plaintiff wiped. After that excuse fell flat, Plaintiff suggested in his response that one of 10 the reasons he used BleachBit and iShredder was “space saving and performance 11 enhancing.” (Doc. 89 at 8.) But this rationale is almost laughable—Plaintiff’s use of 12 BleachBit’s “chaff” feature on his laptop was intended to fill the device with useless 13 gibberish, not save space. Finally, and as discussed in more detail in Part II.D.5 below, 14 Plaintiff was caught red-handed in a series of other lies and acts of deception during the 15 forensic examination process, including lying about when he stopped using his personal 16 email account and attempting to pass off a recently purchased laptop as a different laptop. 17 This backdrop raises a strong inference that the ESI destroyed by Plaintiff was not 18 irrelevant, personal information but information that was devastating to (and, at a 19 minimum, potentially relevant to) his claims in this action. Cf. Klipsh Grp., Inc. v. ePRO 20 E-Com., Ltd., 880 F.3d 620, 628 (2d Cir. 2018) (concluding that “the district court 21 [properly] inferred relevance and prejudice only from the unrecoverable data, and viewed 22 the various means of deleting data as cumulative proof that ePRO’s spoliation was 23 willful”). 24 3. Reasonable Steps To Preserve 25 The Court must next determine whether “the ESI is lost because a party failed to 26 take reasonable steps to preserve it . . . .” Porter, 2018 WL 4215602 at *3 (cleaned up). 27 The analysis as to this factor is straightforward. This isn’t a case where ESI was 28 lost due to reasons outside Plaintiff’s control. See Fed. R. Civ. P. 37(e), advisory 1 committee note to 2015 amendment (“[T]he rule . . . is inapplicable when the loss of 2 information occurs despite the party’s reasonable steps to preserve. For example, . . . 3 information the party has preserved may be destroyed by events outside the party’s 4 control—the computer room may be flooded, a ‘cloud’ service may fail, a malign software 5 attack may disrupt a storage system, and so on.”). Quite the opposite—Plaintiff engaged 6 in an intentional, lengthy, and multifaceted scheme to destroy ESI, including performing 7 factory resets on multiple phones and laptops, purging his email account, dragging his 8 email into his recycle bin, installing and repeatedly using BleachBit and iShredder, and 9 wiping his USB drives the day before he handed them over for inspection. 10 4. Replaceability 11 The next question under Rule 37(e) is whether the lost discovery “can be restored 12 or replaced through additional discovery.” 13 The expert report concludes that Plaintiff “caused Potentially Relevant ESI to be 14 irrevocably lost from his Electronic Media” (Doc. 73-1 at 2) and Plaintiff does not seriously 15 dispute this point (apart from his effort to submit Table 1, which as discussed elsewhere is 16 not properly before the Court and would not, in any event, establish that all of the deleted 17 ESI is replaceable). To recap, Plaintiff permanently deleted ESI from an array of phones, 18 laptops, and USB devices and also purged the contents of his email account. A court- 19 appointed expert concluded, after extensive analysis, that this ESI is irretrievably lost. 20 Accordingly, the Court is satisfied that the missing ESI is not replaceable through 21 additional discovery. 22 5. Intent To Deprive 23 The next inquiry under Rule 37(e)(2) is whether the nonmovant “acted with the 24 intent to deprive another party of the information’s use in the litigation.” Porter, 2018 WL 25 4215602 at *3. 26 The Court will not belabor the analysis as to this factor—the sheer number of 27 obfuscatory actions undertaken by Plaintiff, which are described in extensive detail in other 28 sections of this order, evince an unusually clear level of intent to deprive Defendants of 1 potentially relevant ESI. 2 The temporal proximity between Plaintiff’s acts and key discovery events provides 3 further circumstantial evidence of intent. Colonies Partners, L.P. v. Cnty. of San 4 Bernardino, 2020 WL 1496444, *9 (C.D. Cal. 2020) (“Courts . . . consider the timing of 5 the document loss when evaluating intent.”). Among other things, Plaintiff used 6 Bleachbit’s “chaff” feature only three days after the parties stipulated to a court order 7 permitting third-party subpoenas and then “wiped” both USB drives the day before handing 8 them over for forensic examination. 9 Finally, perhaps the most compelling evidence of intent arises from Plaintiff’s lies 10 and acts of deception during the forensic examination process. During a deposition in 11 March 2020, Plaintiff testified that he had two Dell laptops: (1) a laptop that he currently 12 used, which was located in his home office; and (2) an older Dell laptop that the newer one 13 “replaced.” (Doc. 78-2 at 21-23.) Meanwhile, under the second addendum to the 14 protective order, Plaintiff was required, upon request, to “promptly make [his] Electronic 15 Media available to the expert.” (Doc. 61 at 4.) Included in the definition of “Electronic 16 Media” were “computers [and] laptops.” (Id. at 2.) Accordingly, during the forensic 17 examination process, Plaintiff provided two Dell laptops for examination. (Doc. 73-1 at 3, 18 14-15.) However, this examination revealed that the newer of the two laptops provided by 19 Plaintiff was “a Dell laptop model number P91f, which was [commercially] released in 20 June 2020.” (Id. at 15.) Additionally, Dell’s shipping records showed that this laptop was 21 not shipped to Plaintiff until September 2020. (Id.) Based on these obvious date 22 discrepancies, the report concludes that “it is impossible that . . . the Dell 91f . . . was one 23 of the two laptops [Plaintiff] testified he had used at the time of his March 12, 2020 24 deposition.” (Id.) 25 To put it in layman’s terms, Plaintiff attempted to pass off a Dell laptop he purchased 26 in September 2020 as the laptop he described during his March 2020 deposition as the main 27 computer in his home office. Such outrageous conduct is utterly inconsistent with good 28 faith. Tellingly, although Defendants repeatedly refer to this episode in their motion (Doc. 1 84 at 7 & n.7, 8, 13, 15), Plaintiff makes no effort to address it (let alone defend it) in his 2 response. 3 Plaintiff also engaged in deception in relation to his email account. The expert 4 report states that, during a conference on December 15, 2020, Plaintiff “stated that he 5 stopped using the invst4u@cox.net email account in 2017.” (Doc. 73-1 at 14.)7 However, 6 the report concludes that “[b]ased on the subscriber records provided by Apple, it appears 7 that [Plaintiff] was using the invst4u@cox.net email address until” at least February 2020 8 and that “a review of the content of [a different account] revealed emails sent by Plaintiff 9 using the invst4u@cox.net account as late as” August 2020. (Id.) Such duplicity is, again, 10 inconsistent with good faith but consistent with an intent to deprive. 11 6. Dismissal Sanction 12 “[P]reclusive sanctions, such as dismissal of a case or entry of judgment against a 13 party, are disfavored.” Ritchie v. United States, 451 F.3d 1019, 1026 (9th Cir. 2006). Thus, 14 “[b]efore imposing the harsh sanction of dismissal, . . . the district court should consider 15 the following factors: “(1) the public’s interest in expeditious resolution of litigation; (2) 16 the court’s need to manage its dockets; (3) the risk of prejudice to the party seeking 17 sanctions; (4) the public policy favoring disposition of cases on their merits; and (5) the 18 availability of less drastic sanctions. While the district court need not make explicit 19 findings regarding each of these factors, a finding of willfulness, fault, or bad faith is 20 required for dismissal to be proper. Additionally, the district court must consider less 21 severe alternatives than outright dismissal.” Leon v. IDX Sys. Corp., 464 F.3d 951, 958 22 (9th Cir. 2006) (citations and internal quotation marks omitted). See also Fed. R. Civ. P. 23 37(e) advisory committee’s note to 2015 amendment (“[T]he severe measures authorized 24 7 Defendants’ motion and the declaration accompanying Defendants’ motion both 25 state that the transcript of the December 15, 2020 conference is attached as Exhibit 14 to the motion. (Doc. 84 at 1-2, 8; Doc. 78-4 ¶¶ 42-43.) This is inaccurate. Exhibit 14 (Doc. 26 78-18) consists of a string of emails. Although some of the emails refer to the December 15, 2020 conference, no transcript of that conference is provided. Nevertheless, despite 27 the seemingly missing transcript, the record is sufficient to make factual findings on this issue. Defendants proffered the expert’s report (which describes Plaintiff’s statement) in 28 support of their motion and Plaintiff did not, in his response, address (much less dispute) the report’s description of his statement during the December 15, 2020 conference. 1 by [Rule 37(e)(2)] should not be used when the information lost was relatively unimportant 2 or lesser measures such as those specified in subdivision (e)(1) would be sufficient to 3 redress the loss.”). 4 Having given careful consideration to the aforementioned standards, and 5 recognizing that dismissal is a disfavored sanction that should be imposed sparingly, the 6 Court still concludes that dismissal is warranted here. 7 When a court order has been violated, “factors 1 and 2 support sanctions and 4 cuts 8 against case-dispositive sanctions, so 3 and 5, prejudice and availability of less drastic 9 sanctions, are decisive.” Valley Engineers Inc. v. Elec. Eng’g Co., 158 F.3d 1051, 1057 10 (9th Cir. 1998). Here, Plaintiff violated at least the Court’s October 29, 2020 order, which 11 required Plaintiff to preserve and produce ESI for forensic review. 12 “[F]actor 5 involves consideration of three subparts: whether the court explicitly 13 discussed alternative sanctions, whether it tried them, and whether it warned the 14 recalcitrant party about the possibility of dismissal. . . . But despite all this elaboration of 15 factors . . . it is not always necessary for the court to impose less serious sanctions first, or 16 to give any explicit warning.” Id. (citation omitted). 17 The Court will begin with the third prong of factor 5—whether it warned the 18 recalcitrant party about the possibility of dismissal. Rule 37 of the Federal Rules of Civil 19 Procedure warns that dismissal is an appropriate sanction for failure to comply with court 20 order, Rule 37(b)(2)(v), or for failure to preserve ESI, Rule 37(e)(2)(c). Additionally, the 21 Court’s October 2020 order explicitly warned Plaintiff that “Defendants may seek . . . 22 appropriate sanctions up to and including default . . . if Plaintiff: unreasonably fails to 23 identify or provides misleading information concerning his Electronic Media and 24 Potentially Relevant ESI; obstructs, attempts to evade, or unduly delays the . . . efforts as 25 provided herein; deleted or failed to preserve Potentially Relevant ESI while under a duty 26 to preserve it; or engaged in any other discovery misconduct.” (Doc. 61 at 8.) The Court 27 finds that it gave adequate warnings about the possibility of dismissal. 28 The first and second prongs of factor 5, which analyze alternative sanctions, seem 1 to dovetail with factor 3, which addresses the risk of prejudice to Plaintiff if his case is 2 dismissed. The Court will discuss those issues collectively. 3 “What is most critical for case-dispositive sanctions, regarding risk of prejudice and 4 of less drastic sanctions, is whether the discovery violations threaten to interfere with the 5 rightful decision of the case. . . . Dismissal is appropriate where a pattern of deception and 6 discovery abuse made it impossible for the district court to conduct a trial with any 7 reasonable assurance that the truth would be available. . . . Sometimes . . . a party’s 8 discovery violations make it impossible for a court to be confident that the parties will ever 9 have access to the true facts.” Valley Engineers, 158 F.3d at 1057-58 (citation and 10 quotation marks omitted). 11 Plaintiff does not propose any sanctions in lieu of dismissal, instead arguing that 12 “there is no basis to impose any sanction whatsoever” (Doc. 89 at 1), but the Court would 13 decline to impose lesser sanctions even if Plaintiff had proposed them. An adverse jury 14 instruction or presumption that covers all of the destroyed evidence would have to be so 15 broad that it would, itself, essentially terminate the case. Additionally, the sheer scope of 16 Plaintiff’s dishonesty and spoliation efforts—which the Court explicitly finds amounted to 17 bad faith—makes this the rare case where it is impossible to have confidence that 18 Defendants will ever have access to the true facts. Thus, the Court finds that although it 19 did not impose alternative sanctions before dismissal, such sanctions are “not necessary” 20 in this case. Valley Engineers, 158 F.3d at 1057. 21 Of course, dismissal will be highly prejudicial to Plaintiff. But Plaintiff already had 22 the opportunity to litigate several of his termination-related claims on the merits, via a two- 23 week FINRA arbitration. This somewhat reduces the prejudice of dismissal. At any rate, 24 because Plaintiff has engaged in such extensive misconduct and deception, without any 25 obvious contrition or awareness of the wrongfulness of his conduct, there is a serious risk 26 that further proceedings will continue to be plagued by a “pattern of deception and 27 discovery abuse [which makes] it impossible for the district court to conduct a trial with 28 any reasonable assurance that the truth would be available.” Id. at 1058. 1 Accordingly, 2 IT IS ORDERED that Plaintiff's motion to file omitted exhibits in opposition to || Defendants’ motion for sanctions (Doc. 92) is denied. 4 IT IS FURTHER ORDERED that Defendants’ motion for sanctions (Docs. 78, 5|| 84) is granted. 6 IT IS FURTHER ORDERED that Plaintiff's complaint (Doc. 1) is dismissed with 7\| prejudice. The Clerk of Court shall terminate this action and enter judgment accordingly. 8 Dated this 7th day of October, 2021. 9 10 Lom ee” ll f t _o—— Dominic W. Lanza 12 United States District Judge 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28

-32-