1 2 3 4 UNITED STATES DISTRICT COURT 5 NORTHERN DISTRICT OF CALIFORNIA 6 7 IN RE GOOGLE RTB CONSUMER Case No. 21-cv-02155-YGR (VKD) PRIVACY LITIGATION 8 ORDER RE FEBRUARY 1, 2022 9 DISCOVERY DISPUTES RE PLAINTIFFS’ DOCUMENT 10 REQUESTS TO GOOGLE 11 Re: Dkt. Nos. 141, 143
12 13 Plaintiffs and Google LLC ask the Court to resolve numerous disputes concerning 14 plaintiffs’ document requests to Google. Dkt. Nos. 141, 143. The Court held a lengthy hearing on 15 these disputes on February 8, 2022. See Dkt. No. 151 (transcript). 16 The Court will require Google to produce documents responsive to the following requests, 17 but the scope of the required production is limited as described below: RFPs 1, 2, 3 and 4 (Texas 18 AG only), 7-11, 22(i) and (j), 28, and 30. Google need not produce documents responsive to RFP 19 3 and 4 (other actions), 22(q)(i), 33, and 35. 20 I. BACKGROUND 21 Plaintiffs are Google account holders who allege that Google improperly sells or otherwise 22 discloses to third party companies personal and private information about them through Google’s 23 advertising auction process, which the parties refer to as “real-time bidding” or “RTB.” Google 24 denies that RTB operates in the manner plaintiffs allege and denies that Google sells or otherwise 25 shares Google account holders’ personal information with third parties utilizing RTB without the 26 account holders’ consent. The parties presently are litigating the following eight claims: (1) 27 breach of contract (Count 1); (2) breach of covenant of good faith and fair dealing (Count 2); (3) 1 intrusion upon seclusion (Count 5); (5) publication of private information (Count 6); (6) breach of 2 confidence (Count 7); (7) violation of the California Information Privacy Act, Cal. Penal Code §§ 3 630-638 (Count 8); and (8) violation of the Electronic Communications Privacy Act, 18 U.S.C. § 4 2511—unauthorized interception, use and disclosure by an Electronic Communications Service 5 (ECS) (Count 10). In addition to declaratory and injunctive relief, plaintiffs seek damages, 6 restitution, and disgorgement. See Dkt. Nos. 80, 146. 7 II. DISCUSSION 8 A. Legal Standard 9 A party may obtain discovery of any matter that is relevant to a claim or defense and that is 10 “proportional to the needs of case, considering the importance of the issues at stake in the action, 11 the amount in controversy, the parties’ relative access to relevant information, the parties’ 12 resources, the importance of the discovery in resolving the issues, and whether the burden or 13 expense of the proposed discovery outweighs its likely benefit.” Fed. R. Civ. P. 26(b)(1). 14 B. Disputed Document Requests 15 1. RFP 1: Google’s internal investigations 16 Plaintiffs have narrowed the scope of their demand with respect to RFP 1 and now seek 17 non-privileged documents concerning Google’s internal investigations into the allegations of the 18 complaint. Dkt. No. 141 at 1. As narrowed the request asks for relevant documents and is not 19 unduly burdensome. This request requires Google to: (1) determine whether, after it received 20 notice of the complaint, it conducted any investigations of plaintiffs’ factual allegations, and if so 21 (2) identify the relevant custodians, and (3) produce any non-privileged documents reflecting 22 those investigations. 23 2. RFP 2: Responses to external criticism 24 Plaintiffs ask Google to produce documents created in response to external criticism of 25 RTB, including documents reflecting Google’s consideration of whether to modify RTB, even if 26 no modification was made. Google objects to the breadth of this request to the extent it 27 encompasses changes to RTB that were merely contemplated, but never implemented, and 1 The Court agrees with Google that its obligation to produce documents responsive to RFP 2 2 should be limited to changes actually made to RTB that concern or impact, in any way, the sale 3 or disclosure to third parties of personal and private information about the account holders. The 4 Court is not persuaded that the broader scope of discovery plaintiffs seek will yield relevant 5 information. Plaintiffs have not shown that discovery concerning changes to RTB that Google 6 contemplated but chose not to make is likely to have any bearing on questions of liability or 7 plaintiffs’ damages. 8 3. RFPs 3 and 4: Regulator requests and Google responses 9 Plaintiffs ask Google to produce documents and testimony that Google has previously 10 provided to government regulators and other government agencies relating to data privacy, RTB, 11 or any other matter alleged in the complaint. Specifically, plaintiffs request production of all Civil 12 Investigative Demands (“CIDs”) or equivalent demands, and potentially all responses thereto, in 13 Arizona’s and Australia’s pending actions against Google.1 Plaintiffs also request production of 14 certain categories of documents Google has produced in response to CIDs issued in an action 15 initiated by the Texas Attorney General.2 Google objects to the scope of RFPs 3 and 4 and, in 16 particular, to production of materials relating to the Arizona and Australia actions on the ground 17 that those actions have nothing to do with RTB or with the disclosure of Google account holders’ 18 information to third parties. Google says it has agreed to re-produce to plaintiffs the documents it 19 produced in response to 18 of the Texas AG’s CIDs, but it objects to providing the remaining 20 categories of documents plaintiffs demand. In addition, Google says it has already produced (or 21 agreed to produce) documents from investigation in the United Kingdom that relate to RTB. 22 While plaintiffs are correct that, as a general matter, parties may obtain access to discovery 23 materials gathered or obtained by parties in another litigation, plaintiffs must first demonstrate that 24 the discovery in the other litigation is relevant to the matters at issue. See Foltz v. State Farm Mut. 25 1 State of Arizona ex rel. Mark Brnovich, Attorney General v. Google LLC, No. 2020-006219 26 (Ariz. Superior Ct. 2020); Australia Competition and Consumer Commission v. Google LLC, No. NSD816/2020 (Fed. Ct. of Australia 2020). 27 1 Auto. Ins. Co., 331 F.3d 1122, 1131-32 (9th Cir. 2003). Plaintiffs say that the Arizona action 2 concerns deceptive collection of users’ geolocation data, and that the Australia action concerns 3 misleading promises Google made in its privacy policy regarding account holders’ consent to 4 Google associating their personal information with their activity on third party websites for 5 purposes of targeted advertising. They acknowledge, however, that neither action concerns the 6 sale or disclosure of account holders’ information through RTB, although they contend that there 7 are important and relevant similarities between the conduct being investigated by Arizona and 8 Australia and the conduct at issue here. Plaintiffs say that the Texas AG action concerns Google’s 9 deceptive use of individuals’ personal information to engage in targeted advertising. Google says 10 that the Texas AG action is an antitrust lawsuit that implicates Google’s online advertising 11 business but not the disclosure of personal information to third parties.
Free access — add to your briefcase to read the full text and ask questions with AI
1 2 3 4 UNITED STATES DISTRICT COURT 5 NORTHERN DISTRICT OF CALIFORNIA 6 7 IN RE GOOGLE RTB CONSUMER Case No. 21-cv-02155-YGR (VKD) PRIVACY LITIGATION 8 ORDER RE FEBRUARY 1, 2022 9 DISCOVERY DISPUTES RE PLAINTIFFS’ DOCUMENT 10 REQUESTS TO GOOGLE 11 Re: Dkt. Nos. 141, 143
12 13 Plaintiffs and Google LLC ask the Court to resolve numerous disputes concerning 14 plaintiffs’ document requests to Google. Dkt. Nos. 141, 143. The Court held a lengthy hearing on 15 these disputes on February 8, 2022. See Dkt. No. 151 (transcript). 16 The Court will require Google to produce documents responsive to the following requests, 17 but the scope of the required production is limited as described below: RFPs 1, 2, 3 and 4 (Texas 18 AG only), 7-11, 22(i) and (j), 28, and 30. Google need not produce documents responsive to RFP 19 3 and 4 (other actions), 22(q)(i), 33, and 35. 20 I. BACKGROUND 21 Plaintiffs are Google account holders who allege that Google improperly sells or otherwise 22 discloses to third party companies personal and private information about them through Google’s 23 advertising auction process, which the parties refer to as “real-time bidding” or “RTB.” Google 24 denies that RTB operates in the manner plaintiffs allege and denies that Google sells or otherwise 25 shares Google account holders’ personal information with third parties utilizing RTB without the 26 account holders’ consent. The parties presently are litigating the following eight claims: (1) 27 breach of contract (Count 1); (2) breach of covenant of good faith and fair dealing (Count 2); (3) 1 intrusion upon seclusion (Count 5); (5) publication of private information (Count 6); (6) breach of 2 confidence (Count 7); (7) violation of the California Information Privacy Act, Cal. Penal Code §§ 3 630-638 (Count 8); and (8) violation of the Electronic Communications Privacy Act, 18 U.S.C. § 4 2511—unauthorized interception, use and disclosure by an Electronic Communications Service 5 (ECS) (Count 10). In addition to declaratory and injunctive relief, plaintiffs seek damages, 6 restitution, and disgorgement. See Dkt. Nos. 80, 146. 7 II. DISCUSSION 8 A. Legal Standard 9 A party may obtain discovery of any matter that is relevant to a claim or defense and that is 10 “proportional to the needs of case, considering the importance of the issues at stake in the action, 11 the amount in controversy, the parties’ relative access to relevant information, the parties’ 12 resources, the importance of the discovery in resolving the issues, and whether the burden or 13 expense of the proposed discovery outweighs its likely benefit.” Fed. R. Civ. P. 26(b)(1). 14 B. Disputed Document Requests 15 1. RFP 1: Google’s internal investigations 16 Plaintiffs have narrowed the scope of their demand with respect to RFP 1 and now seek 17 non-privileged documents concerning Google’s internal investigations into the allegations of the 18 complaint. Dkt. No. 141 at 1. As narrowed the request asks for relevant documents and is not 19 unduly burdensome. This request requires Google to: (1) determine whether, after it received 20 notice of the complaint, it conducted any investigations of plaintiffs’ factual allegations, and if so 21 (2) identify the relevant custodians, and (3) produce any non-privileged documents reflecting 22 those investigations. 23 2. RFP 2: Responses to external criticism 24 Plaintiffs ask Google to produce documents created in response to external criticism of 25 RTB, including documents reflecting Google’s consideration of whether to modify RTB, even if 26 no modification was made. Google objects to the breadth of this request to the extent it 27 encompasses changes to RTB that were merely contemplated, but never implemented, and 1 The Court agrees with Google that its obligation to produce documents responsive to RFP 2 2 should be limited to changes actually made to RTB that concern or impact, in any way, the sale 3 or disclosure to third parties of personal and private information about the account holders. The 4 Court is not persuaded that the broader scope of discovery plaintiffs seek will yield relevant 5 information. Plaintiffs have not shown that discovery concerning changes to RTB that Google 6 contemplated but chose not to make is likely to have any bearing on questions of liability or 7 plaintiffs’ damages. 8 3. RFPs 3 and 4: Regulator requests and Google responses 9 Plaintiffs ask Google to produce documents and testimony that Google has previously 10 provided to government regulators and other government agencies relating to data privacy, RTB, 11 or any other matter alleged in the complaint. Specifically, plaintiffs request production of all Civil 12 Investigative Demands (“CIDs”) or equivalent demands, and potentially all responses thereto, in 13 Arizona’s and Australia’s pending actions against Google.1 Plaintiffs also request production of 14 certain categories of documents Google has produced in response to CIDs issued in an action 15 initiated by the Texas Attorney General.2 Google objects to the scope of RFPs 3 and 4 and, in 16 particular, to production of materials relating to the Arizona and Australia actions on the ground 17 that those actions have nothing to do with RTB or with the disclosure of Google account holders’ 18 information to third parties. Google says it has agreed to re-produce to plaintiffs the documents it 19 produced in response to 18 of the Texas AG’s CIDs, but it objects to providing the remaining 20 categories of documents plaintiffs demand. In addition, Google says it has already produced (or 21 agreed to produce) documents from investigation in the United Kingdom that relate to RTB. 22 While plaintiffs are correct that, as a general matter, parties may obtain access to discovery 23 materials gathered or obtained by parties in another litigation, plaintiffs must first demonstrate that 24 the discovery in the other litigation is relevant to the matters at issue. See Foltz v. State Farm Mut. 25 1 State of Arizona ex rel. Mark Brnovich, Attorney General v. Google LLC, No. 2020-006219 26 (Ariz. Superior Ct. 2020); Australia Competition and Consumer Commission v. Google LLC, No. NSD816/2020 (Fed. Ct. of Australia 2020). 27 1 Auto. Ins. Co., 331 F.3d 1122, 1131-32 (9th Cir. 2003). Plaintiffs say that the Arizona action 2 concerns deceptive collection of users’ geolocation data, and that the Australia action concerns 3 misleading promises Google made in its privacy policy regarding account holders’ consent to 4 Google associating their personal information with their activity on third party websites for 5 purposes of targeted advertising. They acknowledge, however, that neither action concerns the 6 sale or disclosure of account holders’ information through RTB, although they contend that there 7 are important and relevant similarities between the conduct being investigated by Arizona and 8 Australia and the conduct at issue here. Plaintiffs say that the Texas AG action concerns Google’s 9 deceptive use of individuals’ personal information to engage in targeted advertising. Google says 10 that the Texas AG action is an antitrust lawsuit that implicates Google’s online advertising 11 business but not the disclosure of personal information to third parties. 12 The claims and defenses in this case may require discovery of: (1) what information about 13 account holders’ is collected by Google and potentially available to third parties through the RTB 14 auction process; (2) how Google obtains consent of account holders to disclose that information to 15 third parties; and (3) what information Google discloses to third parties through RTB and under 16 what circumstances that disclosure is made. While there may be some limited overlap between the 17 relevant discovery in this action and documents and information produced by Google in the 18 Arizona and Australia actions, the Court is not persuaded that the overlap is sufficient to warrant 19 the scope of production plaintiffs demand in RFPs 3 and 4. For example, the fact that Google has 20 made similar promises with respect to its own targeted advertising or has used similar vehicles to 21 obtain consent in contexts other than RTB is too slim a reed to support an order requiring Google 22 to produce all CIDs and responses thereto from the Arizona and Australia actions. Such a 23 production obligation is not proportional to the needs of this case, particularly where plaintiffs 24 may use much more targeted requests for production of documents to obtain the discovery they 25 require. 26 With respect to the Texas AG action, plaintiffs have not shown that the additional 27 categories of documents they have requested are likely to include material relevant to the claims 1 submission (Dkt. No. 143 at 3, 5) do not appear to have anything to do with the sale or disclosure 2 of account holders’ information to third parties generally, or through RTB specifically. Google 3 must specifically identify for plaintiffs the CID categories for which Google will provide 4 responsive documents to plaintiffs from the Texas AG action and must promptly produce those 5 documents, but Google need not produce the additional categories of documents plaintiffs identify 6 in Dkt. 143, Exhibit 2.3 7 4. RFPs 7-11: Interviews, testimony, and op ed 8 In RFPs 7 and 8, plaintiffs ask Google to produce transcripts and recordings of interviews 9 and testimony given to regulators, government bodies, or in court proceedings relating to data 10 privacy, RTB, or any other matter alleged in the complaint, as well as documents compiled by 11 Google in preparation for any such interviews or testimony. In RFP 9, plaintiffs ask Google to 12 produce documents regarding Google’s discussion or analysis of any interview or testimony by a 13 Google employee relating to data privacy, RTB, or any other matter alleged in the complaint. In 14 RFPs 10 and 11, plaintiffs ask Google to produce documents compiled in preparation for Google 15 CEO Sundar Pinchai’s May 7, 2019 opinion editorial in the New York Times (Dkt. No. 92-1, Ex. 16 25), including drafts of the op ed, or comments or discussions about it. Plaintiffs argue that 17 documents concerning prior testimony and statements may contain relevant admissions and other 18 relevant evidence. Google objects that these requests seek broad discovery that encompasses data 19 privacy generally, are not specific to RTB-related matters, and because they include undefined 20 “informal” interviews, it will be difficult for Google to identify or define the scope of responsive 21 documents. Google also objects that these requests target privileged communications. 22 RFPs 7-9: As a general matter, to the extent Google has provided statements or testimony 23 to regulators, government bodies, or in court proceedings that discuss RTB, it must produce non- 24 privileged documents response to RFPs 7-9. Google need not search for or produce responsive 25 documents relating to “informal” interviews, such as statements to the media, because the burden 26 3 The Court is not in a position to resolve the parties’ dispute regarding whether Judge Koh 27 previously ordered Google to produce the entirety of the materials from the Texas AG action. See 1 of identifying and reviewing such materials is not proportional to the needs of the case. The Court 2 also is not persuaded that all interviews or testimony, or documents compiled in preparation 3 therefor, that concern the subject of data privacy generally are likely to yield information relevant 4 to any claim or defense; Google need not search for or produce responsive documents that concern 5 only data privacy generally. 6 RFPs 10-11: The Court has reviewed the Pinchai op ed. While the op ed concerns Google 7 products generally, plaintiffs focus on Mr. Pinchai’s statement that “Google will never sell any 8 personal information to third parties” as a categorical statement that encompasses RTB. See Dkt. 9 No. 141 at 3. It is not clear to the Court from the text of the op ed that Mr. Pinchai meant to 10 encompass RTB when he made this statement. However, to the extent that he or others assisting 11 him with the op ed relied on, referenced, or otherwise compiled documents discussing the 12 operation of RTB, those documents must be produced. Similarly, to the extent drafts of the op ed, 13 or comments or discussions about it, referenced RTB, those documents also must be produced. 14 Given the nature of this op ed, the Court is not persuaded that all materials concerning its 15 preparation or discussion are likely to yield documents relevant to any claim or defense, and so 16 Google need not produce documents concerning only data privacy generally. 17 5. RFP 22: Technical details re use and operation of RTB 18 RFP 22 has multiple subparts, but the parties’ dispute concerns only subparts (i), (j), and 19 (q)(i). Google has agreed to produce documents sufficient to show the information described in all 20 other subparts of RFP 22. Dkt. No. 151 at 58:9-22, 59:8-16. 21 Subparts (i) and (j) are directed to “the location and manner in which Google stores Bid 22 Requests” and “the location and manner in which Google stores user information that is used or 23 may be used in a Bid Request.” While the specific items of user information that may be used or 24 disclosed in the RTB process are relevant to plaintiffs’ claims, Google has already agreed to 25 produce documents sufficient to show this information in response to subpart (e). During the 26 hearing, plaintiffs seemed to suggest that the information sought in subparts (i) and (j) would 27 provide a record of user information actually disclosed to third parties in the RTB process. 1 third parties through the RTB process, it must produce documents sufficient to show what 2 information is shared and how it tracks what information is shared. Otherwise, the Court is not 3 persuaded that the location and manner in which Google stores Bid Requests or the user 4 information that is used or may be used in a Bid Request is relevant to any issue in the case, and 5 Google need not produce these documents. 6 Subpart (q)(i) is directed to documents relating to “the factors, analysis, considerations, 7 and methodologies for selecting the winning bid” in the RTB process. Plaintiffs do not explain 8 why they seek this information, except to say that “these documents go to the market exchange 9 between Google and RTB participants.” Dkt. No. 141 at 3. As it is not clear how Google’s 10 methodology for selecting a winning bid is relevant to any claim or defense, including plaintiffs’ 11 calculation of damages, the Court will not require Google to produce documents responsive to 12 subpart (q)(i). 13 6. RFP 28: Drafts of exhibits attached to complaint 14 Plaintiffs ask Google to produce all documents related to Google’s terms of service, help 15 center pages, and privacy policies, including all drafts and all discussions of drafts and revisions to 16 these materials. Google has agreed to produce earlier versions of these documents and non- 17 privileged drafts. The Court agrees with Google that plaintiffs’ request is too broad. As Google’s 18 proposed scope of production is consistent with the relevance and proportionality requirements of 19 Rule 26, Google shall produce responsive documents consistent with its proposal. 20 7. RFP 30: Analysis and decision-making re RTB-related policies 21 Plaintiffs ask Google to produce “documents regarding Google’s analyses and decision- 22 making practices in the drafting and finalizing of any policy, material, or disclosure made to 23 Account Holders or RTB participants regarding Google’s collection, storage, use and sale of user 24 information, Google’s engagement in targeted advertising and Google’s [RTB],” including 25 specific categories of documents. Google objects to producing documents relating analysis and 26 decision-making for policies, materials, or disclosures regarding collection and storage. Google 27 also objects to producing responsive documents concerning non-U.S. account holders. 1 tells others about collection and storage of user information is not relevant to the claims and 2 defenses in this case, and Google need not produce responsive documents relating to such 3 collection and storage. However, Google’s analysis and decision-making regarding what it tells 4 account holders and RTB participants about the use and sale of user information, Google’s own 5 engagement in targeted advertising, and the RTB process is relevant, and Google must produce 6 documents responsive to this portion of RFP 30. Because the proposed class is limited to U.S. 7 account holders, Google need not produce responsive documents relating to non-U.S. account 8 holders. 9 8. RFP 33: Studies on user engagement and privacy breaches 10 Plaintiffs have narrowed this request and ask Google to produce (1) documents Google 11 prepares on a periodic basis regarding user engagement, either specific to RTB or encompassing 12 RTB, and (2) studies or analyses of how data privacy breaches impact user engagement generally, 13 or specifically with respect to RTB. See Dkt. No. 141 at 4; Dkt. No. 151 at 71:14-75:2. Google 14 objects to this request on several grounds. 15 Having considered the parties’ joint submission and the discussion of RFP 33 during the 16 hearing, the Court finds that plaintiffs’ concept of “user engagement” is not sufficiently well- 17 defined for purposes of this request. For this reason, the Court will not require Google to produce 18 responsive documents regarding period reporting on “user engagement,” or to produce responsive 19 documents regarding studies of how privacy breaches impact “user engagement.” However, the 20 Court will not bar plaintiffs from exploring further whether Google tracks any metrics regarding 21 what RTB participants value when placing a bid request, and if appropriate, seeking discovery of 22 those metrics and whether privacy breaches have some impact on those metrics. 23 9. RFP 35: Google’s market share for all digital advertising 24 Plaintiffs ask Google to produce documents relating to its market share for all digital 25 advertising, including any estimates for the market share derived from RTB. Google objects that 26 this request is unreasonably broad given that RTB is merely one portion of digital advertising. 27 As discussed at the hearing, the Court agrees that the scope of this request is too broad and 1 damages theories, but a request that seeks documents “relating to” market share for “all digital 2 || advertising” encompasses information that is not relevant or proportional to the needs of the case. 3 The parties are directed to confer further regarding whether Google has documents sufficient to 4 show the relevant market sector (e.g., advertiser side) that encompasses RTB, and if possible, 5 RTB’s share of that market sector. With this guidance, the Court expects the parties to be able to 6 reach agreement on this RFP. 7 || I. CONCLUSION 8 The parties shall confer, as appropriate, regarding a schedule for Google’s production of 9 the documents responsive to RFPs 1, 2, 3 and 4 (Texas AG only), 7-11, 22) and (), 28, and 30. 10 || The parties also shall confer regarding the scope of RFP 35. 11 IT IS SO ORDERED. 12 || Dated: April 25, 2022
5 VIRG IA K. DEMARCH nited States Magistrate Judge 16
18 19 20 21 22 23 24 25 26 27 28