Unreported / Non-Citable
Background
Plaintiffs Christina Riganian and others served Request for Production 64 (RFP 64) on defendant LiveRamp Holdings, Inc., seeking all documents LiveRamp produced in any government investigation, regulatory inquiry, or law enforcement request related to its collection, use, sale, or sharing of personal information. During the parties' meet-and-confer, the plaintiffs identified a U.S. House Committee investigation into LiveRamp's data practices and user profiles. LiveRamp agreed to produce responsive, non-privileged documents submitted to the House Committee but refused to produce other documents under RFP 64.
The plaintiffs moved to compel a full response to RFP 64, narrowed to investigations expressly regarding privacy. In the parties' joint statement, the plaintiffs also cited a Federal Trade Commission (FTC) investigation alleging that Avast Ltd. collected user browsing data through antivirus products and illegally sold it to LiveRamp for targeted advertising, arguing that the FTC's inquiry directly related to their claims. LiveRamp did not address the Avast investigation in its portion of the joint statement.
The Court’s Holding
U.S. Magistrate Judge Alex G. Tse declined to compel LiveRamp to respond further to RFP 64, classifying it as disfavored 'cloned discovery' seeking all documents produced or received in other litigation or investigations. Because different investigations have different scopes, a court cannot evaluate overbreadth unless the requesting party identifies a specific case or investigation and describes its subject matter in detail. Beyond the House Committee inquiry, the plaintiffs sought records from unidentified investigations.
Although the plaintiffs tried to limit RFP 64 to privacy-related investigations, their definition of 'related to' covered matters concerning a topic 'in whole or in part.' That definition would force LiveRamp to produce all documents shared in an investigation touching on privacy only in part, including documents on unrelated issues. Because similarities between matters do not justify carte blanche production, the court denied further production under RFP 64. However, the court ordered that by December 1, 2026, the parties must meet and confer to discuss whether discovery from the FTC investigation of Avast would be appropriate, with leave to file another joint statement if a dispute remains thereafter.
Key Takeaways
- Blanket requests for all documents produced in other litigation or government investigations are disfavored cloned discovery because differing scopes across matters make wholesale production overbroad.
- A party seeking cloned discovery must identify a specific prior case or investigation and describe its subject matter in detail so the court can assess relevance and overbreadth.
- Narrowing a request to 'privacy-related' investigations does not cure overbreadth when a broad definition of 'related to' requires carte blanche production from any investigation touching privacy only in part.
- A court may deny an overbroad cloned discovery motion while ordering the parties to meet and confer by a set deadline on whether discovery from a specifically identified investigation is appropriate.
Why It Matters
The ruling illustrates the limits on using government investigative productions as a discovery shortcut in private privacy litigation: subject-matter similarity does not justify a carte blanche transfer of another inquiry's document set when broad definitions could sweep in unrelated issues.
By ordering the parties to meet and confer by December 1, 2026 regarding the FTC's Avast investigation, the court distinguished open-ended demands covering unidentified inquiries from targeted discovery tied to a specific, described enforcement matter.