Tagged: Data Preservation

Disappearing Act: Northern District of California Issues Rare Terminating Sanctions for Spoliation on a Massive Scale

In WeRide Corp. v. Kun Huang, the Northern District of California addressed an egregious case of discovery abuses and spoliation by defendants in a business litigation involving the alleged theft of autonomous vehicle technology. Applying Federal Rules of Civil Procedure 37(b) and 37(e), the court issued rare terminating sanctions against several defendants who willfully and intentionally deleted various forms of ESI, including relevant emails, status reports, and source code, well after the commencement of litigation and after a preservation order issued by the court requiring the preservation of such information. Defendants compounded these abuses by adopting the use of “DingTalk,” an ephemeral communication technology, after the court had issued the preservation order. WeRide, a technology company engaged in the business of developing autonomous cars, employed defendant Jing Wang as CEO in January 2018. WeRide alleged that Wang went on to form his own company, AllRide, as a direct competitor. WeRide also alleged that former employee defendant Kun Huang was recruited by Wang to work for AllRide while still employed by WeRide. WeRide alleged that Huang downloaded various forms of data during this time period and transferred this data onto several USB devices from two WeRide-issued computers, then proceeded to delete files from the devices. WeRide further alleged that AllRide and Huang stole WeRide’s source code,...

In It for the Long Haul: The Duty to Preserve Social Media Accounts Is Not Terminated Upon an Initial Production

In a recent decision by a federal district court in Ohio, the court admonished a plaintiff in a gender-based pay discrimination for deactivating her LinkedIn account during the pendency of the litigation after making an initial production. The court concluded that plaintiff had violated her duty to preserve pursuant to Rule 37(e), as the conduct resulted in the deletion of relevant and discoverable information that was the subject of a previous court order. The court declined to impose sanctions because plaintiff had in fact produced data from her LinkedIn account and because defendant could not demonstrate prejudice. However, the court did not let plaintiff’s offense go lightly; the court stated that plaintiff’s action was serious and inappropriate. In Faulkner v. Aero Fulfillment Services, plaintiffs alleged gender-based pay discrimination during their employment with defendant. Pursuant to a court order, plaintiffs had to produce, among other things, the “last three years of social media information.” Plaintiff Faulkner’s counsel followed the directions on the LinkedIn website to download a full data archive in Microsoft Excel format and produced the Excel file to defendant. Subsequently, defense counsel requested the social media information in a different format, a “screenshot” format. But plaintiff’s counsel was unable to produce Ms. Faulkner’s LinkedIn information in the “screenshot” format because the account had already...

Defendant Acting With “A Pure Heart But Empty Head” Not Subject to Spoliation Sanctions Under Amended Rule 37(e)

A recent decision denying a motion for spoliation sanctions highlights that a moving party must show that even clearly spoliated ESI is not available from other sources to qualify for an award of any form of sanction under Rule 37(e). In Snider v. Danfoss, LLC, the Northern District of Illinois held that a defendant’s admitted and erroneous destruction of duplicative ESI did not prejudice the plaintiff and therefore sanctions were not warranted. In other words, “no harm, no foul.” Plaintiff Snider worked for Danfoss for a number of years, during which time she was sexually harassed by another employee. Plaintiff informed her acting supervisor of the harassment, and was later transferred to a different position, which she viewed as a demotion and retaliation for her complaint. Approximately one week after the transfer, Plaintiff’s counsel sent a generalized, “preserve all evidence” letter to Danfoss. She then quit, and, pursuant to Danfoss’s policy, her emails were deleted 90 days after her employment ended. Plaintiff’s acting supervisor also later left Danfoss’s employment, and her emails were deleted in accordance with Danfoss’s auto-deletion policy. After the case was filed, Plaintiff deposed her acting supervisor, who suffered from a case of “testimonial amnesia” and was unable to recall a variety of facts, even benign, irrelevant facts. Plaintiff thereafter sought production...

Takeda Part Two: Destroy Evidence, Pay the Price — Eli Lilly and Takeda Pharmaceutical Co. Get Hit For $9 Billion Punitive Damages Verdict

Recently, in In re Actos (Pioglitazone) Products Liability Litigation, MDL No. 11-2299, a Louisiana federal jury awarded $9 billion in punitive damages against Takeda Pharmaceutical Co. (“Takeda”) and Eli Lilly & Co. (“Lilly”). The verdict was delivered on the heels of Judge Rebecca Doherty’s January opinion, which lambasted Takeda for failing to (1) enforce its own litigation hold and (2) follow its document retention procedures, which led to the destruction of relevant evidence that Judge Doherty found would have likely been beneficial for the plaintiffs’ case.

Final Cybersecurity Framework Released in Furtherance of President Obama’s Executive Order

On Wednesday, February 12, the White House released the National Institute of Standards and Technology’s (NIST) Final Cybersecurity Framework: a set of industry best practices and standards to help owners and operators of critical infrastructure develop better cybersecurity programs. It is accompanied by a Roadmap which discusses NIST’s next steps with the Framework and identifies key areas of development, alignment, and collaboration. The Framework stems from President Obama’s February 2013 Executive Order on cybersecurity, previously covered on October 1, 2013. The overall core of the Framework is essentially unchanged from earlier drafts, also previously discussed on October 28, 2013.

Negligent Spoliation May Result in Sanctions Under New York Law

Recently, the New York Supreme Court, Appellate Division, First Department considered whether to adopt and apply the Zubulake standard for the spoliation of electronically-stored information (“ESI”) to a claim for spoliation of an audiotape recording or whether existing New York spoliation doctrine was sufficient. Strong v. City of New York involved a June 30, 2009, accident in which an NYPD vehicle collided with another vehicle, jumped the sidewalk curb and struck five pedestrians, including plaintiff, Kevin Strong. Within 30 days of the accident, three plaintiffs commenced personal injury actions and these were consolidated for trial. On September 21, 2009, less than 90 days after the accident, the City joined issue and interposed the “emergency operation” defense, claiming the police officer’s vehicle was an authorized emergency vehicle engaged in an emergency operation at the time of the accident and, therefore, the City could only be held liable if the officer had acted with reckless disregard for the safety of others.

Coming to a Close: Reflections on the Proposed Amendments to F.R.C.P. 37 Debate at the 2013 Georgetown Advanced eDiscovery Institute as the End of the Public Comment Period Nears

The proposed amendments to F.R.C.P. 37(e) would establish a single standard by which courts will assess culpability and issue sanctions for failure to preserve electronically stored information (“ESI”). Our previous blog post discusses the rule. The proposed amendments to F.R.C.P. 37(e) were recommended for adoption in 2010 and, on June 3, 2013, they were approved for public comment (as part of a package of amendments to several federal rules) by the Judicial Conference of the United States’ Standing Committee on Rules of Practice and Procedure. On August 15, 2013, the Committee officially published for public comment the full slate of proposed rule changes. Unsurprisingly, the proposed amendments have generated considerable feedback from the legal community and, indeed, the discussion took center stage at the 2013 Georgetown Advanced eDiscovery Institute on November 22, 2013. With little more than a week to go before the comment period expires, and with, to date, more than 600 comments already posted addressing various aspects of the proposed rule amendments, we thought it might be a good time to reflect upon the discussion at Georgetown, especially for those considering weighing in before the end of the public comment period.

Preliminary Cybersecurity Framework Released in Furtherance of President Obama’s Executive Order

The National Institute of Standards and Technology (NIST) has just released its Preliminary Cybersecurity Framework: a set of best practices to help owners and operators of critical infrastructure reduce cybersecurity risks. This voluntary framework provides both private and public-sector organizations with a common language for understanding and managing cybersecurity risks internally and externally. The framework stems from President Obama’s February 2013 Executive Order on cybersecurity, previously covered by this blog. The Final Framework is due to be released in February 2014, following a 45-day public comment period on the Preliminary Framework.

A Bad “Day” for a Company Whose In-House Attorney Failed to Properly Preserve Relevant Documents

An Arizona federal court has determined that default judgment, an adverse instruction and monetary damages are proper remedies for in-house counsel’s failure to take the proper steps to preserve potentially relevant evidence after receiving notice of potential litigation. In Day v. LSI Corporation, Docket No. CIV-11-186-TUC-CKJ, the United States District Court for the District of Arizona granted, in part, the plaintiff-employee’s motion for entry of a default judgment and imposed additional sanctions against the defendant-employer, concluding that the employer’s in-house attorney had a “culpable mind” and acted willfully in failing to carry out the company’s preservation obligations.