Rodriguez v. Google LLC ( 2024 )

1 2 3 4 5 6 7 UNITED STATES DISTRICT COURT 8 NORTHERN DISTRICT OF CALIFORNIA 9 ANIBAL RODRIGUEZ, et al., 10 Case No. 20-cv-04688-RS Plaintiffs, 11 v. ORDER GRANTING MOTION TO 12 CERTIFY CLASS AND DENYING GOOGLE LLC, DAUBERT MOTION 13 Defendant. 14 15 I. INTRODUCTION 16 Plaintiffs Anibal Rodriguez, Sal Cataldo, Julian Santiago, and Susan Lynn Harvey are 17 users of third-party apps to which Google provides services. Plaintiffs bring a putative class action 18 against Defendant Google LLC with three claims: invasion of privacy, intrusion upon seclusion, 19 and violation of the Comprehensive Computer Data Access and Fraud Act (CDAFA), Cal. Penal 20 Code § 502, et seq. Pursuant to Federal Rules of Civil Procedure 23(b)(3) and 23(b)(2), they seek 21 certification of nationwide classes of all Google users who had their “Web & App Activity” 22 (“WAA”) and/or “supplemental Web & App Activity” (“sWAA”) switched off in their Google 23 privacy settings since July 1, 2016. 24 Concurrently, Google moves to exclude the opinion by Plaintiffs’ damages expert, Michael 25 J. Lasinski, pursuant to Federal Rule of Evidence 702 and Daubert v. Merrell Dow 26 Pharmaceuticals, Inc., 509 U.S. 579 (1993). Lasinski submitted a report to calculate class-wide 27 unjust enrichment and actual damages for Plaintiff’s two proposed classes. For the reasons below, 1 II. BACKGROUND 2 This is a putative class action challenging Google’s data practices. See Fourth Amended 3 Complaint (“FAC”). The factual history of this case has been discussed at length in previous 4 orders. In sum, Plaintiffs aver Google contravenes its representations to its WAA-off and sWAA- 5 off users when it collects, saves, and uses their data from third-party apps built with the Firebase 6 and/or Google Mobile Ads Software Developer Kits (“SDKs”). Google admits that it collects this 7 data but, for sWAA-off users, it does so only for “basic record-keeping” of its advertising services 8 and to store and analyze data for the third-party app developers. Opp. at 1. Plaintiffs now move to 9 certify two classes: 10 Class 1: All individuals who, during the period beginning July 1, 2016 and continuing through the present (the “Class Period”), (a) had their 11 “Web & App Activity” and/or “supplemental Web & App Activity” setting turned off and (b) whose activity on a non-Google-branded 12 mobile app was still transmitted to Google, from (c) a mobile device running the Android operating system, because of the Firebase 13 Software Development Kit (“SDK”) and/or Google Mobile Ads SDK. 14 Class 2: All individuals who, during the Class Period (a) had their “Web & App Activity” and/or “supplemental Web & App Activity” 15 setting turned off and (b) whose activity on a non-Google-branded mobile app was still transmitted to Google, from (c) a mobile device 16 running a non-Android operating system, because of the Firebase SDK and/or Google Mobile Ads SDK. 17 Class Cert. Mot. at 1. To support their motion, Plaintiffs proffer the opinion of Lasinski, 18 the Senior Managing Director at Ankura Consulting Group (“Ankura”) and head of the Intellectual 19 Property group. Lasinski’s report calculates class-wide damages for Plaintiffs’ proposed classes 20 under two damages theories, one based on unjust enrichment to Google, and another based on 21 actual damages to Plaintiffs. Under the unjust enrichment theory, Lasinski provides calculations 22 for two damage scenarios. Lasinski’s first model, “Scenario One,” provides for damages equal to 23 “the portion of Google’s U.S. App Promo, AdMob, and Ad Manager app ads revenues and profits 24 attributable to Google’s collection, saving, and/or use of WAA/sWAA-Off Data for purposes of 25 tracking advertising conversions” which he calculates to be approximately $558.8 million. 26 Lasinski Rep. 1. Alternatively, Lasinski provides a second model, “Scenario Two,” which 27 1 calculates damages equal to “the portion of Google’s U.S. App Promo, AdMob, and Ad Manager 2 app ads revenues and profits attributable to Google’s collection, saving, and/or use of 3 WAA/sWAA-Off Data for purposes of serving and monetizing advertisements” totaling 4 approximately $664.3 million.1 Id. Lasinski also calculated actual damages for the proposed 5 classes as the value to an individual knowingly to surrender their choice to keep their app data 6 private and allow an organization to track their data. Id. at 2. Lasinski estimated damages based on 7 baseline monthly compensation provided to participants in a Google consumer research study, the 8 Ipsos Screenwise Panel. The baseline compensation to participants was $3 per device per month, 9 so Lasinski applied a one-time $3 payment to the number of Class Member Devices, totaling 10 $486.0 million approximately. Id. Google filed a Daubert motion as to Lasinski’s opinions. 11 III. LEGAL STANDARD 12 A. Class Certification 13 Class actions are governed by Rule 23 of the Federal Rules of Civil Procedure. To obtain 14 class certification, plaintiffs bear the burden of showing they have met each of the four 15 requirements of Rule 23(a) and at least one subsection of Rule 23(b). Zinser v. Accufix Rsch. Inst., 16 Inc., 253 F.3d 1180, 1186 (9th Cir. 2001), amended by 273 F.3d 1266 (9th Cir. 2001). Plaintiffs 17 must establish these requirements by a preponderance of the evidence. Olean Wholesale Grocery 18 Cooperative, Inc. v. Bumble Bee Foods LLC, 31 F.4th 651, 665 (9th Cir. 2022) (en banc). 19 Class certification is proper if four conditions are met: “(1) the class is so numerous that 20 joinder of all members is impracticable; (2) there are questions of law or fact common to the class; 21 (3) the claims or defenses of the representative parties are typical of the claims or defenses of the 22 class; and (4) the representative parties will fairly and adequately protect the interests of the class.” 23 Fed. R. Civ. P. 23(a). These requirements are commonly referred to as numerosity, commonality, 24 typicality, and adequacy of representation, respectively. Mazza v. Am. Honda Motor Co., Inc., 666 25 26 1 According to Lasinski, “[t]hese Scenario One and Two amounts represent approximately 5.27% and 6.27%, respectively, of Google’s U.S. revenues net of traffic acquisition costs from App 27 Promo, AdMob, and Ad Manager for apps” between July 1, 2016 and December 31, 2022. 1 F.3d 581, 588 (9th Cir. 2012). 2 If all four Rule 23(a) prerequisites are satisfied, plaintiffs must also “satisfy through 3 evidentiary proof” at least one of the three subsections of Rule 23(b). Comcast Corp. v. Behrend, 4 569 U.S. 27, 33 (2013). Rule 23(b)(3) requires that “the questions of law or fact common to class 5 members predominate over any questions affecting only individual members, and that a class 6 action is superior to other available methods for fairly and efficiently adjudicating the 7 controversy.” Fed. R. Civ. P. 23(b)(3). Such common questions need only be capable of class- 8 wide resolution; plaintiffs are not required to show that “the evidence in fact establishes [they] 9 would win at trial.” Olean, 31 F.4th at 667. Rule 23(b)(2) requires that “the opposing party has 10 acted or refused to act on grounds that apply generally to the class” and “final injunctive relief or 11 corresponding declaratory relief is appropriate respecting the class as a whole.” Fed. R. Civ. P. 12 23(b)(2). A court may certify a 23(b)(2) class and 23(b)(3) class separately. In re ConAgra Foods, 13 Inc., 302 F.R.D. 537, 573 (C.D. Cal. 2014) (“Ninth Circuit precedent indicates that the court can 14 separately certify an injunctive relief class and if appropriate, also certify a Rule 23(b)(3) damages 15 class”). 16 B. Daubert 17 Federal Rule of Evidence 702 requires that a witness proffered as an expert by a party be 18 qualified by “knowledge, skill, experience, training, or education.” Fed. R. Evid. 702. Even if a 19 witness is qualified as an expert in a particular field, any scientific, technical, or specialized 20 testimony is admissible only if it (a) “will help the trier of fact to understand the evidence or to 21 determine a fact in issue,” (b) “is based upon sufficient facts or data,” (c) “is the product of 22 reliable principles and methods,” and (d) “the expert has reliably applied the principles and 23 methods to the facts of the case.” Id. 24 Irrelevant or unreliable testimony is prohibited under Rule 702. Daubert v. Merrell Dow 25 Pharm., Inc., 509 U.S. 579, 589 (1993). Expert opinions are relevant if the knowledge underlying 26 them has a “valid connection to the pertinent inquiry.” United States v. Sandoval-Mendoza, 472 27 F.3d 645, 654 (9th Cir. 2006) (internal quotation marks and alteration omitted). “Expert testimony 1 which does not relate to any issue in the case is not relevant and, ergo, non-helpful.” Daubert, 509 2 U.S. at 590. Expert opinion testimony is reliable if such knowledge has a “basis in the knowledge 3 and experience of [the relevant] discipline.” Id. at 592. Under Daubert, courts should consider the 4 following factors when evaluating whether an expert’s proposed testimony is reliable: (1) 5 “whether a theory or technique . . . can be (and has been) tested,” (2) “whether the theory or 6 technique has been subjected to peer review and publication[,]” (3) the known or potential error 7 rate of the particular scientific theory or technique, and (4) the degree to which the scientific 8 technique or theory is accepted in a relevant scientific community. Id. at 593–94. This list is not 9 exhaustive, however, and the standard is flexible. Kumho Tire Co. v. Carmichael, 526 U.S. 137, 10 151 (1999). The Daubert inquiry “applies not only to testimony based on ‘scientific’ knowledge, 11 but also to testimony based on ‘technical’ and ‘other specialized’ knowledge.” Id. at 141. 12 The court’s task is not to “decid[e] whether the expert is right or wrong, just whether his 13 testimony has substance such that it would be helpful to a jury.” Alaska Rent-A-Car, Inc. v. Avis 14 Budget Grp., Inc., 738 F.3d 960, 969–70 (9th Cir. 2013). Courts may not exclude testimony 15 simply because it is impeachable. Id. at 969. “Vigorous cross-examination, presentation of 16 contrary evidence, and careful instruction on the burden of proof are the traditional and 17 appropriate means of attacking shaky but admissible evidence.” Daubert, 509 U.S. at 596. The 18 focus of the inquiry is thus on the principles and methodology employed, not the conclusions 19 reached by the expert. See id. at 595. Ultimately, the purpose of the assessment is to exclude 20 speculative or unreliable testimony to ensure accurate, unbiased decision-making by the trier of 21 fact. 22 IV. DISCUSSION 23 A. Class Certification 24 Plaintiffs contend their claims warrant class-wide treatment because they satisfy the four 25 23(a) requirements, common questions predominate over individual ones pursuant to 23(b)(3), and 26 they seek uniform equitable relief from Google’s conduct per 23(b)(2). Plaintiffs seek application 27 of California law to all claims. Defendants do not raise any choice-of-law related objections and 1 focus on California law in opposing Plaintiff’s motion for class certification. 2 I. 23(a) requirements 3 Plaintiffs meet the four 23(a) requirements of numerosity, commonality, typicality, and 4 adequacy. Class 1 proposes Android users, while Class 2 proposes non-Android users, who during 5 the class period had their WAA/sWAA settings turned off and had their data transmitted to Google 6 while using non-Google branded apps. 7 a. Numerosity 8 First, each of the proposed classes contain members so numerous that class-wide treatment 9 is appropriate. The numerosity prong of Rule 23(a) requires joinder to be “impracticable.” Fed. R. 10 Civ. P. 23(a)(1). There is no numerical cut-off to determine whether this requirement has been 11 met. Gen. Tel. Co. v. EEOC, 446 U.S. 318, 330 (1980). Instead, a fact-specific inquiry may be 12 used to determine whether joinder would be impracticable. Id. Here, each of Plaintiffs’ proposed 13 classes constitute millions of users, so this condition is satisfied. 14 b. Commonality 15 Next, Plaintiffs proposed classes satisfy the commonality requirement because their claims 16 pose common “questions of law or fact.” Fed. R. Civ. P. 23(a)(2). Plaintiffs suggest that common 17 questions include whether Google has “permission” to collect third party app data based on the 18 “objective meaning” of Google’s sWAA disclosures. Id. Plaintiffs’ claims raise a “common 19 contention” as to Google’s conduct, and the “determination of its truth or falsity will resolve an 20 issue that is central to the validity of each one of the claims in one stroke.” Wal-Mart Stores, Inc. 21 v. Dukes, 564 U.S. 338, 350 (2011). Therefore, Plaintiffs meet the commonality requirement. 22 c. Typicality 23 Named plaintiffs’ individual claims are also typical of those of the proposed class 24 members. See Fed. R. Civ. P. 23(a)(3). “The purpose of the typicality requirement is to assure that 25 the interest of the named representative aligns with the interests of the class.” Hanon v. 26 Dataproducts Corp., 976 F.2d 497, 508 (9th Cir. 1992). All named plaintiffs are Google users who 27 used third-party apps with the Firebase and/or Google Mobile Ads SDKs. Named Plaintiffs 1 Rodriguez, Cataldo, and Harvey are Android users and aver claims typical of Class 1, while 2 named Plaintiff Santiago uses an Apple device and avers claims typical of Class 2. 3 d. Adequacy 4 Finally, Plaintiffs and their counsel “fairly and adequately protect the interest of the 5 class[es].” Fed. R. Civ. P. 23(a)(4). Two questions determine adequacy: “(1) do the named 6 plaintiffs and their counsel have any conflicts of interest with other class members and (2) will the 7 named plaintiffs and their counsel prosecute the action vigorously on behalf of the class?” Hanlon 8 v. Chrysler Corp., 150 F.3d 1011, 1020 (9th Cir. 1998). Plaintiffs and their counsel have shown no 9 conflicts of interest, and Google has not asserted any. Further, Plaintiffs and their counsel state in 10 their declaration that they are committed to the prosecution of this matter on behalf of the 11 proposed classes. Thus, this requirement is satisfied. 12 II. 23(b)(3) 13 Rule 23(b)(3) certification requires Plaintiffs to satisfy two conditions: predominance and 14 superiority. See Fed. R. Civ. Pro. 23(b)(3). To meet the predominance requirement, Plaintiffs do 15 not need to show an absence of individual claims, only that the claims that may be resolved class- 16 wide predominate over individual ones. See Dukes, 564 U.S. at 359. “Considering whether 17 ‘questions of law or fact common to class members predominate’ begins, of course, with the 18 elements of the underlying cause of action.” Erica P. John Fund, Inc. v. Halliburton Co., 563 U.S. 19 804, 809 (2011). The second requirement under 23(b)(3) is that class treatment is the superior 20 method of fairly and effectively adjudicating the instant controversy. Fed. R. Civ. P. 23(b)(3). 21 The parties’ primary dispute concerns whether common or individual questions 22 predominate. Plaintiffs argue they do because the central issues in this action, specifically what 23 Google represented and the technical functioning of Google’s SDK technology, “turn on common 24 questions” and “are subject to common proof.” Class Cert. Mot. at 9. Conversely, Google argues, 25 first, that the averred harms are individualized, and even if not, they cannot be determined on a 26 class-wide basis. Google further argues that even if both harms and damages can be determined 27 class-wide, it would thereby be unfairly precluded from asserting its implied and explicit consent 1 defenses. It insists that Plaintiffs failed to identify a single California mass torts case that certified 2 a class for a “privacy tort claims (or CDAFA)” because “these claims are inherently personal, and 3 the nature, extent, and frequency of injury and damage are highly individualized issues that are 4 typically unsuitable for class treatment.” Opp. at 12; but see McDonald v. Kiloos ApS, 385 F. 5 Supp. 3d 1022, 1034 (N.D. Cal. 2019) (a putative class action with intrusion upon seclusion and 6 invasion of privacy claims, in which the Court held that Plaintiffs had adequately pleaded the 7 offensiveness element); see also Order Concerning: (1) The Parties’ Expert Exclusion Motions; 8 and (2) Plaintiffs’ Class Certification Motion, Csupo, et al. v. Alphabet, Inc., 19CV352557 (Super. 9 Ct. Santa Clara Oct. 26, 2023) (certifying a class in which the plaintiffs, under theories of 10 conversion and quantum meruit, alleged that the defendant used their cellular data allowances 11 without consent).2 Thus, according to Google, common questions fail to predominate over 12 individual ones. 13 The intrusion upon seclusion and invasion of privacy claims are increasingly discussed 14 together because they entail similar elements, “[a]lthough the claims do continue to exist as 15 separate claims with technically distinct elements.” McDonald v. Kiloo ApS, 385 F.Supp.3d 1022, 16 1033 (N.D. Cal. 2019). Combined, these claims ask whether “(1) there exists a reasonable 17 expectation of privacy, and (2) the intrusion was highly offensive.” In re Facebook, Inc. Internet 18 Tracking Litigation, 956 F.3d 589, 601 (9th Cir. 2020) (hereinafter “Facebook Tracking”). 19 a. Reasonable expectation of privacy 20 Under both the intrusion upon seclusion and invasion of privacy claims, the question of 21 whether a reasonable expectation of privacy exists is an objective one. See Shulman v. Grp. W. 22 Prods., Inc., 18 Cal.4th 200, 232 (1998). Nonetheless, this objective test may permit examination 23 of “the surrounding circumstances” to ascertain whether a person had a reasonable expectation of 24 privacy. Opp at 13. “California law does not require Plaintiffs to prove subjective expectation.” 25 26 2 Left unsaid is that Google similarly cannot point to developed California mass torts case authority in the privacy context in which certification was denied. Absence of a case in a new area 27 of law is not surprising. 1 Opperman v. Path, 13-cv-00453-JST, 2016 WL 3844326 at *11 (N.D. Cal. July 15, 2016) 2 (discussing the elements of the intrusion upon seclusion tort); see also Hill v. Natl. Collegiate 3 Athletic Assn., 7 Cal.4th 1, (1994) (holding that, for the state constitutional privacy cause of 4 action, “a reasonable expectation of privacy is an objective entitlement founded on broadly based 5 and widely accepted community norms.” (internal quotations omitted)). Instead, the claim 6 requires: “(1) intrusion into a private place, conversation or matter, (2) in a manner highly 7 offensive to a reasonable person.” Opperman, 2016 WL 3844326 at *11 (quoting Shulman, 18 8 Cal.4th at 231) (emphasis in original). 9 Google invokes Hart v. TWC to argue that individual inquiries as to whether putative class 10 members had a reasonable expectation of privacy can defeat predominance. No. 20-cv-03842-JST, 11 2023 WL 3568078 (N.D. Cal. March 30, 2023). In that case, the plaintiffs averred that The 12 Weather Channel (“TWC”) violated the California Constitution when it tracked and collected users’ data and engaged in a scheme to sell that data to third parties and business partners without 13 users’ knowledge. Id. at *1. The court determined that ascertaining if users maintained a 14 reasonable expectation of privacy required “an individualized factual inquiry” into whether they 15 knew their affirmative responses to the permission prompts allowed TWC to engage in the averred 16 misconduct. Id. at *10. Furthermore, the Court held that analysis of an individual user’s “conduct” 17 could also defeat predominance by manifesting “voluntary consent.” Id. (citation omitted). 18 Here, those same considerations weigh in favor of predominance. First, the relevant 19 “conduct” showing a lack of consent is the users’ decisions affirmatively to switch off the WAA 20 and sWAA buttons. It is not, as Google tries to argue, the fact that users continued using apps with 21 Google’s SDKs. It is unreasonable for Google to expect, as it does, that users must also stop using 22 the many apps on their phone, after selecting sWAA to be off, to show a lack of consent. This 23 places an undue burden on everyday users who indicated their privacy preferences by turning off 24 sWAA. Second, Google’s argument places an impossible burden on Plaintiffs that would preclude 25 injunctive relief altogether: they must stop using the many apps on their phones to avoid 26 consenting to the wrongful conduct, unfairly undercutting standing to seek injunctive relief. See 27 1 infra at IV.A.II.c. Third, both the third party apps in this case and TWC in Hart provided its users 2 with privacy disclosures when the app was opened. Separately from these disclosures, putative 3 class members here affirmatively sought out and clicked on Google’s WAA and sWAA buttons, a 4 common act representing their privacy choices, based on Google’s own ubiquitous 5 representations. In Hart, TWC was both the app facing users and the defendant; user’s reasonable 6 expectations as to TWC’s conduct was the basis of the court’s decision there. By contrast, Google 7 is the party engaging in the alleged wrongful conduct separate from the third party apps making 8 disclosures to class members. Individual representations by the third party apps here do not 9 outweigh Google’s common representation to users for purposes of finding predominance. 10 Despite Google’s insistence otherwise, whether the amount or nature of data collected is a 11 fact-specific inquiry does not by itself defeat predominance, because the relevant question is 12 whether the members, who shared common conduct, had an objective, reasonable expectation of 13 privacy based on Google’s representation about the sWAA button to all members under these 14 claims. This is a question capable of resolution class-wide. 15 b. Highly offensive conduct 16 The second element of both claims, whether the intrusion was “highly offensive,” also 17 warrants class treatment. Google argues this is a complex question that “requires consideration of 18 all the circumstances of intrusion, including its degree and setting and the intruder’s motives and 19 objectives.” Opp. at 13 (quoting Shulman, 18 Cal.4th at 236). Again, Google fails to make a case 20 for why these additional questions supersede the central inquiry: whether a reasonable person 21 would find the intrusion by Google highly offensive. Instead, Google invokes two cases decided 22 under the California Invasion of Privacy Act (CIPA) section 632, which protects communications 23 made over a “wire, line, or cable,” to argue that both claims require a fact-specific inquiry 24 incapable of class-wide treatment. See Kight v. CashCall, Inc., 231 Cal. App. 4th 112 (2014); 25 Hataishi v. First Am. Home Buyers Prot. Corp., 223 Cal. App. 4th 1454 (2014). Both cases 26 Google identifies pertain to secretly overheard phone conversations that were listened to 27 surreptitiously. Plaintiffs’ CIPA section 632 claim, while previously dismissed, does not control 1 the analysis of the intrusion upon seclusion and invasion of privacy claims. 2 Factual inquiries underscoring a § 632 analysis are inapplicable here. There are no similar 3 individual issues about whether each plaintiff “reasonably believed their calls were not being 4 monitored.” Kight, 231 Cal. App. 4th at 119. Here, the relevant inquiries are primarily Google’s 5 uniform disclosures and users’ uniform conduct. Furthermore, CIPA § 632 is not, as Google 6 contends, an analog for the common law privacy tort. As stated above, the test under the state 7 intrusion upon seclusion and invasion of privacy claims is an objective one, capable of resolution 8 class-wide, and while analysis of surrounding circumstances may sometimes be necessary to 9 determine whether a user maintained their reasonable expectation of privacy, here, that question is 10 eclipsed by the undisputed fact that all class members switched off their sWAA settings. Cf. Hart 11 v. TWC, 2023 WL 3568078 at *9. 12 c. CDAFA 13 CDAFA makes certain computer-related crimes a public offense, including to “knowingly 14 access[] and without permission take . . . any data from a computer.” Cal. Penal Code § 502(c)(2). 15 Access “means to gain entry to, instruct, cause input to, cause output from, cause data processing 16 with, or communicate with, the logical, arithmetical, or memory function resources of a computer, 17 computer system, or computer network.” Cal. Penal Code 502(b)(1). Further, to show “damage or 18 loss” under CDAFA, a plaintiff need not have suffered a corresponding loss, as “California law 19 recognizes a right to disgorgement of profits resulting from unjust enrichment.” Facebook 20 Tracking, 956 F.3d at 599-600. 21 Google first argues, incorrectly, that CDAFA provides for “highly individualized . . . 22 compensatory damages” limited to the victim’s expenditure, i.e. what was “reasonably and 23 necessarily incurred by the owner or lessee to verify that a computer system, computer network, 24 computer program, or data was or was not altered, deleted, damaged, or destroyed by the access.” 25 Opp. at 15 (quoting Cal. Penal Code § 502(b)(11)). However, the statute provides for 26 compensatory damages including victim expenditures. Cal. Penal Code § 502(e)(1). 27 Next, Google asserts that it cannot be all class members who used apps with Firebase 1 and/or Google Mobile Ads SDKs suffered “damage or loss,” as their information was collected for 2 “run-of-the-mill record-keeping” and was not “sensitive, confidential, or even meaningful to 3 users.” Opp. at 16. Plaintiffs, on the other hand, argue that they need not prove the at-issue data 4 was sensitive or not-anonymous, but that “any damage or loss” is sufficient for standing under the 5 CDAFA3. Reply at 3; see Facebook Tracking, 956 F.3d at 599-600. Google’s definition is too 6 restrictive, while Plaintiff’s is too permissive. In order to maintain entitlement to the disgorged 7 profits, plaintiffs must show that they have standing, i.e. that they “retain a stake in the profits 8 garnered.” Facebook Tracking, 956 F.3d at 599-600. In that case, the Court held that Plaintiffs had 9 adequately established standing because they alleged their data “carr[ied] financial value” and that 10 the defendant “profited from this valuable data.” Plaintiffs’ damages expert provides two models 11 of unjust enrichment that account for both elements capable of application class-wide. However, 12 even if Google is right, and the “vast majority” of class members’ data was only exposed to 13 record-keeping “not tied to a person’s identity or used by Google for any purpose other than to 14 perform accounting for the apps that generated the data or advertising in the first place,” Opp. at 15 16, then surely that can be proven by common evidence of Google’s record-keeping practices. It is 16 unclear why Google would need to take discovery “from the 100 million privacy plaintiffs” if it 17 engaged in a uniform policy of record-keeping. 18 Google further insists predominance is not met because Plaintiffs “admitted they suffered 19 no harm.” Opp. at 17. Google points to concessions by the named plaintiffs of their continued use 20 of apps, Google accounts, and Google services, despite knowledge of the alleged privacy 21 violations. Google argues that this behavior “fatally undermined the claim of harm because each [named plaintiff] testified they had not changed their behavior [on their] phones after learning ‘the 22 truth’ about sWAA.” Opp. at 17. This argument places an undue burden on Plaintiffs. They need 23 24 25 3 Plaintiffs provide three ways damage or loss may be adjudicated class-wide: first, by proof of Google’s unjust enrichment class-wide; second, because Google failed to pay for collected data 26 despite there being a “market” for it, see Brown v. Google LLC, 2023 WL 5029899 at *19 (N.D. Cal. Aug. 7, 2023); and third, by showing how the data collection negatively impacts members’ 27 devices. See Class Cert. Mot. at 3. 1 not show they unilaterally stopped using Google’s services after learning about sWAA’s alleged 2 privacy violations to be able to aver they suffered harm. This would permit Google to argue that 3 Plaintiffs lack standing to aver the instant claims as they would face no real and immediate threat. 4 In In re Yahoo Mail Litig., 308 F.R.D. 577, 589 (N.D. Cal. 2015) (hereinafter, “Yahoo Mail Litig.”), the Court declined to place such an impossible burden on Plaintiffs seeking injunctive 5 relief. 6 7 Yahoo would put Plaintiffs in a catch–22 that would essentially preclude injunctive relief altogether. Yahoo would require Plaintiffs 8 to allege both (1) that Plaintiffs, in order to avoid “consenting” to Yahoo's conduct, stopped emailing Yahoo subscribers after 9 discovering Yahoo's alleged wrongful conduct, and (2) that Plaintiffs continued to email Yahoo subscribers so that Plaintiffs allege a real 10 and immediate threat of future injury, i.e., that Yahoo would intercept Plaintiffs' communications in the future. 11 Id. Aside from this unworkable predicament, the ubiquitous nature of phones, coupled 12 with the sheer number of apps with Google SDKs would render Plaintiffs’ use of their phones 13 impossible. The growing reliance on phones increasingly make them necessities, not luxuries, with 14 significant privacy implications for users. The fact that Plaintiffs, as putative class members, 15 affirmatively selected the WAA/sWAA-off buttons sheds light on their privacy choices as to 16 Google’s practices. Google may argue, as it does, that Plaintiffs have consented to the behavior 17 they complain about, but Plaintiffs’ continued use of Google’s products and services does not 18 equate to consent. See id. 19 d. Damages 20 Plaintiffs next argue that common questions predominate regarding damages. A showing 21 of predominance may fail if “questions of individual damage calculations will inevitably 22 overwhelm questions common to the class.” Comcast Corp. v. Behrend, 569 U.S. 27, 34 (2013). 23 Damage calculations need not be exact, but “at the class-certification stage (as at trial), any model 24 supporting a ‘plaintiff's damages case must be consistent with its liability case.’” Id. at 35 (citation 25 omitted). 26 The parties’ primary dispute as it relates to damages is whether they may be shown on a 27 class-wide basis, particularly with respect to Lasinski’s expert opinion (discussed infra Section B). 1 Plaintiffs provide four models for monetary relief: “disgorgement, actual damages, punitive 2 damages, and nominal damages.” Class Cert. Mot. at 19. Lasinski’s models on disgorgement and 3 actual damages are at issue in Google’s Daubert motion and are discussed below, so first 4 discussion turns to punitive and nominal damages. 5 Plaintiffs seek punitive damages for all three claims to “punish and deter” Google based on 6 its “conduct towards the class as a whole.” Class Cert. Mot. at 22 (citing Ellis v. Costco Corp. III, 7 285 F.R.D. 492, 542-44 (N.D. Cal. 2012)). Plaintiffs also seek nominal damages, relying on 8 Opperman, 2016 WL 3844326 at *15-16. Google argues that Plaintiffs “would need to have 9 shown that something about the data collection in question went beyond routine commercial 10 behavior . . . and crossed into highly-offensive-and-harmful territory.” Opp. at 19. At this juncture, 11 “it is sufficient to decide that the availability of punitive damages is amenable to classwide 12 resolution,” through common evidence. Opperman, 2016 WL 3844326 at *17. 13 e. Consent 14 While Plaintiffs bear the burden of proving predominance under 23(b)(3), Google bears the 15 burden of proof for the affirmative defense of consent. See True Health Chiropractic Inc. v 16 McKesson Corp., 896 F.3d 923, 931 (9th Cir. 2018); see also Brown v. Google LLC, No.: 4:20-cv- 17 3664-YGR, 2023 WL 5029899 *17-18 (N.D.Cal. Aug. 7, 2023). “When ‘one or more of the 18 central issues in the action are common to the class and can be said to predominate, the action may 19 be considered proper under Rule 23(b)(3) even though other important matters will have to be 20 tried separately, such as damages or some affirmative defenses peculiar to some individual class 21 members.’” Tyson Foods, Inc. v. Bouaphakeo, 577 U.S. 442, 453–54, (2016) (citation omitted). 22 i. sWAA disclosures 23 Google argues that even if harms and damages may be shown class-wide, its asserted 24 defenses of express and implied consent as to its own disclosures raise individual questions that 25 supersede common ones. First, Google suggests Plaintiffs theorize sWAA disclosures created 26 confusion for class members “as to types of data it covered and which aspects of Google’s 27 business would be disabled by turning sWAA off” as necessarily raising individualized questions. 1 Opp. at 20. Specifically, Google reasons that whether sWAA really was ambiguous to Plaintiffs 2 requires individualized evidence about a user’s “experience with Google, their exposure to third- 3 party app developers, and their own personal experiences with technology.” Opp. at 20. Plaintiffs 4 object to this characterization of their claim, arguing that express consent does not defeat 5 predominance because the “sWAA disclosures and Google’s Privacy Policy” are the only relevant 6 materials for analysis, and are “the same for all class members.” Reply at 10. 7 By way of example, Google invokes In re Google, Inc. Gmail Litigation, No. 13-MD- 8 02430-LHK, 2014 WL 1102660 (N.D. Cal. Mar. 18, 2014). In that case, the Court held that 9 predominance was defeated because plaintiffs could learn about Google’s disclosures from a 10 “panoply of sources” including Google’s own Terms of Service, privacy policies, news sources, with continued use of these various disclosures raising individual questions about implied consent. 11 Id. at *17. 12 Google’s position for purposes of this argument is a curious one. Throughout their 13 Opposition to Plaintiffs’ Motion, Google provides evidence that its disclosures to class members 14 were decidedly unambiguous. See, e.g., Opp. at 6-9 (describing Google’s Privacy Policy, and 15 various disclosures to users about what data is collected and/or saved). In fact, Google insists that 16 “for users who actually read the disclosures and engaged with the Ad Settings button, they would 17 have understood that turning off the personalization setting would not prevent Google from 18 serving ads, only make the ads less relevant” and, in order to disclose its notice and consent 19 procedures as clearly as possible, Google “disclos[es] information over time rather than all at 20 once.” Opp. at 9. Google bears the burden of proof of express consent, but the “non-speculative” 21 evidence it has provided leans against individualized treatment because Google itself vehemently 22 insists that its own disclosures are unambiguous. See Brown, 2023 WL 5029899 at *18. Google 23 cannot argue that its disclosures were unambiguous where it suits it, and ambiguous where it does 24 not. While it is possible that individual class members learned about the WAA feature from a 25 panoply of sources, it is left unexplained why that necessarily means Google’s explanations were 26 inconsistent, warranting defeat of predominance. Google’s representations about the WAA 27 1 feature, unambiguous and persistent by its own admission, outweigh these individual questions 2 about where class members learned about the WAA feature. 3 Google next argues that users impliedly consented because “most of the class was likely 4 well aware that sWAA would not serve as an ad blocker because they turned sWAA off and 5 Google kept serving them ads.” Opp. at 21 (emphasis in original). This argument supposedly 6 weighs against Plaintiffs’ position that the “sWAA button could never be unambiguous.” Id. 7 Plaintiffs argue that “Google cites no evidence users know a Google ad when they see one,” and, 8 regardless, “Google must prove class members consented to Google’s saving and use of sWAA-off 9 data, not Google advertising.” Reply at 14 (emphasis in original). Indeed, the relevant inquiry is 10 whether class members consented to the collection of sWAA-off data. Google has maintained that 11 the only data collected from sWAA-off users is required for their “record-keeping,” most of which 12 is related to tracking their ad services. Therefore, Google argues that it can raise a defense of 13 implied consent because users knew they were being served Google ads. Again, this defense may 14 be raised class-wide. Google’s ubiquitous representation to users is a common question, not an 15 individual one, particularly as Google insists that “every member of the class who was served an 16 ad by Google had the obvious and clear opportunity to understand that the ad was served by 17 Google.” Opp. at 21. If its behavior was consistent across the class, then it may raise its defense 18 class-wide, even if an additional concern may arise as to who actually clicked on the 19 representations. That individual question, balanced against the many common ones, does not 20 defeat predominance. In this respect, Google’s policy is uniform, and common questions 21 predominate. 22 While Google’s third argument breaks in the opposite direction, it is not enough to defeat a 23 finding of predominance. Google maintains that each class member had a way to prevent 24 conversion attribution at the device-level. For example, Google points to Apple iOS’s “opt-in” 25 policy starting in April 2021, called App Tracking Transparency, which requires users “to opt-in 26 to ad tracking affirmatively.” Opp. at 22. An analog for Android devices that allows users to opt- 27 out of ad-tracking is called “Opt out of Ad Personalization.” Id. Google insists that predominance 1 is defeated because some of the proposed class members will have consented by opting-in to ad 2 tracking affirmatively, and others will not. Plaintiffs insist that this technology is irrelevant to 3 sWAA-off data. While Google has sufficiently pointed to the challenge of raising this defense 4 class-wide, this issue still warrants class treatment because device-level settings presumably apply 5 uniformly across all iOS devices or all Android devices. Further, summary adjudication, not class 6 certification, is the appropriate vehicle by which to resolve how device-level settings may interact 7 with sWAA. 8 Google’s last argument focuses on users who had accounts prior to 2016. It asserts that, 9 prior to that date, sWAA was “off by default” for accounts. It insists that the challenge will be in 10 separating which members did not change their settings by default and which did not do so by 11 choice, raising individualized inquiries. Plaintiffs rely on two expert opinions to refute Google’s 12 contention. Plaintiffs point out that pre-2016 users received a “consent bump” prompt, by “which 13 Google urged them to turn sWAA on.” Reply at 14-15. This conduct matches the conduct post- 14 2016, as all users collectively switched sWAA off. In other words, the users who did not turn 15 sWAA on effectively refused data collection by Google. While Google points out that it may have 16 to raise different defenses with respect to the pre-2016 users, these defenses need not be 17 individualized and may apply as a whole to pre-2016 users and post-2016 users, such that the issue 18 may be resolved through sub-classing if necessary. See Tyson Foods, Inc., 577 U.S. at 453–54. 19 ii. Third-party disclosures 20 Google argues that that each class members “was subjected to dozens, perhaps hundreds, 21 of disclosures from apps informing them that their activity data on third party apps was being 22 collected.” Opp. at 23. Google suggests that, as a result, a factfinder will have to sift through “each 23 innumerable permutations of apps the user has downloaded” to conduct a consent inquiry. 24 However, the relevant question concerns Google’s disclosures about the sWAA button, not third- 25 party disclosures to users. To the extent Google had a policy that required third party apps to 26 disclose Google’s policies to users, that evidence may be applied across the class. Google is 27 correct that a factfinder may have to analyze an app’s specific disclosures to evaluate consent but 1 that individual inquiry, if applicable, does not overwhelm predominating questions as to Google’s 2 privacy disclosures. 3 The predominance inquiry of 23(b)(3) is therefore satisfied. Additionally, class treatment 4 of this case is the “superior” method of adjudication because each class member would not have to 5 “litigate numerous and substantial issues to establish his or her right to recover individually.” 6 Zinser, 253 F.3d at 1192. For these reasons, the motion to certify a damages class under 23(b)(3) 7 is granted. 8 III. 23(b)(2) 9 Plaintiffs also seek certification under 23(b)(2) for injunctive relief from Google’s alleged 10 misconduct class-wide. “Rule 23(b)(2) applies only when a single injunction or declaratory 11 judgment would provide relief to each member of the class.” Dukes, 564 U.S. at 360. Unlike 12 23(b)(3), the relevant inquiry here is not whether common questions predominate in the individual 13 claims of proposed class members, “but rather whether [the defendant] has engaged in a “common 14 policy’” with respect to the class. Yahoo Mail Litig., 308 F.R.D. at 599. 15 Plaintiffs seek injunctive relief: 16 (1) precluding Google from further collecting, storing, and using consumers’ (s)WAA-off app activity data; (2) requiring Google to 17 delete already collected (s)WAA-off app activity data; (3) requiring Google to delete any products, services, or algorithms built in whole 18 or in part with that unlawfully collected (s)WAA-off app activity data; and (4) appointing an independent third party to verify that the 19 injunctive relief has been (and continues to be) implemented. 20 Class Cert. Mot. at 25. Google argues that none of these requests address any “common 21 policy” by Google. Plaintiffs’ second request would, according to Google, require it to identify 22 each class member and contravene its own policy “against joining pseudonymous data with user 23 accounts” to delete this data. Opp. at 25. This argument is unavailing. Plaintiffs seek deletion of 24 all sWAA-off data collected. Indeed, if Google were conducting “basic record-keeping” of its 25 users’ data, then it should know which of its users toggled sWAA off and which did not – a 26 27 1 feature by Google and, therefore, under its control.4 Plaintiffs contend that Google should delete 2 sWAA-off data Google itself admits to collecting, albeit only for record-keeping purposes. 3 Further, Google fails to raise any arguments against three out of four Plaintiffs’ requests, and 4 Plaintiffs have convincingly identified “the general contours” of the class-wide injunctive relief 5 they seek. Parsons v. Ryan, 754 F.3d 657, 689-90 fn. 35 (9th Cir. 2014). Google may raise these 6 arguments again at summary judgment should it wish to do so, but at this stage, Plaintiffs have 7 met their burden. Class certification is granted under 23(b)(2). 8 B. Daubert Motion as to Michael J. Lasinski 9 Google moves to exclude the opinion of Michael J. Lasinski, Plaintiff’s damages expert, 10 relying on Fed. R. Evid. 702 and Daubert. Dkt. at 330. Lasinski opines that discovery can be used 11 to establish monetary relief sought by Plaintiffs class-wide. Lasinski Rep. 1. As discussed above, 12 Lasinski provided two sub-models under Plaintiffs’ unjust enrichment theory (Scenarios One and 13 Two) and one model for actual damages. Lasinski’s unjust enrichment analyses “quantify the 14 portion of Google’s U.S. App Promo, AdMob, and Ad Manager app ads revenues and attendant 15 profits attributable to the alleged wrongful conduct” under two scenarios, discussed further below. 16 Lasinski Rep. ¶ 77. For much of his analysis, Lasinski relies on the opinions of Jonathan 17 Hochman, Plaintiffs’ technical expert, and Mark Keegan, Plaintiffs’ survey expert. 18 I. Unjust Enrichment 19 Under Scenario One, Lasinski calculates Google’s unjust enrichment as equal to “(a) 20 Google’s U.S. App Promo revenues and attendant profits from signed-in, WAA/sWAA-Off users 21 attributable to conversion tracking with GA4F plus [(b)] the portion of Google’s U.S. AdMob and 22 [(c)] Ad Manager app ads revenues and attendant profits from signed-in, WAA/sWAA-Off users 23 attributable to conversion tracking.” Id. ¶ 82-91 (describing methods of calculating the proportion 24 25 4 Google states that it conducts “basic record-keeping” of its users’ data because, even when a 26 user’s sWAA is turned off, it will “(1) log the fact that it has served an ad alongside a pseudonymous device identifier for accounting purposes, and (2) attribute conversion events to 27 those ad serving records.” Opp at 5. 1 of Google’s U.S. App Promo net revenue from signed-in, WAA/sWAA-off users attributable to 2 conversion tracking). Per Scenario 1, damages equate to $558.8 million. 3 In Scenario Two, Lasinski calculates (a) “the revenues and attendant profits attributable to 4 conversion tracking quantified under Scenario One plus [(b)] an additional measure of AdMob and 5 Ad Manager app ads revenues and attendant profits attributable to the serving and monetization of 6 ads to WAA/sWAA-Off users.” Id. ¶ 113. The additional measure here adds the value to Google 7 derived from served ads from methods other than conversions. Scenario Two calculates damages 8 totaling $664.3 million. 9 II. Actual damages 10 To generate a model for his actual damages calculation, Lasinski considered: (a) Google’s 11 payments for user data, (b) Users’ willingness to pay to prevent data collection; and (c) Research 12 organizations’ willingness to pay for data collection.” Id. ¶ 132. 13 Lasinski looked to the Ipsos Screenwise Panel, a consumer research study conducted by 14 Google since 2012 to “collect information about how users browse the internet.” Id. ¶ 135. 15 Lasinski states that the panel participants knowingly allow Google to track their activity, thus 16 “relinquish any sense of online data privacy.” Id. ¶ 139. The minimum recurring payment for a 17 participant is $3 a month. To arrive at an actual damages calculation, Lasinski applied the $3 value 18 once to each of the class member devices (i.e. a device where WAA/sWAA was turned off from 19 July 1, 2016 to December 2022). Lasinski calculates actual damages to equal approximately 20 $486.05 million. 21 III. Recoverable damages 22 To support its Daubert motion, Google asserts that (a) Plaintiffs cannot recover 23 disgorgement on their claims, (b) the disgorgement model provides for a “full restitution model” 24 based on unrealistic “hypothetical damages scenario” or fictitious facts, (c) the actual damages 25 model has no methodology and is therefore unreliable because it is cribbed from another case, (d) 26 the models used by Lasinski are “outcome determinative” and “cherry-picked” so should be 27 rejected, and (e) the actual damages model does not account for variances among class members. 1 a. Availability of disgorgement as a remedy 2 Google argues that Plaintiffs did not suffer any actual loss, as Google never invaded any 3 property right, so disgorgement is not available to Plaintiffs as a remedy. As already discussed 4 above in the analysis for 23(b)(3), Google is incorrect at least with respect to the CDAFA claim. 5 See Facebook Tracking, 956 F.3d at 600; see also Brown v. Google LLC, 2023 WL 5029899 at 6 *6-7 (N.D. Cal. Aug. 7, 2023). 7 With respect to the intrusion upon seclusion and invasion of privacy claims, Google argues 8 that disgorgement is unavailable to Plaintiffs because “the primary damage . . . is the mental 9 distress from having been exposed to public view.” Time, Inc. v. Hill, 385 U.S. 374 384 n.9 (1967) 10 (as quoted in CACI 1820 (2023)). However, that argument misses the mark. The Ninth Circuit has 11 not limited disgorgement to CDAFA claims. The relevant inquiry under California law is whether 12 there is “an entitlement to unjustly earned profits” and, “to establish standing, plaintiffs must only 13 establish a stake in the profits garnered from their personal data and that it is unjust for the 14 defendant to retain those profits.” Greenley v. Kochava, Inc., No. 22-cv-01327-BAS-AHG, 2023 15 WL 4833466 at *4 (S.D. Cal. July 27, 2023) (citation omitted). Plaintiffs, through Lasinski’s 16 opinion, have met this burden for Daubert purposes. Further, Plaintiffs must show that the 17 damages model is “consistent with its theory of liability in the case.” Brown, 2023 WL 5029899 at 18 *6 (quoting Comcast, 569 U.S. at 35). Here, Plaintiffs’ theory is consistent to the extent that they 19 contend Google was unjustly enriched by collection of their data. Lasinski’s theory attributes 20 damages to the wrongful conduct. 21 b. Lasinski’s model is not based on fictitious scenarios 22 Google next argues that Lasinski’s model for unjust enrichment suffers causation 23 deficiencies because he assumes that all of Google’s revenue from ads served to sWAA-off users 24 was attributed to Google’s capacity to keep a record the ad was served. Google objects to 25 Lasinski’s methods, which according to Google “presume 100% forfeiture” because Lasinski does not consider “(1) user reactions if Google had provided users with the disclosures Plaintiffs allege 26 it should have provided; or (2) changes in behavior by Google or advertisers if Google could no 27 1 longer use the record-keeping data.” Daubert Mot. at 10-11. Google argues this analysis is 2 “critical” because, if class members would not change their behavior based on Google’s 3 disclosures, or if advertisers would have placed just as many ads with Google in the absence of 4 sWAA-off data, then Google could not have been unjustly enriched. However, Lasinski was not required to examine whether Google could have profited otherwise before reaching a conclusion 5 that Google was not unjustly enriched. Furthermore, Google bears the burden of quantifying 6 recouped profits. 7 Google relies on Hart to argue that Lasinski’s methods suffer an attribution problem. In 8 that case, the plaintiffs calculated gross revenue minus costs equal unjustly retained benefit. By 9 contrast, Lasinski further apportioned his calculations by how many class devices had their 10 WAA/sWAA off, a value provided to Lasinski by Google. Lasinski’s models do not speculate on 11 hypothetical scenarios, but Google’s own practices. 12 c. The actual damages model is not unreliable for being used in a different case 13 Google argues that Lasinski’s actual damages model should be excluded because it is 14 “cribbed” from another case. However, that by itself should not preclude Lasinski’s actual 15 damages model. See Brown, 2023 WL 5029899 at *6 (discussing a similar damages calculation 16 but for restitutionary damages). As it did in that case, Google tries to argue that Lasinski does not 17 rationalize “pegging actual damages to a one-time $3 payment per device.” Daubert Mot. at 18. 18 However, as the court in Brown already noted, “The $3 rate is derived from looking at what 19 Google actually pays Screenwise participants for agreeing to allow Google to collect their 20 browsing data.” Id. (emphasis added). The simple fact that this model was utilized in another case 21 averring Google mishandled private data does not warrant exclusion. 22 d. Lasinski’s models are not “cherry-picked” 23 Google argues Lasinski’s damages model “cherry-picked” his actual damages model from 24 “a single survey.” Daubert Mot. at 19. Google insists that because Lasinski could not explain why 25 $4 or $2, or any other figure, would also be appropriate, the $3 is a cherry-picked figure. It also 26 argues that because Lasinski referred to the $3 valuation as “conservative” in his deposition, this 27 must also mean that it is inaccurate. However, Google incorrectly characterizes the actual damages 1 calculation as being randomly picked from a single survey. In fact, Lasinski provided analysis and 2 compared market studies to explain why he settled on the Screenwise panel and the $3 figure. He 3 provided insight as to why the payments made by Google to the Screenwise participants offers a 4 strong basis for an actual damages model. Lasinski explored other programs that pay users for their data, and ultimately generated a model based on an actual, baseline payment made by 5 Google to track actual consumer data. 6 e. Actual damages need not account for variances as they are based on the market value 7 Google’s final argument is that Lasinski’s actual damages model does not account for 8 variances among class members and risks grossly undercompensating and overcompensating 9 others. Google makes three arguments to this end: first, that some users are willing to let analytics 10 providers access their data for free. Second, Lasinski overlooks the “diversity of user attitudes” 11 related to privacy. Third, Lasinski never showed actual economic injury to the class. However, as 12 Brown points out, where there is unjust enrichment, “restitution can be measured by either: (a) the 13 value of benefit to the defendant; (b) the cost to plaintiff of conferring such benefit; (c) the market 14 value of the benefit; or (d) the price the defendant has expressed a willingness to pay, if the 15 defendant's asset may be treated valid on the question of price.” 2023 WL 5029899 at *7 (quoting 16 Rest. 3d of Restitution and Unjust Enrichment § 49). In that case as here, Lasinski appropriately 17 built his model around the price Google was willing to pay for users’ privacy and this “objective 18 standard” warrants denial of Google’s motion. To the extent that users have mixed attitudes 19 related to privacy – all class members shared at least one uniform attitude related to privacy, 20 evidenced by their uniform conduct of switching WAA/sWAA off. Therefore, as to the uniform 21 conduct of the class, the actual damages model does, in fact, account for class-wide attitudes and 22 Google’s class-wide alleged wrongdoing. 23 V. CONCLUSION 24 For the reasons discussed above, Plaintiffs’ motion to grant class certification is granted, 25 and Google’s motion to exclude the opinion of Plaintiffs’ damages expert is denied. The following 26 classes are certified: 27 Class 1: All individuals who, during the period beginning July 1, 2016 1 and continuing through the present (the “Class Period”), (a) had their “Web & App Activity” and/or “supplemental Web & App Activity” 2 setting turned off and (b) whose activity on a non-Google-branded mobile app was still transmitted to Google, from (c) a mobile device 3 running the Android operating system, because of the Firebase 4 Software Development Kit (“SDK”) and/or Google Mobile Ads SDK. Class 2: All individuals who, during the Class Period (a) had their 5 “Web & App Activity” and/or “supplemental Web & App Activity” setting turned off and (b) whose activity on a non-Google-branded 6 mobile app was still transmitted to Google, from (c) a mobile device running a non-Android operating system, because of the Firebase 7 SDK and/or Google Mobile Ads SDK. 8 The parties will appear for a Case Management Conference on February 1, 2024 and 9 submit a Joint Case Management Statement by January 25, 2024. 10 11 || ITISSO ORDERED. 12 13 |] Dated: January 3, 2024 MAA RICHARD SEEBORG IS Chief United States District Judge 16 = 17 Z 18 19 20 21 22 23 24 25 26 27 98 ORDER GRANTING MOTION FOR CLASS CERTIFICATION AND DENYING DAUBERT MOTION CASE No. 20-cv-04688-RS