Uncategorized

Managing Evidence for Government Agencies

Managing Evidence and Data for Government Agencies: Balancing Data Control, FOIA Requirements, and Hybrid Flexibility

For government legal teams, responding to Freedom of Information Act (FOIA) and public records requests involves more than locating and producing documents. It requires reliable search and review practices, careful handling of sensitive information, and effective coordination between legal departments, records managers, and IT professionals.

As electronically stored information (ESI) expands across email, collaboration platforms, mobile devices, and other communication channels, those responsibilities continue to evolve.

For agencies managing investigations, litigation, audits, and public records requests, the technology used to collect, process, review, and produce information can make a meaningful difference. That includes an important decision about where these processes and data residency should take place: on-premise, through Software-as-a-Service (SaaS), or within a hybrid environment.

On-premise platforms for investigations, eDiscovery and other data management processes remain a valuable option for government agencies that require direct control over sensitive information, infrastructure, and technology investments. At the same time, SaaS and hybrid approaches provide flexibility for organizations with different security requirements and minimal or infrequent workloads.

The goal isn’t to choose one deployment model over another. It’s to understand how technology, people, and processes can work together to support efficient, defensible, and legally appropriate information management.

Understanding the Relationship Between FOIA and Modern eDiscovery

FOIA and public records requests play an essential role in government transparency. They give members of the public a means of requesting access to government-held information.

At the federal level, FOIA establishes the right to request access to federal agency records, subject to applicable exemptions. State and local governments operate under their own public records laws, which may differ in scope, terminology, exemptions, and response deadlines.

While FOIA and traditional litigation discovery operate under different legal frameworks, they share many practical challenges.

Both can require teams to identify potentially responsive information, conduct reasonable searches, examine sensitive records, and prepare electronic productions.

Consider a public records request involving several years of communications among agency employees.

Responsive information could potentially exist across emails, attachments, Microsoft Teams conversations, text messages, shared drives, and other electronic systems.

Locating those records is only the beginning.

The agency must also determine which records fall within the request, assess applicable disclosure requirements, identify information that may be withheld, and prepare an appropriate response.

These activities closely resemble the processes eDiscovery professionals use when managing electronically stored information for litigation and investigations.

Established eDiscovery capabilities, including data processing, filtering, searching, review, redaction, and production, can therefore be valuable in supporting public records workflows.

However, agencies must still apply the legal requirements governing the particular request. Federal FOIA, state public records laws, and civil discovery obligations are not interchangeable.

Modern FOIA Requests Begin with Effective Information Governance

One of the biggest challenges facing government legal teams is the variety of locations where electronic records may exist.

Traditional email and shared drives remain important, but government business can also generate records through collaboration applications, mobile messaging platforms, video communications, and other electronic services.

Depending on their content and the applicable law, communications created through these technologies may qualify as government records.

This makes information governance an essential part of responding to public records requests.

In May 2025, the National Archives and Records Administration (NARA) issued updated guidance reminding federal agencies of their records management responsibilities concerning third-party messaging applications, including Signal and WhatsApp.

The guidance reinforced that official agency communications may be federal records even when created through third-party applications or personal accounts.

It also emphasized that electronic records must be managed under applicable retention and disposition requirements.

For government legal teams, this creates an important connection between records management and eDiscovery.

Agencies cannot efficiently search, review, or produce information if they do not understand where relevant records are maintained or whether those records have been properly preserved.

A thoughtful information governance strategy should address record retention, authorized communication platforms, data accessibility, and coordination among legal, records management, and IT teams.

The earlier these responsibilities are established, the easier it becomes to identify and retrieve information when a public records request arrives.

Why On-Premise eDiscovery Still Matters for Government Agencies

Cloud-based technology has transformed how organizations manage information, but on-premise eDiscovery continues to serve an important purpose for agencies with demanding security, operational, and infrastructure requirements.

For government legal teams, maintaining control over information involves more than deciding where files are stored.

It also means understanding how records are accessed, processed, reviewed, protected, and ultimately produced.

Maintaining Direct Control Over Sensitive Information

Government agencies routinely handle information that requires careful management, including confidential investigations, protected personal information, privileged communications, and other restricted records.

An on-premise eDiscovery environment can allow agencies to process and review information within infrastructure they directly administer.

For organizations with established data centers, restricted networks, or specialized security policies, this can provide valuable operational control.

However, not every platform described as on-premise operates entirely within an agency’s network.

Some technologies may require external services for licensing, technical support, system updates, or particular processing capabilities.

Agencies should therefore determine whether a platform can perform the complete required workflow within their own environment, including any restrictions on external connectivity.

An on-premise deployment also brings ongoing responsibilities.

Internal teams must maintain appropriate security controls, access management, software updates, monitoring, and disaster recovery procedures.

Keeping information within an agency’s infrastructure can provide greater direct control, but effective security still depends on how that environment is configured and managed.

Managing Costs Across the Information Lifecycle

Government legal departments often work within carefully planned annual budgets, making long-term cost predictability an important consideration.

SaaS environments may involve recurring charges for hosting, data processing, storage, user access, or other services.

Depending on the pricing model, expenses may change as agencies manage more information or retain matters for longer periods.

On-premise environments offer a different financial structure.

Agencies with existing infrastructure may be able to use those investments to support ongoing eDiscovery activities while reducing certain recurring hosting expenses.

However, internal deployments also involve costs associated with hardware, software, maintenance, staffing, security, and infrastructure upgrades.

For that reason, neither deployment model should automatically be considered more economical.

Legal and technology teams should evaluate the total cost of ownership across the expected lifecycle of their matters.

This includes understanding how expenses may change as data volumes increase, processing requirements evolve, or additional personnel need access.

The most sustainable approach is one that supports an agency’s workload while keeping long-term expenses understandable and manageable.

Managing Modern Data and Increasing Processing Demands

A major investigation, audit, or high-volume public records request can introduce significant amounts of electronically stored information requiring review.

That information may include traditional documents and emails, but it can also involve collaboration messages, mobile communications, audio recordings, video files, and other complex data types.

For legal professionals, these varied formats introduce challenges beyond the amount of storage required.

Teams must be able to identify relevant information, preserve necessary context, and prepare records for review without losing important details.

Modern eDiscovery technology can help through capabilities such as metadata extraction, email threading, deduplication, optical character recognition (OCR), targeted filtering, and document organization.

These tools can reduce repetitive work and help reviewers focus on information that requires closer examination.

Audio and video also deserve consideration. Depending on their responsibilities, agencies may receive requests involving recorded meetings, interviews, surveillance footage, or body-worn camera recordings.

These materials can introduce additional review and redaction requirements that traditional document workflows were not designed to address.

Processing capacity becomes particularly important when requests involve substantial amounts of information.

An on-premise environment may allow agencies to allocate internal computing resources based on their needs. SaaS environments may offer additional capacity without requiring an agency to purchase and maintain all the underlying infrastructure.

Both approaches have potential benefits and limitations.

Agencies should understand how their platforms handle large data volumes, whether processing restrictions apply, and how performance may change during particularly demanding matters.

The objective is to maintain reliable processing and review capabilities even when workloads become more complex or less predictable.

The Growing Role of AI and Automation in Public Records Review

Artificial intelligence and automation are increasingly part of the conversation around modern FOIA administration.

Federal agencies are already exploring and using technologies that assist with document searching, categorization, deduplication, and redaction.

The Department of Justice’s 2026 Chief FOIA Officer Report describes the use of AI-assisted tools and electronic document review capabilities to help streamline aspects of FOIA processing.

These developments demonstrate how technology may reduce repetitive tasks and help teams manage substantial collections of information.

However, using AI in public records workflows introduces additional considerations.

Automated tools may incorrectly classify documents, overlook responsive information, or recommend redactions that require further examination.

For that reason, agencies should understand how automated results are generated, test the reliability of the tools they use, and maintain appropriate human oversight.

Legal professionals remain responsible for applying the relevant disclosure standards and making defensible decisions about the information being released.

Agencies must also consider where information is processed when using AI-enabled technology, particularly if external services are involved.

AI can support the review process, but it should not replace the legal judgment, quality control, and accountability required for government records decisions.

FOIA Compliance: Search, Exemption Review, and Production Quality

A reliable FOIA response requires more than finding potentially responsive documents.

Federal agencies must conduct searches that satisfy applicable legal requirements, evaluate requested records under the relevant exemptions, and respond within the statutory framework.

Under federal FOIA, agencies generally have 20 working days to make and communicate a determination on a properly submitted request, subject to applicable provisions and extensions.

Importantly, this is a deadline for the agency’s determination, not necessarily a requirement to complete the production of every responsive record within that period.

State and local public records laws establish their own response procedures and deadlines.

Applying Exemptions and Protecting Sensitive Information

Federal FOIA includes nine statutory exemptions addressing categories of protected information.

However, identifying a potentially applicable exemption is not always the end of the analysis.

The FOIA Improvement Act of 2016 established a statutory foreseeable-harm standard. Generally, federal agencies may withhold information when they reasonably foresee that disclosure would harm an interest protected by an exemption or when disclosure is prohibited by law.

Agencies must also consider whether nonexempt portions of records can reasonably be segregated and released.

These requirements reinforce the importance of careful document review.

For government legal teams, this means maintaining appropriate procedures for applying exemptions, documenting decisions, and ensuring redactions protect only the information that may lawfully be withheld.

When technology supports automated or assisted redactions, reviewers should verify the results before records are released.

Producing Records in Appropriate Electronic Formats

The format in which information is provided also deserves attention.

Under federal FOIA, agencies must provide records in a requested form or format when they are readily reproducible in that form or format.

Agencies must also make reasonable efforts to search electronically maintained records, subject to the statutory limitation concerning significant interference with their automated systems.

These requirements do not establish a universal rule that every production must contain particular metadata fields or be delivered as a fully searchable native file.

Instead, legal teams should evaluate the applicable requirements, the nature of the records, and the agency’s ability to reproduce information in the requested format.

As a practical matter, preserving document relationships, maintaining appropriate metadata, and producing usable records can help reduce confusion and unnecessary follow-up.

Before release, teams should also verify that redactions are effective, intended documents and attachments are included, and no protected information is inadvertently exposed.

A defensible production process supports both legal compliance and the public’s ability to access information appropriately.

How Hybrid eDiscovery Supports Different Government Workloads

While on-premise eDiscovery can provide valuable direct control, not every government matter requires the same deployment environment.

Some agencies benefit from a hybrid strategy that combines agency-managed infrastructure with appropriately authorized SaaS capabilities.

For example, an agency might maintain sensitive investigative materials within an internal environment while using SaaS technology for other matters when security requirements and organizational policies permit.

This approach can provide flexibility as workloads and operational needs change.

However, an effective hybrid environment requires more than access to both deployment models.

Legal and IT teams should understand how information moves between systems, how permissions are maintained, and whether review procedures and audit trails remain consistent.

They should also assess how records are retained, exported, or deleted across the different environments.

These considerations are especially important when working with information subject to specialized security requirements.

For federal agencies using cloud services, FedRAMP may apply depending on the service and its intended use. Agencies remain responsible for determining whether a service is appropriate for their systems and authorizing that use.

Similarly, the FBI’s Criminal Justice Information Services (CJIS) Security Policy may introduce additional requirements for environments handling covered criminal justice information.

Neither framework should be treated as a universal requirement for every government agency or every eDiscovery matter.

A successful hybrid approach allows agencies to use different technologies where appropriate while maintaining a consistent strategy for security, information governance, and legal oversight.

People, Processes, and Technology: Building More Effective FOIA Workflows

Even the most capable eDiscovery platform cannot resolve every challenge associated with managing public records requests.

Successful programs depend on the relationship between people, processes, and technology.

People: Supporting Legal and Records Teams

Many government agencies depend on relatively small teams to manage requests involving information from several departments.

Establishing a central FOIA or public records coordinator and identifying responsible contacts within departments can improve communication and accountability.

Training is equally important, particularly when employees must work with newer communication platforms or unfamiliar data formats.

Processes: Establishing Repeatable Practices

Clear procedures help agencies manage requests from initial intake through final production.

These procedures should address request tracking, search planning, records collection, exemption analysis, redaction, quality control, approval, and documentation.

They should also account for relevant retention schedules and any preservation obligations associated with litigation or investigations.

Regularly reviewing completed matters can help teams identify unnecessary delays and improve their response practices.

Technology: Supporting the Work Without Adding Complexity

Technology should help employees carry out their responsibilities more efficiently while maintaining appropriate oversight.

For example, case management and eDiscovery tools can help teams track requests, organize responsive records, perform searches, document review decisions, and prepare productions.

The most useful capabilities are those that align with the agency’s actual needs and work effectively within its chosen deployment environment.

By addressing all three elements together, agencies can develop more consistent and sustainable practices for managing FOIA and public records requests.

Want a step-by-step playbook? Download the free FOIA Guide for the 12 most common records-request challenges and how agencies solve them.

Six Questions Government Legal Teams Should Ask When Evaluating eDiscovery Technology

Every agency has different security requirements, operational priorities, budgets, and legal responsibilities.

Before implementing or updating an eDiscovery environment, legal and technical teams should consider several questions.

1. Does the platform provide the level of data control our agency requires?

Can the complete processing and review workflow operate within the agency’s own infrastructure when necessary? Are there external services or connectivity requirements that need to be evaluated before sensitive information is introduced?

2. Can the technology support our FOIA and public records responsibilities?

Does it provide reliable searching, review, redaction, documentation, and production capabilities? Can these functions support the agency’s response procedures and applicable legal deadlines?

3. How predictable are the long-term costs?

Can the agency anticipate licensing, storage, processing, infrastructure, and maintenance expenses? What happens to those costs when data volumes increase, or matters remain active for extended periods?

4. Can the environment handle modern data and substantial workloads?

Does the platform support the electronic records commonly encountered by the agency? Can it process large collections efficiently, and are there licensing or capacity restrictions that may affect performance?

5. How does the deployment align with applicable security and compliance requirements?

Does the environment support the agency’s data governance policies, access controls, retention requirements, and security obligations? Are additional federal, state, or agency-specific requirements relevant to the information being handled?

6. Does the technology support an appropriate hybrid approach?

Can the agency use on-premise and SaaS environments for different workloads when needed? How will information be transferred, secured, tracked, and managed across those systems?

These questions can help government legal teams evaluate technology beyond individual features or deployment preferences.

They also encourage collaboration between the professionals responsible for the legal, technical, and operational aspects of managing government information.

Key Takeaways for Government Legal and eDiscovery Teams

Managing government eDiscovery and FOIA requests requires balancing transparency, security, efficiency, and legal responsibility. While every agency has different needs, several important considerations can help guide a more effective approach.

  • Data control remains a priority. On-premise eDiscovery gives agencies greater direct oversight of their infrastructure and sensitive information. However, maintaining strong security practices and meeting applicable compliance requirements remain essential regardless of the deployment model.
  • Hybrid approaches provide valuable flexibility. Combining on-premise infrastructure with appropriately authorized SaaS solutions allows agencies to manage different workloads based on their security requirements, operational needs, and available resources.
  • Effective FOIA responses begin with sound information governance. As government communications extend across email, collaboration platforms, and mobile applications, knowing where records are stored, how they are retained, and how to retrieve them is increasingly important.
  • Defensible workflows support more reliable outcomes. Consistent searching, exemption review, redaction procedures, documentation, and production quality control help legal teams manage requests while meeting their responsibilities under applicable laws.
  • Modern technology should support people, not replace their judgment. Scalable processing, automation, and AI-assisted capabilities can help reduce repetitive work, but knowledgeable professionals and appropriate oversight remain essential to accurate legal review and disclosure decisions.
  • The right eDiscovery strategy considers long-term needs. Evaluating deployment flexibility, security responsibilities, processing capacity, and total cost of ownership helps agencies make informed technology decisions that can support their teams as requirements evolve.

Ultimately, there is no single eDiscovery environment that meets every government agency’s needs. The most effective approach is one that aligns technology with legal obligations, supports the people managing the work, and maintains appropriate control over information throughout its lifecycle.

Building a More Sustainable Government eDiscovery Strategy

Government legal teams must balance several important responsibilities when managing FOIA requests, investigations, and litigation.

They need to protect sensitive information, comply with applicable legal requirements, support transparency, and make responsible use of their resources.

As communication methods evolve and electronically stored information becomes more complex, these responsibilities require continued attention to information governance, review practices, and technology capabilities.

On-premise eDiscovery remains a valuable choice for agencies that require greater direct oversight of their data and infrastructure.

SaaS and hybrid approaches can offer additional flexibility, provided they align with the organization’s legal, security, and operational requirements.

The right deployment model is ultimately the one that supports the agency’s work without introducing unnecessary complexity.

By combining thoughtful technology decisions with consistent processes and knowledgeable teams, government agencies can strengthen their eDiscovery practices and develop more effective approaches to managing public records requests.

The foundation of that success remains the same: protecting information appropriately, making well-supported decisions, and ensuring the public can access the records it is legally entitled to receive.

FREE WHITE PAPER

THE ULTIMATE GUIDE TO MANAGING PUBLIC RECORDS & FOIA REQUESTS

How federal, state and local agencies use eDiscovery technology, trained teams and repeatable processes to respond faster, without losing control of sensitive information.

Download the FOIA Guide

A smarter approach to privilege review

A Smarter Approach to Privilege Review: Balancing Risk, Cost, and Data Control

Privilege review is one of the most important parts of eDiscovery, but it’s also one of the easiest places for costly mistakes to happen.

An email that includes an attorney isn’t automatically privileged. A Microsoft Teams conversation might contain both business discussions and legal advice. And when thousands of documents are being reviewed under a tight deadline, maintaining consistency across reviewers can become a challenge.

For legal teams, the goal isn’t just identifying privileged information. It’s protecting client communications, making defensible decisions, and keeping the review process efficient without adding unnecessary costs.

In this guide, we’ll explore practical ways to strengthen privilege review, manage modern data types, and use technology to support better decisions, regardless of where your review takes place.

What Is Privilege Review in eDiscovery?

Privilege review is the process of identifying material protected by attorney-client privilege, the work product doctrine, or another applicable protection before documents are produced. It can involve everything from a formal legal memo to a short message buried in a longer Teams discussion.

An attorney’s name on a message does not settle the question. Reviewers still need to understand who was communicating, why, and what the conversation actually says. Just as important, the team needs a consistent way to record those decisions.

A defensible process is not built on the assumption that no one will ever make a mistake. It is built on clear instructions, reasonable checks, and a record of how the team handled the work.

Why Is Privilege Review Difficult in Cloud-Based eDiscovery?

Modern communications rarely fit neatly into one document

Consider a Teams conversation that begins with a business update, moves into legal advice, and ends with a routine operational follow-up. The whole thread may come back in one search, but different parts can raise different privilege questions. Slack, text messages, and other collaboration tools create the same problem.

Reviewing the conversation in context matters more than relying on a sender field or a keyword alone. Your instructions should explain how to handle mixed business and legal discussions.

More reviewers can mean more inconsistent calls

eDiscovery review platforms (both SaaS and On-Premise versions) make it possible for colleagues in different offices to work in the same matter. That helps when deadlines are tight, but it also means people may interpret the same instruction differently. A regular calibration meeting and a clear route for questions can prevent small differences from becoming production issues.

Sensitive data can influence where review happens

Some matters involve client restrictions, regulatory obligations, or data residency requirements. Those constraints may determine whether the team uses a cloud platform, keeps data inside its own environment, or divides matters across both. Make that decision early, before moving sensitive material into a location that may not meet the matter’s requirements.

How to Build a Defensible Privilege Review Workflow

The most useful work often happens before the first reviewer opens a document. A little planning can save your team from revisiting thousands of documents later.

Step 1: Give reviewers rules they can actually use

Start with a written protocol that defines the types of privilege at issue, how to code potentially protected material, and when to escalate a delicate decision. Address dual-purpose communications, attachments, and any common-interest or joint-defense arrangements relevant to the case.

Include an attorney reference list with names, known aliases, email addresses or domains, and law firm identifiers. It will not make every decision automatic, but it will give reviewers a better place to start.

Step 2: Match the decision to the right reviewer

A tiered process gives each person a clear role. First-level reviewers flag likely privileged material. Senior reviewers resolve routine questions and check consistency. Supervising attorneys make the most sensitive decisions and oversee the log. This keeps the work moving without asking junior reviewers to make the hardest calls alone.

Step 3: Use technology to narrow the work, not replace judgment

Search terms, attorney-domain filters, email threading, metadata, and near-duplicate detection can help surface likely privileged material and reduce repeated reading. CloudNine Review brings case data into a searchable workspace, so the team can organize its review instead of juggling disconnected files.

These platforms help you decide where to look. They do not determine whether a piece of communication is legally privileged. That still takes an attorney who understands the facts and the applicable rules.

Step 4: Coordinate privilege and relevance review when practical

If your workflow and staffing allow it, consider assessing relevance, privilege, and confidentiality during the same pass. That can reduce the number of times a document has to be opened. The tradeoff is that reviewers need precise coding guidance and a clear way to send uncertain choices to counsel.

Step 5: Check the work while review is underway

Do not leave quality control until the production date is in sight. Sample completed decisions, compare how reviewers handle similar documents, and document corrections. Keep an audit trail of changes and escalations. Those habits help you find problems while there is still time to address them.

How to Create a Defensible Privilege Log

The privilege log explains what is being withheld and why. A useful log gives opposing counsel enough information to evaluate the claim without revealing the protected substance. The right format depends on the court, the case, and any agreement between the parties.

Choose a format that fits the matter

Traditional document-by-document logs typically identify the author, recipients, date, and basis for withholding. Metadata-based logs use extracted fields and may need additional description. Categorical logs group similar documents, which can reduce repetitive entries when permitted by the governing requirements.

There is no single format that works for every matter. Discuss log expectations early, including treatment of attachments, required fields, and whether categories are acceptable. The Rule 26(f) conference or a comparable early case-planning discussion is a good place to start.

Address inadvertent production before it happens

Consider seeking a Federal Rule of Evidence 502(d) order at the outset. Such an order can protect against privilege waiver from disclosure covered by its terms. It does not take the place of careful review, but it can provide an important safeguard if something is produced by mistake.

Choosing Between On-Premise and Cloud Deployment for Privilege Review

There is no universal answer to where privilege review should run. The better question is what your matter requires and how your team needs to work.

When on-premise review makes sense

Keeping data on your own infrastructure may be the right fit when a client or regulator requires tighter control over storage and access. It can also appeal to teams that want to manage hosting inside their existing environment. CloudNine Review On-Premise is available for teams that need that level of control, without separate cloud hosting fees.

When cloud review makes sense

Cloud review can make it easier for a case team to access the same case data fast through automated processing and hosting since case teams can get started without managing review servers. CloudNine Review (SaaS and On-Premise versions) supports searching, reviewing, and producing material in one place and processes more than 4,800 file types, including phone extraction reports and Slack exports.

When a combination makes sense

Different cases can call for different approaches. A highly sensitive matter may stay on-premise, while another benefits from cloud advantages. Having both options lets you make that decision based on the case rather than force every dataset into the same setup.

Whichever path you choose, confirm your organization’s access controls, retention requirements, and review procedures before the matter begins.

How AI and Generative AI Are Changing Privilege Review

AI-assisted tools can help reviewers spot likely attorney communications, group related material, suggest tags, and summarize documents for closer inspection. Used carefully, those capabilities can focus attention on the items that need it most and help speed up the review process.

But a suggested tag is not a final privilege call. Mixed-purpose advice, common-interest questions, and possible waivers still require legal judgment. If your team uses AI-assisted review, document the approach, test the output, and include it in your normal quality-control process.

CloudNine’s partnership with eDiscovery AI adds options for tasks such as auto-tagging and summarization within CloudNine Review. Your team should still validate the results against its own privilege protocol.

Privilege Review for Modern Data Types

When data comes from phones or collaboration tools, decide early how conversations will be displayed. A flat export can make it harder to tell who said what, when advice was given, and which part of the conversation needs closer inspection.

Where your review tools allow it, keep the thread, participants, timing, and surrounding messages visible when making a call. Review and redact at the appropriate message or conversation level rather than relying only on a flat document export. Preserving context helps attorneys explain why one part of a conversation is withheld and another is not.

Reducing Privilege Review Costs Without Sacrificing Defensibility

Privilege review takes time, and that time affects the client’s bill. The answer is to reduce avoidable work while maintaining the checks that protect the production.

Cut down the review population early

Use early case assessment to narrow dates, custodians, and search terms, then remove duplicates and identify related email threads where appropriate. Every document that can be reasonably excluded from review is one less document someone has to open, code, and potentially revisit.

Make costs explainable before the invoice arrives

Ask how data volume, hosting, users, and additional services affect the estimate. On-premise and SaaS options may have different cost structures, so choose the approach that fits the matter and make sure you can walk your client through the numbers. No one enjoys a surprise bill, so knowing what drives the cost is much more useful than finding out after the deadline.

Bring in help when the workload grows

Some matters outgrow the team available to handle them. CloudNine’s U.S.-based Client Services team can help with bringing data in, developing search terms, and managing project work alongside your case team. That extra support can be especially useful when a new data source arrives late in the schedule.

FAQs About Privilege Review in Cloud eDiscovery

How does a 502(d) order help protect privilege?

A court-entered Rule 502(d) order can prevent disclosure from resulting in privilege waiver to the extent specified by the order. Ask counsel to address it early rather than relying on a clawback discussion after production.

Can AI make the final privilege decision?

AI can help identify and organize material for review, but final privilege decisions belong with qualified legal reviewers who can assess the facts and applicable law.

Is cloud or on-premise better for sensitive matters?

It depends on the client’s requirements, data controls, and team workflow. Some matters call for on-premise review with consumption cost considerations or high volumes; others work well in the cloud where quick uploads and access to smaller matters can be more efficient. You may need both options across your caseload.

What makes a privilege log defensible?

Consistency, accurate information, and enough detail to explain the protection claimed. Agree on the log format early and check entries against your review decisions before production.

Key Takeaways: Privilege Review in Cloud eDiscovery

  • Set privilege rules and an escalation process before review begins, so everyone knows how to handle difficult calls.
  • Treat chat, text, and collaboration data as conversations, not just isolated keyword hits.
  • Build attorney oversight, quality control, and privilege-log planning into the workflow from day one.
  • Choose cloud, on-premise, or a mix based on each matter’s security needs, team, and budget.

A Practical Next Step

Privilege review will always require careful judgment, but the process itself doesn’t have to be unnecessarily complicated.

Clear protocols, consistent oversight, and technology that supports the way your team works can help make privilege review more manageable, even as data volumes and communication methods continue to evolve.

At CloudNine, we’ve spent more than 20 years working alongside legal professionals to help simplify the complexities of eDiscovery. We understand that every matter comes with its own challenges, and finding the right approach starts with understanding your team’s needs.

If you’re looking for ways to make privilege review more efficient while maintaining control over your data and decisions, we’d welcome the opportunity to show you how CloudNine can help.

9 Reasons Why Businesses are Switching to the Cloud (as told by a business consultant)

By guest blogger, Arnold Rogers

As an experienced business consultant, Arnold Rogers has advised businesses across many industries in areas of lead generation, customer experience, service development, and small business cash flow and financial management. He has experience in handling diverse industries, from fast-moving consumer goods to business-to-business hardware retailers. 

Many businesses are switching to the cloud for their day-to-day operations, and you should too. Today’s business climate keeps changing. You should be able to access data on your phone, tablet, or computer, whether in the office, home, or field. This will help you remain competitive. Cloud technology allows employees to access files and work platforms from any place in a secure way. Read on to find out why businesses are switching to the cloud.

Improved Data Security

Any data you store in the cloud is encrypted, making it safe. And since cloud technology is frequently updated, the cloud hosting company will implement the latest cybersecurity measures, ensuring your data isn’t at risk. This is particularly important when you have a lot of customer information you wouldn’t want to lose. Integrating your digital marketing strategies from Digital Spotlight into cloud computing can ensure your tricks remain safe with your business.

Frees Up Your Staff

By switching to the cloud, you free up your staff members to focus on other important things. For instance, if you have hired an IT team, they can now focus on helping other employees with IT needs. Cloud computing also tends to boost employees’ productivity. Users can successfully focus on the task at hand without mixing different software bundles to accomplish tasks.

It’s Flexible

One of the advantages of cloud computing is the flexibility it offers. Your employees can work from whichever location, at whatever time. Considering that 1 in 3 remote employees may quit if asked to return to the office, cloud computing can protect you from such an inconvenience. On the other hand, a business can reduce workstations in the office, saving rental costs. As long as you have fast internet, you’ll continue monitoring your business and employees’ work from whichever corner of the world you’re in.

It’s Scalable

Cloud hosting companies allow businesses to scale depending on their current needs. That means you only pay for what you need. As the business continues growing and your needs change, you can scale up quickly. For instance, you may not need data analysis tools or CRM immediately when you’re a startup. But as you continue expanding, your cloud technology will have to include CRM programs. When that happens, contact your provider, and they will upgrade your package in a few minutes.

Reduces Costs

While it may seem counterproductive, hiring a third party to manage your IT infrastructure is cheaper than hiring an in-house team. With an in-house team, you’ll need to buy hard drives, software, and mobile devices and add workstations. The level of expertise and infrastructure needed to match that of a cloud computing company is expensive. It’s much cheaper to work with a hosting company because you only call them when necessary. At the same time, businesses can save 30% to 50% by switching to the cloud, ultimately saving their running costs.

There’s no Need for a Backup Plan

In the past, computing systems would need backup plans for large amounts of data. Understandably, a company will suffer a financial loss if there’s no backup storage and disaster strikes. When storing data in the cloud, you don’t need any such means to back up your data. That data will always be there whenever users need it. They only need to have internet, and they are good to go. In fact, the cloud itself is your backup plan because the data stored there is safe.

A Variety of Options

There are different cloud computing models which let you choose the option that fits your business. The main models include:

  • SaaS: Software as a service gives businesses access to software through the internet. These applications are available through a desktop client, API, or web browser that integrates with a user’s mobile or desktop operating system. SaaS applications allow workers to download important files and collaborate on projects. Usually, users pay an annual or monthly subscription fee for this service.
  • IaaS: Infrastructure as a service (IaaS) lets you rent IT infrastructure from a provider. This includes virtual machines, servers, storage, and network. Usually, it will be on a pay-as-you-go basis.
  • PaaS: Platform as a service allows software developers to access cloud-based tools like gateway software, APIs, and web portals.

Improved Collaboration at Work

Business owners know just how important collaboration at work can help propel the company forward. One of the ways to boost team performance is through cloud computing. Employees can easily share information and collaborate on projects even when in different locations. Field workers can upload data in real-time, allowing those at the office to get updates. This saves time and eliminates redundant tasks like data re-entry. This level of efficiency increases productivity and saves money.

If you have yet to switch to cloud computing, start looking for a provider. Ensure it’s the right one, as your ability to enjoy the benefits outlined will depend on the provider you go with. You can ask for referrals from businesses that have already switched to cloud computing.

Contact a cloud migration expert at CloudNine here.

7 Hidden Costs of On-Premise Software

The well-documented benefits of moving to the Cloud include speed, security, and scale, but none may impact your business more than cost recovery. To help you analyze how you can enhance your bottom line, we’ve compiled this list of the hidden costs of on-premise software.

  1. Infrastructure – When an organization wants to run a platform within its own environment, there are infrastructure costs that the organization will incur up front, and some will continue over time. Keeping on top of suitable hardware is not only expensive but makes it difficult to scale. A SaaS model makes it easy for companies of all sizes to invest in new technology and expand capacity as needed.
  2. Equipment Constraints – The equipment an organization purchases, leases, or otherwise managers will age over time, and will have to be replaced. Sometimes the replacement will be because of failure related to age. Sometimes the replacement will be due to increasing needs around speed and horsepower for the equipment that is hosting the organization’s platform and data. Sometimes, the equipment you need is on backorder and you are at the mercy of availability. In contrast, there are no infrastructure costs for an organization using a Cloud environment like AWS; this becomes the Cloud provider’s responsibility.
  3. “Always On” – Another infrastructure challenge is that the equipment uses power and energy constantly. Even in highly virtualized environments, customers who want to host their own platforms must pay for the power consumption of computing and storage in their data center. The organization pays for that power whether people are using the platform or not. In a Cloud environment, costs are easier to manage because parts of the environment can be “spun down” and “spun up” depending on user demand, in real-time.
  4. Staffing – A team of highly skilled workers is necessary to maintain an on-premises application or platform. The infrastructure must be maintained physically, security designed and monitored, and you need to deploy and control the systems and networks that allow users and systems to communicate with each other. On top of these resources, staff who have deep technical knowledge of how the platform works behind the scenes may also be necessary.
  5. Database Administrators – Database administrators design and deploy the database that serves as the backbone of many platforms in eDiscovery. Databases such as SQL are often the domain of these administrators. In a Cloud environment, database administration is often provided by the organization offering the Cloud. An organization can still choose to employ its own DBA team, but there are options that can avoid this expense.
  6. Network and System Administrators – Network and system administrators control permissions to various systems, such as folders, servers, and individual workstations. In an on-premises setup, the network or system administrator must design user groups and assign people to those groups – or remove them if needed. In a Cloud-based scenario, this access is handled at the provider level for folder and machine access but can be managed by the organization within individual platforms or databases.
  7. Platform Specialists – Complex platforms can require specialists to operate them to maximize the return on what the platform can do for the organization. These specialists are in high demand, so they command a high salary. This adds to the people costs of an organization. In contrast, in a Cloud environment, platforms are designed to be easy to operate by everyday users, and the “power user” tasks are performed by the platform developers themselves, or by partner organizations that can provide this as a service. This keeps expensive employees off the books of organizations.

To read more about understanding and managing eDiscovery costs, click here.

To use our ESI cost budget calculator and help manage costs, click here.

Click here to schedule a free consultation on how you can quickly and effectively move to the Cloud and save money!

 

Don’t Get Spooked by Communication Applications!

Since Halloween is approaching, it’s time to reflect on a scary part of the discovery process: handling communication applications. As a newer form of digital evidence, communication apps can be a legal team’s worst nightmare. Ephemeral messaging apps like Wickr and Signal make conversations disappear like ghosts in the night. Slack and Microsoft Teams have sunk their teeth into the communications of most corporations. Social media apps have entranced us with a spell, prompting our fingers to type a new DM or tweet every other hour. It’s easy to view these applications as monsters in the discovery process. They have revolutionized the world of e-discovery, expanding it to more than just emails and electronic files.  Whether you love them or hate them, communication apps aren’t going anywhere. In fact, their popularity is only rising. Approximately 2.5 billion people use at least one messaging app on their mobile devices. This number is expected to reach 3 billion by the end of next year. [1] Here’s another chilling statistic: in 2020, 41 million application messages were sent every minute. The volume of communication app data is frighteningly large, but its relevance is undeniable. Regardless of case type, (criminal, personal injury, defamation, etc.) litigants should consider its production. Within each channel and group chat lies a plethora of information that could make or break a case. Still afraid? Here’s a list of challenges and solutions for managing communication applications.

Understanding the missing context:

Messages sent on communication applications are often short and sent with little context. Bits and pieces of conversations might be spread out across multiple platforms and group chats. When handling a case, legal teams should identify all relevant communication platforms to connect the missing dots. Litigants should also consider deriving context from atypical sources such as emojis, liked messages, images, and GIFS. [2] These humorous icons and features can reflect the sender’s tone, a difficult thing to gather over text. Remember, images and emojis aren’t supported in all native file types, so it’s important to find an eDiscovery provider that will reconstruct the conversations. [3]

Managing large volumes of data:

Producing and reviewing voluminous data is stressful, time-consuming, and expensive. By creating comprehensive retention policies, businesses can proactively determine which data types and channels should be preserved. Within the policies, companies should outline the procedures for labeling, storing, and deleting records. [4] The deletion of unneeded data lowers the risk of massive data accumulation.

Remembering each application’s retention policies:

Applications like Slack and Microsoft Teams will retain all messages unless configured otherwise. Similarly, Facebook, Instagram, and Messenger store data until the account has been deleted. [5] If the account owner deletes or unsends a message, the data will still show on the recipient’s phone. Some of these platforms contain “Recently Deleted” features that make recovery much easier. The policies for collaboration and social media applications are rather straightforward. Ephemeral messaging apps are a bit different; however, the auto-deletion features can be adjusted to the user’s discretion. Auto-deletion settings should be turned off during or in anticipation of litigation.

[1] Damjan Jugovic Spajic, “Text, Don’t Call: Messaging Apps Statistics for 2020,” Komando Tech, December 11, 2019.

[2] Erin Tomine, “Chat Messages and eDiscovery: How to Ease the Burden and Get the Full Picture,” Conduent, July 7, 2021.

[3] Matthew Verga, “Discovery from Slack: It’s Complicated,” Xact Data Discovery, June 19, 2020.

[4] Law Offices of Salar Atrizadeh, “Electronic Discovery and Data Retention Policies,” Internet Lawyer Blog, May 18, 2020.

[5] “Data Policy,” Instagram Help Center, 2021.

The Risks and Benefits of Ephemeral Messages

What are Ephemeral Messages?

In the corporate world, Gmail, Microsoft Teams, and Slack are the most common forms of communication. Though these platforms are traditional and efficient, they create privacy and storage challenges. Ephemeral messages counteract these issues by disappearing shortly after the recipient has read the message. [1]

Platforms with disappearing messages:

  • Snapchat
  • Signal
  • Wickr
  • Cover Me
  • Confide
  • Telegram
  • Hash
  • WhatsApp
  • DingTalk

Court Cases Involving Ephemeral Messaging

  • Waymo, LLC v. Uber Technologies, Inc.: In this trade secrets case, Uber’s usage of Wickr and Telegram became a discovery headache. The judge granted both parties the opportunity to argue for or against the relevance of the messages. Thus, the case’s focus shifted from trade secrets to unrecoverable conversations. [2]
  • WeRide Corp v. Huang: After the defendant was accused of intellectual property theft, they took several measures to destroy communication evidence. One of those measures included communicating through DingTalk after the preliminary injunction. Since the messages were destroyed and post-injunction, terminating sanctions were issued. [3]
  • Herzig v. Arkansas Foundation for Medical Care, Inc.: In this age discrimination case, the plaintiffs started using Signal after receiving preservation orders. The judge noted that the plaintiffs manually configured the deletion settings; thus, the case was dismissed for intentional spoliation. [4]

Weighing the Risks and Benefits

Through automated deletion, ephemeral messaging apps eliminate issues concerning data volume. Smaller amounts of data provide greater security from data leaks and reductions in storage costs. Despite these benefits, ephemeral messages are a risky form of communication because they increase the likelihood of spoliation. [5] Spoliation sanctions can range from monetary payments to case dismissal. [6]

Best Practices for Preservation

  • Automated deletion settings should be shut off as soon as a complaint is filed.
  • Create comprehensive policies on managing ephemeral messages. These policies should outline legitimate reasons for the app’s usage, retention information, and destruction guidelines.
  • Train employees on ephemeral messaging etiquette in the workplace.
  • Monitor and document company usage of ephemeral messaging apps. [7]

[1] Dennis Kiker, “Now you see it, now you don’t: Ephemeral messaging may lead to sanctions,” DLA Piper, June 8, 2020, https://www.dlapiper.com/en/us/insights/publications/2020/06/now-you-see-it-now-you-dont-ephemeral-messaging-may-lead-to-sanctions/

[2] Robert M. Wilkins, “Client Litigation Risks When Using Ephemeral Messaging Apps,” Jones Foster, March 5, 2020, https://jonesfoster.com/our-perspective/pbcba-messaging-app-article

[3] Philip Favro, “INSIGHT: California Case Offers Warnings on Ephemeral Messaging,” Bloomberg Law, June 1, 2020, https://news.bloomberglaw.com/esg/insight-california-case-offers-warnings-on-ephemeral-messaging

[4] Scott Sakiyama, “This Message Will Self-Destruct in 5 Seconds,” Corporate Compliance Insights, March 26, 2020, https://www.corporatecomplianceinsights.com/self-destruct-ephemeral-messaging/

[5] Rebecca Cronin, “A Lawyer’s Guide to Ephemeral Messaging,” JD Supra, May 18, 2021, https://www.jdsupra.com/legalnews/a-lawyer-s-guide-to-ephemeral-messaging-4360652/

[6] Michael W. Mitchell and Edward Roche, “Lessons Learned: Destroying Relevant Evidence Can Be Catastrophic in Litigation,” Smith Anderson, https://www.smithlaw.com/resources-publications-1673

[7] Thomas J. Kelly, “The Rise of Ephemeral Messaging Apps in the Business Word,” National Law Review, April 23, 2019, https://www.natlawreview.com/article/rise-ephemeral-messaging-apps-business-world

Heat Wave or Cool Front? Results of the Summer 2019 eDiscovery Business Confidence Survey: eDiscovery Trends

It’s that time again!  I’m here to cover the results of the Summer 2019 eDiscovery Business Confidence Survey, published (as always) on Rob Robinson’s terrific Complex Discovery site.  So, how confident are individuals working in the eDiscovery ecosystem in the business of eDiscovery?  Let’s see.

As always, Rob provides a complete breakdown of the latest survey results, which you can check out here.  As I’ve done for the past few surveys, I will provide some analysis and I’m continuing to take a look at all surveys conducted to look at trends over time.  So, this time, I will look at the results for all fifteen surveys to date, from January 2016 to present.

The Summer 2019 Survey response period was initiated on July 1 and continued until registration of 173(!) responses last week, another high number of participants, thanks in part to support and promotion from the Association of Certified E-Discovery Specialists (ACEDS).

Software and/or Services Provider Reclaim Their Normal Position: After a rare instance of another group (Law Firm respondents) leading in the Spring survey, we’re back to Software and/or Services Provider respondents as the top group with 31.8% of all respondents.  Law Firm respondents weren’t too far behind at 30.6% of all respondents (still higher than last time).  Corporation respondents were third at 15.6%, another high percentage of corporate respondents and Consultancy was fourth at 12.7%.  If you count law firms as providers (they’re technically both providers and consumers), they account for over three-quarters of respondents at 75.1% of total respondents, which is still the second lowest percentage of provider respondents (higher than only last quarter’s 72.2%).  So, expanding the respondents has still continued diversify the responses somewhat.  Here’s a graphical representation of the trend over the fifteen surveys to date.

So, how confident is the largest group of respondents ever in eDiscovery business confidence?  See below.

Most Respondents Consider Business to Be Good (Barely): After the lowest ever number of respondents last time considered business to be good, we saw a 9.8 point rebound to 50.9% of respondents.  While that’s higher than last quarter, it’s lower than the last two summers.  41.6% of respondents consider business to be normal, so the good and normal numbers pretty much flip-flopped from last quarter.  7.5% of respondents rated business conditions as bad, which is comparable to last summer, but higher than two summers ago.  So, was last quarter’s lower current business conditions rating an anomaly?  Hmmm…  Here is the trend over the fifteen surveys to date.

So, how good do respondents expect business to be in six months?  See below.

Most Respondents Expect Business to be the Same Six Months From Now: While most respondents (96.0%) expect business conditions will be in their segment to be the same or better six months from now, that’s a drop of 1.8% as those expecting worse business conditions rose to 4.0% (from 2.2% last quarter), while the percentage expecting business to be the same fell to 56.1%.   More than half of respondents also expected the same on revenues and profits – 51.4% and 57.2% respectively.  When looking at previous summers, this summer reflects the lowest percentage of respondents expecting higher profits at 31.2% (only Winter 2019 was lower at 28%).  Great scott!  Here is the profits trend over the fifteen surveys to date.

Will the trend toward lower future profits predictions continue?  We’ll see.

Cost, Cost, Cost!  Budgetary Constraints Considered to Be Most Impactful to eDiscovery Business: Tag, you’re it!  Budgetary Constraints and Increasing Volumes of Data continued their almost reliable flip-flop between the top two positions, with Budgetary Constraints identified as the top factor this time with 27.2%.  Increasing Volumes of Data dropped back down to second at 22.5%. Increasing Types of Data was once again third at 20.8%, followed by Lack of Personnel at 12.7%, Data Security at 11.6% and Inadequate Technology (once again) bringing up the rear at 5.2%, the lowest number ever for any factor in the history of the survey.  Does this mean most people are happy with their technology?  Hmmm…  The graph below illustrates the distribution over the fifteen surveys to date.

Increasing Volumes of Data, Budgetary Constraints and (now) Increasing Types of Data continue to consistently be at the top of the most impactful factors quarter after quarter.

“Managing” to Be Somewhat Even in Distribution of Respondents: Operational Management respondents were the top group at 37.6%, almost it’s highest level ever (other than 38.9 percent in Fall 2016).  Tactical Execution respondents were second at 35.3% and Executive Leadership respondents were last again at 27.2%, though almost 3 percent higher than last quarter.  Here’s the breakdown over the fifteen surveys to date.

It’s clear that the more respondents we get, the more diverse the results with a much greater influence from the “rank and file” (i.e., managers and technicians).

Again, Rob has published the results on his site here, which shows responses to additional questions not referenced here.  Check them out.

So, what do you think?  What’s your state of confidence in the business of eDiscovery?  Please share any comments you might have or if you’d like to know more about a particular topic.

Image Copyright © Rankin/Bass Productions

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.

A “Random” Idea on Search Sampling: eDiscovery Throwback Thursdays

If you missed it the past couple of weeks, we started a new series – Throwback Thursdays – here on the blog, where we are revisiting some of the eDiscovery best practice posts we have covered over the years and discuss whether any of those recommended best practices have changed since we originally covered them.

This post was originally published on April 4, 2011.  It was part of a three-post series that we started revisiting last week and will conclude the series next week.  We have continued to touch on this topic over the years, including our webcast just last month.  One of our best!

Last Thursday, we talked about how to determine an appropriate sample size to test your search results as well as the items NOT retrieved by the search, using a site that provides a sample size calculator.  Today, we’ll talk about how to make sure the sample size is randomly selected.

A randomly selected sample gives each file an equal chance of being reviewed and eliminates the chance of bias being introduced into the sample which might skew the results.  Merely selecting the first or last x number of items (or any other group) in the set may not reflect the population as a whole – for example, all of those items could come from a single custodian.  To ensure a fair, defensible sample, it needs to be selected randomly.

So, how do you select the numbers randomly?  Of course, many eDiscovery platforms do that for you and enable you to generate your own random sample.  However, to illustrate the concept, we will once again demonstrate here with a web site.

Here’s one site, Random.org, that has a random integer generator which will randomly generate whole numbers.  You simply need to supply the number of random integers that you need to be generated, the starting number and ending number of the range within which the randomly generated numbers should fall.  The site will then generate a list of numbers that you can copy and paste into a text file or even a spreadsheet.  The site also provides an Advanced mode, which provides options for the numbers (e.g., decimal, hexadecimal), output format and how the randomization is ‘seeded’ (to generate the numbers).

In the example from Friday, you would provide 660 as the number of random integers to be generated, with a starting number of 1 and an ending number of 100,000 to get a list of random numbers for testing your search that yielded 100,000 files with hits (664, 1 and 1,000,000 respectively to get a list of numbers to test the non-hits).  Here’s how that looks on the site:

And, here is an example of the beginning of the list of numbers it generates (run it again and it will generate a different set of numbers):

You could paste the numbers into an Excel spreadsheet (Paste Special, then select Text) and sort them.  Here’s how that looks (sort dialog shown with the sort already performed):

You can then retrieve the files by position in the result set (typically Doc ID if you’re doing the entire collection) based on the random numbers retrieved review each of them to determine whether they reflect the intent of the search, which will give you a good sense of how effective your search was, based on the random sample.  And, probably more importantly, using that random sample to test your search results will be a highly defensible method to verify your approach in court.

So, what do you think?  Do you use sampling to test your search results?   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.

Facebook Finally Reveals the Full Extent of the Cambridge Analytica Breach: Cybersecurity Trends

When I see news stories related to eDiscovery, cybersecurity or data privacy that I think would be of interest to our readers, it seems appropriate to share those stories here on this blog.  And this story is no exception.  It appears we finally now fully understand the extent of the Facebook/Cambridge Analytica breach from a few years ago.

According to the DailyER (Facebook relieved to discover data breached was just millions of minion memes, written by Chris Goehring), a newly released report confirmed the only data Cambridge Analytica accessed during the U.S. presidential campaign season a few years ago from 50 million Facebook users was millions of minion memes.

As you may recall, minion memes gained popularity on Facebook after the first Despicable Me movie was released in 2010.  Three years later, the popularity of minions was extended with the sequel Despicable Me 2 – sadly, it wasn’t until 2015 that the minions got their own movie, appropriately titled Minions.

A typical minion meme features one or more minions, which are goofy yellow characters from the movies who speak in gibberish, along with a funny saying in the background that is relatable to a group of people in some way. Here are some examples in a photo with Facebook CEO Mark Zuckerberg:

The minion memes have been a hit among suburban moms who constantly share the memes on their Facebook pages.

“I can’t believe someone stole all my funny minion memes!” exclaimed Lincoln, NE native Sharon Smith, mother of two loving children and grandmother to three grandchildren. “I can’t believe Facebook would let hackers access my data! If they let those hackers take any of my personal information, I’m gonna dab on those haters, LOL! Watch me whip and nae-nae!”

According to the article, Zuckerberg spoke about the scandal in a recent press release.

“Thank God they didn’t take any sensitive information,” said Zuckerberg. “This really could have been a huge disaster. What a relief it is they only took the minion memes. Hopefully, they don’t find the millions of credit card numbers I put on Craigslist last night. Now THAT would be a disaster.”

As they used to say in the old days, “that’s all the news that’s fit to print” on this, the first day of April, 2019.  ;o)

So, what do you think?  Did you have any minion memes on Facebook during this time?  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 Target for Failing to Preserve Surveillance Video: eDiscovery Case Law

In Decker v. Target Corp., No. 1:16-cv-00171-JNP-BCW (D. Utah Oct. 10, 2018), Utah District Judge Jill N. Parrish granted in part and denied in part the plaintiffs’ for a finding of spoliation and for sanctions, granting the plaintiffs’ request for sanctions for failing to preserve more of the video surveillance footage of the plaintiff’s trip and fall accident, but denied the plaintiffs’ request for sanctions for failing to preserve training records and the store’s safety statistics and records for 2015.

Case Background

In this trip and fall dispute where the plaintiff tripped on a flatbed stocking cart and fell onto the floor (suffering serious injury that required transport from Target by ambulance) in December 2015, two defendant employees reviewed video surveillance footage of the incident and created a copy of the portions of the video that included the plaintiff in the frame. The defendant employees did not save any other portions of the video. The unsaved portions of the footage were later automatically overwritten by the defendant’s system, which only maintains video surveillance footage for approximately fifteen to twenty-five days.

Exactly one month after the incident, the plaintiffs delivered a letter to the defendant, through counsel, requesting preservation of “all pertinent records and electronic records pertaining to [the] incident or that could relate to [the] incident,” as well as “a copy of any video surveillance that shows [the] accident or the area of the accident at any time before, during, or after the event.”  The parties subsequently engaged in several rounds of discovery and document production and the plaintiffs specifically requested the defendant’s training records and safety statistics from 2015.

On June 8, 2018, the plaintiffs filed a motion for a finding of spoliation and for sanctions for the defendant’s failure to preserve more of the video surveillance footage of the accident, and failing to preserve training records and the store’s safety statistics and records for 2015.

Judge’s Ruling

Noting that “[t]o be entitled to an adverse inference instruction, the Deckers must establish that Target acted in bad faith in failing to preserve the evidence at issue”, Judge Parrish stated:

“The video footage as issue was reviewed shortly after the incident by two Target employees, Mackenzie Steele and Trevor Phillips. The employees testified that they decided not to preserve the portions of the footage where Mrs. Decker was not present because they did not believe they were relevant. In so doing, they acted in violation of Target policy requiring that employees preserve video surveillance footage showing twenty minutes before and twenty minutes after any such incident. The employees represented that they were not aware of this policy. Were the court to evaluate their actions individually, the court would not conclude they acted in bad faith. But these employees were not acting as individuals, they acted as agents of Target, and the court concludes that Target has acted in bad faith in regards to the evidence. First, Target failed to instruct its employees regarding Target policy of what footage to preserve. Second, Target employees failed to preserve all relevant footage. And third, Target’s counsel now seeks to take advantage of the evidence that Target failed to preserve by arguing that the flatbed cart was attended or worked by Target employees during the gap in the video. It is this attempt to take advantage of a situation that Target caused that leads the court to conclude Target acted in bad faith. The court will therefore instruct the jury to make the adverse inference that the flatbed cart was unattended for the twenty minutes prior to the accident.”

However, Judge Parrish also stated that “The Deckers are not entitled to an adverse inference instruction regarding the training records because the Deckers have not established that the allegedly destroyed records were ever created.”  And, she also denied the plaintiffs’ request for sanctions regarding the lack of safety statistics, stating: “General safety statistics do not indicate whether Target was negligent in leaving the flatbed cart in the aisle.”  But, she did caution the defendant that its failure to produce its safety statistics would prevent it from offering any evidence that the store had high safety scores at the time of the accident.

So, what do you think?  Should a party be held to the bad faith standard when their employees fail to adhere to company policy?  Please let us know if 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.

  • 1
  • 2