Court, Explained
U.S. Federal District Courts
Back to docket
N.D. Cal.Procedural orderFiled Sept. 8, 2023

In re Google RTB Consumer Privacy Litigation

Judge
Yvonne Rogers
Docket
4:21-cv-02155
Court
U.S. District Court · Northern District of California
Pages
11
DiscoveryCivil Procedure
In one sentence

In In re Google RTB Consumer Privacy Litigation, Judge Demarchi ordered Google to provide some requested testimony but not other deposition testimony.

Who this affects

The order affects the plaintiffs and Google by defining which corporate depositions and additional deposition-related discovery Google must provide in the litigation.

What happened

In In re Google RTB Consumer Privacy Litigation, the plaintiffs asked to take more than the 10 depositions normally allowed and asked Google to provide a corporate witness on several topics. Google objected that the requests were unnecessary, repetitive, too broad, or burdensome.

The court allowed plaintiffs to obtain corporate testimony about information in Google’s answers to Interrogatories 11–14 and required testimony on Topic 5 as narrowed by the court. It did not require testimony on Topics 7, 8, or 9, and denied without prejudice the request to automatically allow depositions of employees who might support Google’s class-certification opposition. The court also addressed the timing of the depositions.

Judge Demarchi ordered Google to provide Rule 30(b)(6) testimony on Topics 1, 4, 5 as clarified, and 6, plus four additional topics concerning Google’s interrogatory answers. Google was not required to provide testimony on Topics 3, 7, 8, or 9.

The detailed version

For law students, journalists, and other readers who want the full reasoning

Case
In re Google RTB Consumer Privacy Litigation · No. 4:21-cv-02155
Judge
Yvonne Rogers
Date
Sept. 8, 2023

Background

The parties asked the court to resolve two discovery disputes concerning plaintiffs’ depositions of Google witnesses. First, plaintiffs sought permission to take at least five depositions beyond the 10-deposition limit in Federal Rule of Civil Procedure 30. They identified five Google employees who helped compile information for Google’s answers to Interrogatories 11–14 and also sought advance permission to depose any Google employee who submitted a substantive declaration supporting Google’s opposition to plaintiffs’ class-certification motion.

Second, plaintiffs asked the court to require Google to designate a corporate representative under Rule 30(b)(6). That rule allows a party to question an organization through one or more designated witnesses about matters described with reasonable particularity. The requested topics included Google’s data systems, account-holder consent, document practices, and preservation of information.

Google argued that the additional depositions were cumulative, duplicative, and disproportionate to the needs of the case. It also argued that Topics 5, 7, 8, and 9 sought information outside the permissible scope of discovery, were overbroad, or sought irrelevant information. Google further argued that the depositions should not occur before September 29, 2023, its deadline to oppose class certification.

Additional deposition request

The court found that plaintiffs had made a particularized showing of need for testimony about Google’s recent answers to Interrogatories 11–14. But the court concluded that plaintiffs did not need depositions of each of the five specifically identified employees. Instead, the court ordered Google to prepare corporate designees to testify about:

  1. The creation and maintenance of a spreadsheet produced as GOOG-HEWT-00455648, its data sources, calculations, recording of certain real-time bidding revenues, and Google’s ability to provide similar information for other periods.
  2. The creation and maintenance of another Excel spreadsheet, its data sources, calculations, how Google determined account activity, and the spreadsheet’s time period.
  3. How Google identified and quantified real-time bidding requests associated with each named plaintiff and why its response covered only specified periods.
  4. How Google identified and quantified successful real-time bidding auctions associated with each named plaintiff and why its response covered only specified periods.

The court denied without prejudice plaintiffs’ request for advance permission to depose any Google employee who later submitted a substantive declaration supporting Google’s class-certification opposition because no such declarations had been filed.

Rule 30(b)(6) topics

For Topic 5, the court required Google to provide a corporate designee, but narrowed the topic. The testimony must concern records showing how information shared with real-time bidding participants was logged, mapped, associated, or linked to personal Google accounts in connection with real-time bidding auctions. It does not cover Google’s general collection, creation, or storage of account-holder information. The court overruled Google’s objection to testimony about mapping account-holder information in connection with real-time bidding auctions.

For Topic 7, the court agreed that plaintiffs were entitled to discovery about Google’s consent defense but did not require a separate witness on that topic. Google’s representative was instead required to testify fully about Topic 6, which concerned the mechanisms and procedures for obtaining account holders’ consent to share or sell specified information with third parties outside Google in Google’s real-time bidding system.

For Topic 8, the court denied plaintiffs’ request for testimony about Google employees’ creation, use, maintenance, and retention of emails, chats, presentations, memoranda, and other documents. The court found that plaintiffs had not shown why witnesses’ inability to remember every document they had authored or received justified such a broad inquiry. The court stated that the denial was without prejudice to a more particularized deposition topic if necessary.

For Topic 9, the court did not require testimony about Google’s litigation holds and preservation of data and records. The court found the proposed inquiry too expansive because plaintiffs sought information about preservation efforts throughout the case rather than targeting a particular log or data source. The court suggested that plaintiffs accept Google’s offer to provide verified written responses about data preservation.

Timing and disposition

The court encouraged the parties to agree on dates for Google’s corporate designees to testify promptly after September 29, 2023. It found that plaintiffs had not persuasively explained why the testimony was needed before that date.

The court ordered Google to provide Rule 30(b)(6) testimony on Topics 1, 4, 5 as clarified, and 6, as well as the four additional topics concerning Google’s answers to Interrogatories 11–14. Google was not required to provide Rule 30(b)(6) testimony on Topics 3, 7, 8, or 9. The order was signed by Virginia K. Demarchi, United States Magistrate Judge.

The authoritative version

Read the full 11-page opinion on CourtListener, the free public archive maintained by the Free Law Project.

Open opinion PDF →
Summary written with AI assistance. See how summaries are made. Spot something wrong? Tell us.