Close
Enter your
text here

Electronic Discovery

Plaintiff is Able to Get Some Subpoenas for Personal Data Quashed, But Not All: eDiscovery Case Law

In Delgado v. Tarabochia, et al., No. C17-1822RSL (W.D. Wash. May 4, 2018), Washington District Judge Robert S. Lasnik granted in part and denied in part the plaintiff’s motion to quash subpoenas for personal phone records and bank records, finding that phone records before the plaintiff’s hand injury on the defendant’s fishing boat were “of vital importance to defendants’ theory of the case”, but that the need for pre-incident bank records was not proportional to the needs of the case and that, with regard to subpoenas of post-incident data, defendants were “fishing”.

I’ll pause a moment to let you enjoy the irony of that statement… :o)

Case Background

Anyway, the plaintiff injured his hand while on board the F/V JOYCE MARIE and sued the vessel and vessel owner(s) for Jones Act negligence and unseaworthiness, alleging that he lost his balance and his hand went through a plate glass window on the wheelhouse, causing severe injuries with continuing disabilities.  However, another crew member on board at the time of the incident claimed that the plaintiff was using heroin in the days leading up to the incident and was in the midst of a heated argument with his girlfriend when he punched through the window.  After the plaintiff left the vessel, defendants located a computer file supposedly created by the plaintiff, containing text messages, emails, and photographs dated October 2013 to July 2014 that seemed to reflect drug transactions and a volatile relationship, but the plaintiff (in his deposition) denied fighting with his girlfriend and denied punching through the wheelhouse window.  Reporting that he had no feeling in three of his fingers and his thumb and was in constant, severe pain, the plaintiff claimed he was entitled to damages of $3 million, but the defendant had surveillance video that seemed to contradict the plaintiff’s testimony regarding the extent and severity of his injuries.

The defendants issued three subpoenas for phone records from January 2014 to the present, including all account information, call and text message logs, and roaming data. They also issued two subpoenas for bank records for the same period, seeking detailed summaries of credit and debit card transactions, withdrawals, and deposits. The plaintiff seeks to quash all five subpoenas as irrelevant and an unwarranted burden on his privacy interests.

Judge’s Ruling

With regards to the pre-incident phone records, Judge Lasnik indicated that “defendants have identified a specific need to confirm events and authenticate communications that are directly relevant to a determination of whether defendants’ negligence and/or the vessel’s unseaworthiness caused plaintiff’s injuries. To the extent these records mirror the electronic files found on the vessel’s computer and corroborate the other crewman’s statements, they are of vital importance to defendants’ theory of the case. While much will be disclosed that has nothing to do with this case, plaintiff’s privacy interests do not outweigh the need to obtain relevant information regarding the cause of plaintiff’s injuries in this case where plaintiff says he is entitled to damages of $3,000,000.”

With regards to the pre-incident bank records, Judge Lasnik stated that “defendants offer no reason to suspect that these records will authenticate or corroborate the electronic files plaintiff left behind. Production of plaintiff’s pre-incident finances, including every purchase and every deposit, is unlikely to result in admissible evidence (there is no reason to suspect that plaintiff used a credit card to purchase heroin or that defendants would be able to identify such transactions from a list of charges or withdrawals). Because of its minimal relevance and the outsized burdens it would impose on plaintiff’s privacy interests, discovery of the pre-incident bank records is not proportional to the needs of the case.”

As for the post-incident phone and bank records, Judge Lasnik stated that “defendants are fishing” and granted the plaintiff’s motion to quash the subpoena for these records because the “balance of the benefits and burdens of these post-incident discovery requests are not in defendants’ favor: they are not prompted by any specific need for information and are likely to drive discovery and generate disputes that are wholly collateral to the primary issues in this case.”

So, what do you think?  Did the judge assess the relevancy and proportionality in this case correctly and were the defendants “fishing” for the post-incident records?  Tee-hee!  Please share any comments you might have or if you’d like to know more about a particular topic.

Case opinion link courtesy of eDiscovery Assistant.

Sponsor: This blog is sponsored by CloudNine, which is a data and legal discovery technology company with proven expertise in simplifying and automating the discovery of data for audits, investigations, and litigation. Used by legal and business customers worldwide including more than 50 of the top 250 Am Law firms and many of the world’s leading corporations, CloudNine’s eDiscovery automation software and services help customers gain insight and intelligence on electronic data.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine. eDiscovery Daily is made available by CloudNine solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscovery Daily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

As Blockchain Joins the Healthcare Profession, Are Legal Departments Prepared to Keep Up?: eDiscovery Trends

When we hear the word blockchain, most of us still think of Bitcoin, that mysterious new currency that seems to equally enthrall forward thinking investors and less-than-savory entrepreneurs who lurk around the darkest parts of the Dark Web. But blockchain technology is finding more and more practical uses, most recently in the healthcare industry.

In a recent Wall Street Journal Article, blockchain is presented as a low-cost, highly secure way to unify healthcare records, which to date has been a huge obstacle. As the article puts it, “In the current tangle of incompatible records systems that typifies U.S. health care, incorrect information can creep in when patient data gets re-entered multiple times by doctors’ offices, insurers and hospital staff. Big errors can seriously affect the quality of care that patients receive, small discrepancies can result in wrongful denials of insurance coverage, and errors of all types add to the system’s cost.”

In very simplified terms, Blockchain works like a giant Google Sheet: a single ledger that can be added to simultaneously by all users in the system, with each “transaction” creating an audit trail so that its data is nearly infallible. For healthcare records systems, this can put patients, insurers, and providers literally on the same page, providing secure and accurate information for all stakeholders across the board.

In January, Nashville-based Change Healthcare (a network of 800,000 physicians, 117,000 dentists and 60,000 pharmacies) introduced a blockchain system for processing insurance claims. The shared ledger of encrypted data gives providers a “single source of truth,” according to Emily Vaughn, blockchain product development director at Change Healthcare.

All parties can see the same information about a claim in real time, so that a patient or provider won’t have to call multiple parties to verify information. Each time data is changed, a record is shown on the digital ledger, identifying the responsible party. Any changes also require verification by each party involved, ensuring record’s accuracy.

Change Healthcare won’t reveal actual numbers about how much the new system (which processes roughly 50 million events daily) cuts costs, but the efficiencies, accuracy, and security will no doubt bring huge savings.

The question regarding the eDiscovery implications with this type of move are clear: How will this data be preserved, collected, and prepared for review? It’s not so much a question of a technical nature (though that will have to be answered by someone, but I’ll leave it to the software engineers to properly answer it). What I mean to say, is that anytime a new data source is introduced into the organization’s landscape, the question of preservation, collection, and production should already be on the minds of the legal department. Often, changes in a company’s technology infrastructure are driven by departments outside of legal: usually a combination of IT and business units looking for efficiency, security, and cost savings. Many times, large decisions will be made, leaving the legal team in the position of playing catch up when it comes to discovery should litigation arise.

So, even if your company isn’t moving to blockchain anytime in the near future, this story of what is happening in the healthcare space is important to consider, because, to quote the poet William Blake, “What is now real, was once only imagined.” And the potential uses for blockchain technology lately seems to be on everyone’s mind.

So, what do you think?  How do you see the increased use of blockchain technology affecting eDiscovery?  Please share any comments you might have or if you’d like to know more about a particular topic.

Sponsor: This blog is sponsored by CloudNine, which is a data and legal discovery technology company with proven expertise in simplifying and automating the discovery of data for audits, investigations, and litigation. Used by legal and business customers worldwide including more than 50 of the top 250 Am Law firms and many of the world’s leading corporations, CloudNine’s eDiscovery automation software and services help customers gain insight and intelligence on electronic data.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine. eDiscovery Daily is made available by CloudNine solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscovery Daily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

Freedom of Information? Not Necessarily for Text Messages: eDiscovery Trends

What percentage of Freedom of Information Act (FOIA) requests actually result in receiving all of the information requested?  75 percent?  50 percent?  You might be surprised.  Apparently, according to a recent survey, one part of the problem could be the lack of capturing text messages within government organizations.

According to the 2018 Public Sector Text & Mobile Communications Survey from Smarsh, 70 percent of federal, state, county and city government organizations surveyed report allowing SMS/text for official business communication.  But, almost half of those (46 percent) are not formally capturing and retaining these messages.  There were 236 total respondents in the survey.

Here are some other interesting findings from the report:

  • The vast majority of agencies allow organizational email (97 percent) on mobile devices, but right behind it is SMS/text messaging, with 70 percent allowing it for official government business. Social channels Facebook and Twitter are the next most frequently cited, with 58 percent and 44 percent, respectively.
  • Two-thirds of surveyed organizations allow employees to use their own BYOD devices for official business, for those devices, only 35 percent of respondents are retaining SMS/text messages (as opposed to 62 percent for Corporate Owned Personally Enabled (COPE) devices).
  • The top four reasons SMS/Text records are NOT captured are: 1) Don’t currently have budget this year, 2) SMS/text isn’t required to be retained by law, 3) Waiting for Capstone/FOIA guidance, 4) Existing capture technologies are too complicated.
  • The majority of respondents, 62 percent or nearly 2/3, lacked confidence that they could provide specifically requested mobile text messages promptly if responding to a public records or litigation request.
  • Agencies with no retention solution in place have very little confidence in their ability to fulfill requests. 23 percent reported that if requested, it was unlikely they could produce SMS/text messages from their organizational leader at all.

When you hear these stats, you might be surprised the numbers aren’t higher.  Last year, Federal Freedom of Information Act (FOIA) litigation jumped 26 percent over the previous year. In 2018, that number is on track to increase again. While an average of 2.08 lawsuits were filed each day in 2017, 2018 has seen the average increase to 2.72 lawsuits per day.  Last year, there were 823,222 Federal FOIA requests – 78 percent of those requests yielded censored files or no records at all.  In other words, only 22 percent of FOIA requestors got everything they asked for.  22 percent!  And, the Federal government spent $40.6 million in legal fees defending its withholding of files in 2017.  Freedom of information isn’t free, apparently.

I guess it isn’t surprising that government agencies are struggling with the same challenges of collecting and keeping mobile device data that other organizations are.  Maybe we should conduct a webinar on the topic?  Does two weeks from today work for you?  :o)

So, what do you think?  Is your organization able to produce text messages from your employees if needed?  Please share any comments you might have or if you’d like to know more about a particular topic.

P.S. — Happy Birthday, Carter!

Sponsor: This blog is sponsored by CloudNine, which is a data and legal discovery technology company with proven expertise in simplifying and automating the discovery of data for audits, investigations, and litigation. Used by legal and business customers worldwide including more than 50 of the top 250 Am Law firms and many of the world’s leading corporations, CloudNine’s eDiscovery automation software and services help customers gain insight and intelligence on electronic data.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine. eDiscovery Daily is made available by CloudNine solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscovery Daily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

Plaintiff Argument for Failure to Produce Cell Phone Data in Wife’s Name is “Unpersuasive”: eDiscovery Case Law

In Ortiz v. Amazon.com LLC, et al, No. 17-cv-03820-JSW (MEJ) (N.D. Cal. May 25, 2018), California Magistrate Judge Maria-Elena James ordered the plaintiff, who failed to produce court-ordered cell phone records because the account was in his wife’s name and refused to provide her information, to provide defendant Golden State with his cell phone account holder’s name and address so that defendant could subpoena the cell phone records from her.  Judge James also ordered the plaintiff to appear for a deposition in San Francisco, as originally scheduled, instead of Los Angeles (where the plaintiff had moved).

Case Background

In this case on March 7, 2018, the Court ordered the plaintiff to produce his cell phone records to Golden State no later than April 6, 2018. The plaintiff stated these records were not in his possession or control, as the account for the phone records was in his non-party wife’s name.  The plaintiff claimed he had attempted to obtain the phone records by requesting them from the carrier, but was not authorized to do so, nor could he get them from his wife (the plaintiff didn’t explain why).  He did not inform Golden State that the cell phone records were in his wife’s name and thus unobtainable until April 27, 2018 – three weeks after the Court-ordered deadline for production.  The plaintiff also refused to provide his wife’s name and address to allow defendant Golden State to subpoena the records from her, despite his representations that he would do so by May 8 and 16.

Also, on January 25, 2018, defendant Golden State requested the plaintiff’s availability for deposition and, at the beginning of March, he confirmed his deposition would take place on April 23, 2018. On March 7, 2018, defendant Golden State served a Notice of Deposition that Plaintiff’s deposition would take place at defense counsel’s San Francisco office, but on April 19, 2018, Plaintiff cancelled the deposition because he moved to Los Angeles.

The plaintiff defendant Golden State filed two joint discovery dispute letters, from which the Court made its ruling.

Judge’s Ruling

In assessing the request for cell phone records, Judge James stated that “Plaintiff does not explain his delay in informing Golden State that the cell phone records are not in his possession or control. Plaintiff knew or should have known who is named on the account; he offers no reason why this information was not available to him prior to April 27. Plaintiff has known as early as September 18, 2017, and at the very latest, as of March 7, 2018, that he had to produce his phone records… Plaintiff states that, ‘[f]or personal reasons, Plaintiff wishes to maintain the details of his relationship status, and interactions with his wife, private.’…This argument is unpersuasive. By alleging Golden State failed to pay him for all hours worked and to provide him with meal and rest breaks, Plaintiff has placed his work day activities—including whether he made or received phone calls or text messages on his personal cell phone—at issue. Providing the account holder’s name and address reveals minimal details, if any, about Plaintiff’s marital status or interactions.”  As a result, Judge James ordered the plaintiff to provide defendant Golden State with his cell phone account holder’s name and address so that defendant could subpoena the cell phone records from her.

As for the deposition, Judge James ordered the deposition to be conducted in San Francisco, noting the fact that the plaintiff “did not inform Golden State that his relocation would cause difficulties until the eve of the deposition is not well taken” and rejecting the plaintiff’s proposed compromise to have one of Golden State counsel’s Los Angeles attorneys take the deposition in counsel’s Los Angeles office.  She also granted Golden State’s request for an order that “Plaintiff appear at his deposition before he can compel or proceed with depositions of Golden State’s witnesses”.

So, what do you think?  Do these seem like delay tactics or could the plaintiff have had a legitimate reason for failing to produce the cell phone records?  Please share any comments you might have or if you’d like to know more about a particular topic.

Case opinion link courtesy of eDiscovery Assistant.

Sponsor: This blog is sponsored by CloudNine, which is a data and legal discovery technology company with proven expertise in simplifying and automating the discovery of data for audits, investigations, and litigation. Used by legal and business customers worldwide including more than 50 of the top 250 Am Law firms and many of the world’s leading corporations, CloudNine’s eDiscovery automation software and services help customers gain insight and intelligence on electronic data.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine. eDiscovery Daily is made available by CloudNine solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscovery Daily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

Unsure About How to Map Your Data for GDPR? Here are Several Templates to Get Started: Data Privacy Best Practices

Now that Europe’s General Data Protection Regulation (GDPR) is in effect, all organizations out there have a good handle on all of their data, including which personally identifiable information (PII) they handle for European data subjects out there and clear policies for how they ensure protection of that PII.  Right?  OK, maybe not.  If your organization is still scrambling to comply with GDPR and still trying to get a handle on the data you’re managing and the flow of that data, here is a site with several templates to help you get started in that process.

The site Demplates has templates for all sorts of things, including SWOT analysis templates (we wrote about the benefits of a SWOT analysis here), Certificates of Appreciation for employees, even Pest Control Service Agreements.  A couple of months ago (on my birthday, no less), the site posted GDPR Data Mapping Template: 10+ Print-Ready Templates, with several useful templates to help organizations create data maps, data flow diagrams, GDPR Data Processing Notices, privacy policy and data protection policy statements, data protection impact assessments and data audits.  The template documents are in different formats, including Excel, Word and Visio.  Here are pictures of a couple of examples:

With the challenges these days stemming from the growth of big data, data mapping is not only a good organization practice to not only help get a handle on your organization’s big data, but also to document your organization’s handling of PII and compliance with GDPR on the handling of PII.  Tom O’Connor and I talked about the importance of data mapping in our webcast on GDPR back in February (you can check it out here).  Data mapping supports in compliance and adherence to critical GDPR factors such as:

  • Maintenance of the data lifecycle;
  • Documentation that records are kept in adherence to the rules of GDPR to submit to the regulatory and supervising authorities;
  • Maintaining Accountability of the data for the full data lifecycle;
  • Evidence for the organization that the data is protected in its full cycle.

If you’re still scrambling to comply with GDPR, perhaps one or more of these templates can help you document your compliance or help you discover one or more areas where you may be deficient in your compliance.

So, what do you think?  Is your organization still trying to comply with GDPR?  Does your organization have an organization data map?  Please share any comments you might have or if you’d like to know more about a particular topic.

Sponsor: This blog is sponsored by CloudNine, which is a data and legal discovery technology company with proven expertise in simplifying and automating the discovery of data for audits, investigations, and litigation. Used by legal and business customers worldwide including more than 50 of the top 250 Am Law firms and many of the world’s leading corporations, CloudNine’s eDiscovery automation software and services help customers gain insight and intelligence on electronic data.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine. eDiscovery Daily is made available by CloudNine solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscovery Daily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

Collecting Responsive ESI from Difficult Places: eDiscovery Webcasts

Happy June!  I don’t normally promote webcasts twice in one week, but this month’s webcast is a little earlier than normal.  What can I say, it’s family vacation season and my family has plans the last week of this month… :o)

Believe it or not, there was a time when collecting potentially responsive ESI from email systems for discovery was once considered overly burdensome. Now, it’s commonplace and much of it can be automated. But, that’s not where all of the responsive ESI resides today – much of it is on your mobile device, in social media platforms and even in Internet of Things (IoT) devices. Are you ignoring this potentially important data? Do you have to hire a forensics professional to collect this data or can you do much of it on your own?  We will discuss these and other questions in a webcast in a few weeks.

Wednesday, June 20th at noon CST (1:00pm EST, 10:00am PST), CloudNine will conduct the webcast Collecting Responsive ESI from Difficult Places. In this one-hour webcast that’s CLE-approved in selected states, we will discuss what lawyers need to know about the various sources of ESI today, examples of how those sources of data can be responsive to litigations and investigations, and how lawyers may be able to collect much of this data today using intuitive applications and simple approaches. Topics include:

  • Challenges from Various Sources of ESI Data
  • Ethical Duties and Rules for Understanding Technology
  • Key Case Law Related to Mobile Devices, Social Media and IoT
  • Options and Examples for Collecting from Mobile Devices
  • Options and Examples for Collecting from Social Media
  • Examples of IoT Devices and Collection Strategies
  • Recommendations for Addressing Collection Requirements
  • Resources for More Information

As always, I’ll be presenting the webcast, along with Tom O’Connor.  To register for it, click here.  Even if you can’t make it, go ahead and register to get a link to the slides and to the recording of the webcast (if you want to check it out later).  If you want to know how to collect electronically stored information from difficult places, this is the webcast for you!

So, what do you think?  Do you feel like you know when and how to collect ESI from mobile devices, social media and IoT devices?  If not, register for our webcast!  Please share any comments you might have or if you’d like to know more about a particular topic.

Sponsor: This blog is sponsored by CloudNine, which is a data and legal discovery technology company with proven expertise in simplifying and automating the discovery of data for audits, investigations, and litigation. Used by legal and business customers worldwide including more than 50 of the top 250 Am Law firms and many of the world’s leading corporations, CloudNine’s eDiscovery automation software and services help customers gain insight and intelligence on electronic data.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine. eDiscovery Daily is made available by CloudNine solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscovery Daily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

Court Denies Plaintiff Request for “Quick Peek” to Privilege Log, Proposing Special Master Review Instead: eDiscovery Case Law

In Winfield v. City of New York, No. 15-cv-05236, (S.D.N.Y. May 10, 2018), New York Magistrate Judge Katherine H. Parker, ruling on a debate of what constitutes privileged ESI,  denied the plaintiff’s request for a “quick peek” at 3,300 documents listed on the defendant’s privilege log, opting to propose instead for a special master to conduct a privilege review of those documents.

Case Background

In June 2017, the defendant moved for return of an accidentally produced privileged document under the agreed-upon procedures set forth in their Clawback Agreement, which then led to further discussion between the parties about the defendant’s privilege designations, with the plaintiffs believing the defendant over-designated documents as privileged.

In July 2017, the court directed the plaintiffs to identify a subset of 80 documents from the defendant’s privilege log that had been withheld on the basis of the deliberative process privilege. The court also ruled that “the defendant would have an opportunity to rereview the 80-document subset identified by Plaintiffs and determine whether it intended to maintain its privilege claim as to each document.”

After this review, the defendant maintained a claim of privilege over only 27 documents and withdrew its privilege designation for 51 document and produced them.  The Court subsequently ordered the City to submit all 80 documents to this Court for in camera review for purposes of assessing the validity of the initial and remaining privilege designations.

The plaintiffs also contested some of the defendant’s refusal to answer at depositions on the basis of attorney-client, work product, and/or deliberative process privilege and submitted a letter to the court seeking privilege rulings on 20 questions to which the City’s witnesses were directed not to respond. The defendant subsequently withdrew its privilege objections six of these questions and provided the plaintiffs with responses.

In February 2018, the court issued a lengthy ruling granting the defendant’s Clawback Demand and granting in part and denying in part the plaintiffs’ motion to compel production of certain documents from the sample set of documents designated as privileged by the defendant on its privilege log. The court also granted in part the plaintiffs’ motion to compel answers to questions posed during depositions. At the same time, the court directed the defendant to re-review its privilege designations, after which, the defendant de-designated certain documents as privileged and produced them.

In April 2018, the plaintiffs raised a concern with the volume (3,300 documents) designated by the defendant as privileged. The court then directed the parties to meet and confer concerning a proposal to address the plaintiffs’ concerns. At that meeting, the plaintiffs proposed the Court order the defendant to turn over all 3,300 documents designated as privileged for a “quick peek” at them, promising to review them in only a few weeks. The defendant, which had already spent significant time reviewing documents for privilege prior to producing them, vigorously objected.

Judge’s Ruling

After taking into consideration FRCP 26 and FRE 502, as well as previous case law, Judge Parker ruled:

“The task of reviewing 3,300 documents is enormous and one that this Court cannot complete before the end of fact discovery on July 31, 2018 given other demands in this and other cases. Appointment of a Special Master to conduct the privilege review pursuant to Rule 53 is therefore warranted…. In accordance with Rule 53(b)(1), the parties may file a letter regarding their position on the appointment of a Special Master, whether they have identified any conflict-of-interest issues… and suggest other candidates for appointment if they so desire…. Given the costs of a Special Master, Plaintiffs are directed to evaluate whether they can narrow the documents for review so as to reduce the time and thus the costs of the review.”

Judge Parker proposed the appointment of the Honorable Frank Maas (Ret.) of JAMS, who recently retired as a Magistrate Judge in the District and was available to conduct a review (and was recently proposed for a privilege review in another high-profile case).  Judge Parker indicated that “the parties may file a letter regarding their position on the appointment of a Special Master, whether they have identified any conflict-of-interest issues that would preclude appointment of Judge Maas, and suggest other candidates for appointment if they so desire.”

So, what do you think? Is the appointment of a special master to perform the privilege review the right ruling? Please share any comments you might have or if you’d like to know more about a particular topic.

Case opinion link courtesy of eDiscovery Assistant.

Sponsor: This blog is sponsored by CloudNine, which is a data and legal discovery technology company with proven expertise in simplifying and automating the discovery of data for audits, investigations, and litigation. Used by legal and business customers worldwide including more than 50 of the top 250 Am Law firms and many of the world’s leading corporations, CloudNine’s eDiscovery automation software and services help customers gain insight and intelligence on electronic data.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine. eDiscovery Daily is made available by CloudNine solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscovery Daily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

Today is the Day for eDiscovery for the Rest of Us!: eDiscovery Webcasts

Does it seem like eDiscovery technology today is only for the “mega-firms” and “mega-cases”? What about for the “rest of us”? Are there solutions for the small firms and cases too? What does the average lawyer need to know about eDiscovery today and how to select a solution that’s right for them?  Find out in our webcast today!

Today at noon CST (1:00pm EST, 10:00am PST), CloudNine will conduct the webcast eDiscovery for the Rest of Us. In this one-hour webcast that’s CLE-approved in selected states, we will discuss what lawyers need to know about eDiscovery, the various sources of data to consider, and the types of technology solutions to consider to make an informed decision and get started using technology to simplify the discovery process. Topics include:

  • How Automation is Affecting All Industries, including eDiscovery
  • Drivers for eDiscovery Automation Today
  • Challenges from Various Sources of ESI Data
  • Ethical Duties and Rules for Managing Discovery
  • Getting Data Through the Process Efficiently
  • Small Case Examples: Ernie and EDna
  • Key Components of an eDiscovery Solution
  • Types of Tools to Consider
  • Recommendations for Getting Started

As always, I’ll be presenting the webcast, along with Tom O’Connor, who wrote a four part blog post series that we have published on the blog in the past couple of weeks.  To register for it, click here.  Even if you can’t make it, go ahead and register to get a link to the slides and to the recording of the webcast (if you want to check it out later).  If you want to know what eDiscovery solution options there within an affordable budget, this is the webcast for you!

So, what do you think?  Do you feel like you can’t afford eDiscovery technology?  Please share any comments you might have or if you’d like to know more about a particular topic.

Sponsor: This blog is sponsored by CloudNine, which is a data and legal discovery technology company with proven expertise in simplifying and automating the discovery of data for audits, investigations, and litigation. Used by legal and business customers worldwide including more than 50 of the top 250 Am Law firms and many of the world’s leading corporations, CloudNine’s eDiscovery automation software and services help customers gain insight and intelligence on electronic data.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine. eDiscovery Daily is made available by CloudNine solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscovery Daily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

Court Grants Adverse Inference Sanction Against Infringing Author: eDiscovery Case Law

In Nunes v. Rushton, No. 2:14-cv-00627-JNP-DBP (D. Utah May 14, 2018), Utah District Judge Jill N. Parrish, ruling that the plaintiff was prejudiced by the deletion of one of the defendant’s Google “sock puppet” accounts, granted the plaintiff’s motion for sanctions in part, ordering an adverse instruction to the jury regarding the “bad faith” deletion of that account.  Judge Parrish denied the motion with regard to several other accounts, ruling that the plaintiff was not prejudiced by deletion of those accounts (as most of the information was still available or recoverable).

Case Background

In this case, the defendant infringed the plaintiff’s copyright in her novel by copying protected elements of the book and distributing copies of the infringing work to reviewers and bloggers for promotional purposes. Around this time, the defendant created a number of “sock puppet” accounts on Google and Yahoo by registering these accounts under usernames that did not identify her as the individual controlling the accounts and used these accounts to create several sock puppet accounts on Facebook, Goodreads, and Amazon. The defendant then used the Goodreads and Amazon sock puppet accounts to post positive reviews of her own books and negative reviews of the plaintiff’s books. The defendant also created a Twitter account and a Blogspot account under her pen name to promote her books.

In August 2014, the plaintiff became aware of the potential infringement, attempted to obtain an advance copy of the infringing novel and discover the true identity of the defendant’s pen name. The defendant used her sock puppet social media accounts to anonymously criticize the plaintiff’s efforts to investigate the infringing novel. Sometime in August or September of 2014, after the plaintiff had discovered the defendant’s identity, The defendant deleted most of her sock puppet accounts. The defendant also deleted her pen name Twitter and Blogspot accounts. The plaintiff filed this lawsuit on August 28, 2014.

During litigation, the plaintiff made a discovery request for documents stored on the defendant’s various Google and Yahoo accounts. On August 12, 2015, while this discovery request was pending, the defendant deleted one of her Google sock puppet accounts.  When the court granted a motion to compel the defendant to produce documents from her Google and Yahoo accounts, counsel for the defendant represented that she had lost the passwords to the accounts, leading to subpoenas to those services.  The defendant deleted all of the remaining accounts on March 21, 2016, asserting that she did so because she believed that all of the documents associated with the accounts had been or would be produced by Google and Yahoo pursuant to the subpoenas.  Google stated that the account deleted on August 12, 2015 could not be recovered because too much time had passed, but preserved the accounts that had been deleted on March 21, 2016.

Judge’s Ruling

In analyzing the defendants’ motion, Judge Parrish denied the motion for sanctions regarding most of the accounts, determining that the plaintiff suffered no prejudice because the information pertaining to those accounts either remained, was saved by the plaintiff before the accounts were deleted or could be recovered by Google and Yahoo.

As for the August 12, 2015 deletion of one of the Google accounts, Judge Parrish stated: “At the time of the deletion, Rushton had a duty to preserve this account because litigation was pending. The court also finds that Nunes was prejudiced by the deletion because any documents or emails stored on this account were irretrievably lost… Given that litigation had been pending for almost a year, that Rushton was represented by counsel, and that Nunes had requested the production of documents associated with this Google account, the court infers that Rushton’s August 12, 2015 deletion of one of her Google accounts was done in bad faith.”

As a result, Judge Parrish ordering an adverse instruction to the jury regarding the “bad faith” deletion of that account.

So, what do you think?  Was an advance inference sanction a severe enough punishment?  Please share any comments you might have or if you’d like to know more about a particular topic.

Case opinion link courtesy of eDiscovery Assistant.

Sponsor: This blog is sponsored by CloudNine, which is a data and legal discovery technology company with proven expertise in simplifying and automating the discovery of data for audits, investigations, and litigation. Used by legal and business customers worldwide including more than 50 of the top 250 Am Law firms and many of the world’s leading corporations, CloudNine’s eDiscovery automation software and services help customers gain insight and intelligence on electronic data.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine. eDiscovery Daily is made available by CloudNine solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscovery Daily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.