Blog

The Platform Holds the Data. That Does Not Mean It Controls It.

A May 2026 ruling separates where data physically lives from who has to produce it, and most subpoena strategies have not caught up.

Your opponent’s data sits in a vendor’s cloud. The obvious move is to go to the vendor, because that is where the servers are. A Northern District of California ruling in May 2026 is a direct warning against that assumption.

The court denied a motion to compel a major HR software provider to produce its customers’ applicant data, holding that the plaintiffs had not shown the provider had control under Rule 34 over data sitting in its own platform. The subscription agreement allowed the provider to disclose customer information when legally required, but only after notice to the customer and subject to the customer’s right to seek an injunction. That, the court held, is not the legal right to obtain the data on demand that Rule 34 control requires.

Possession is not control. The platform operator is a custodian of someone else’s records, and the contract usually says so.

What this changes operationally

  • The right respondent for tenant data is generally the tenant, not the platform. Subpoena strategy built the other way can waste months.
  • Terms of service and master subscription agreements become discovery documents. The control question is answered in a contract most litigation teams have never read.
  • The notice-and-injunction clause that appears in most enterprise SaaS agreements is the specific provision that defeats control. Read it before deciding who to serve.
  • Where a client is the tenant, the client does have control — which means their own export capability, or lack of it, is now their problem to solve.

Export capability is the next question, and it is a real constraint

Having control under Rule 34 does not mean the data comes out cleanly. SaaS platforms vary enormously in what they will let a customer extract and in what form. Some produce clean relational exports. Some offer only canned reports. Some expose data through an interface that was never designed to export at all.

A recurring version of this is the real-time dashboard: a display that assembles from live data and cannot be regenerated to show what it looked like on a past date. A 2022 New Jersey case on exactly that problem ended with the court ordering either screenshot production to the extent possible or a deposition on the system’s capabilities, because nobody could say what the platform could actually do.

That remedy is worth noticing. Where the technical capability is unknown, the court made the producing party put up a witness to explain it.

And the data can simply go away

In September 2025 a Southern District of New York court addressed spoliation where granular web traffic data was lost because the analytics product it lived in was discontinued by its vendor. The remedy limited the plaintiff to presenting that traffic evidence as an approximation derived from the data that remained, and allowed the defendant to raise the loss at summary judgment and at trial.

A vendor retiring a product is a preservation event. Nobody sends a notice about it, it does not appear on anyone’s calendar, and the data is gone on the vendor’s schedule rather than yours.

What to do about all three

Identify, for each SaaS platform in scope, who the tenant is, what the agreement says about disclosure, what export the platform actually supports, and whether anyone has tested it. That is a half-day exercise at scoping and an unrecoverable problem at month nine.

Pro-Legal Services provides forensic data collection, cloud and SaaS collection, ESI processing and defensible production for law firms, corporate legal departments and government agencies across Washington DC, Maryland and Virginia. Where a platform’s export is thin, we test it before anyone relies on it, and we document the method so the limitation is a recorded fact rather than an argument later.

Related: structured data discovery, database production format, forensic data collection services, cloud data collection, litigation hold services, litigation readiness assessment, ESI processing.

Pro-Legal Services, Inc. provides cloud and SaaS collection and ESI processing from Arlington, Virginia, serving law firms, corporate legal departments and government agencies in Washington DC, Maryland, Virginia and nationwide.

Planning a subpoena to a cloud platform? Send us the platform and whose tenant the data sits in. We will tell you whether the operator is the right respondent and what the export will actually produce. Pro-Legal Services, Inc. · 1550 Wilson Blvd, Suite 250, Arlington, VA 22209 · 202-955-9400 · info@pro-legal.com