California Case Summaries

Thomas Dorobiala v. Apple Inc. — Discovery Order Limiting Analytics Production to Existing Reports

Unreported / Non-Citable

Case
Thomas Dorobiala v. Apple Inc.
Court
U.S. District Court — Northern District of California
Judge
Virginia K. DeMarchi (Judges of the U.S. District Court for the Northern District of California, 2018)
Date Decided
2026-11-12
Docket No.
5:24-cv-01270
Status
Unreported
Topics
discovery dispute, user engagement analytics data, request for production, undue burden, existing reports, motion to seal

Background

In an ongoing civil dispute against Apple Inc., plaintiff Thomas Dorobiala moved to compel the production of third-party user engagement analytics data for cloud storage applications in use since January 1, 2020. Plaintiff specifically sought data fields covering active devices and sessions as well as retention rate, contending they served as an appropriate proxy for the number of unique active users under Request for Production (RFP) 11. Concurrently, plaintiff filed an administrative motion to seal portions of the discovery dispute letter containing information designated by Apple as confidential regarding internal data infrastructure and retention practices.

Apple opposed the requested production, arguing that plaintiff raised the dispute past the applicable deadline, that the requested fields fell outside the scope of RFP 11, and that compiling the data would be unduly burdensome. Following a hearing where plaintiff withdrew his request for proceeds-per-paying-user data, Apple submitted a supplemental statement detailing the engineering, computation, and validation work necessary to generate the requested historical analytics.

The Court’s Holding

The court granted plaintiff's motion to seal as narrowed by Apple, applying the good cause standard for discovery materials under Ninth Circuit precedent and directing plaintiff to file a revised redacted discovery letter. Addressing the discovery merits, the court agreed with Apple that plaintiff delayed past the deadline and that the requested fields were not expressly or reasonably within the scope of RFP 11, notwithstanding plaintiff's plausible argument concerning active devices and sessions as a user proxy.

Nevertheless, relying on Apple's supplemental statement demonstrating that producing reports already generated at the request of third-party developers would avoid burdensome engineering, computation, or validation work, the court ordered Apple to produce only existing, already-generated analytics reports containing the active devices and sessions field. The court explicitly emphasized that Apple is not required to generate non-existent reports or execute new computations, directing the parties to confer on a reasonable production schedule.

Key Takeaways

  • Courts will enforce procedural deadlines and reasonable RFP boundaries to protect parties from disproportionate discovery burdens involving complex analytics generation.
  • Production of proprietary application analytics may be strictly confined to existing, previously generated developer reports rather than requiring new data engineering or validation.
  • Parties seeking to seal sensitive internal infrastructure and retention practices in discovery disputes must satisfy the Ninth Circuit good cause standard.

Why It Matters

The decision highlights the Northern District of California's practical approach to electronic discovery involving large-scale software analytics platforms. By restricting production to reports that developers had already requested and generated, the magistrate judge balanced the plaintiff's need for user engagement proxies against the undue engineering burden of querying historical system repositories.

Read the full opinion (PDF) · Court docket

Scroll to Top