throbber
Case 3:21-cv-09004-CRB Document 64 Filed 12/01/22 Page 1 of 25
`
`
`
`
`
`
`
`
`
`IN THE UNITED STATES DISTRICT COURT
`
`FOR THE NORTHERN DISTRICT OF CALIFORNIA
`
`
`
`
`
`MARIE HAMMERLING, et al.,
`
`Plaintiffs,
`
`v.
`
`GOOGLE LLC,
`
`
`
`
`
`Defendant.
`
`Case No. 21-cv-09004-CRB
`
`
`ORDER GRANTING MOTION TO
`DISMISS
`
`Defendant Google LLC (“Google”) moves to dismiss Plaintiffs Marie Hammerling
`
`and Kay Jackson’s amended complaint. For the second time, Plaintiffs allege that Google
`
`secretly used their Android smartphones to collect data regarding their use of third-party
`
`apps. Plaintiffs allege that, through the collection of this data, Google “gains a wealth of
`
`highly personal information about consumers” in order to “gain an unfair advantage
`
`against its competitors.” Am. Compl. (dkt. 51) ¶¶ 3, 5. In its prior order, the Court
`
`dismissed all of Plaintiffs’ claims against Google. See Hammerling v. Google LLC, No.
`
`21-CV-09004-CRB, 2022 WL 2812188 (N.D. Cal. July 18, 2022). Plaintiffs renew those
`
`claims in their amended complaint, alleging that Google breached its contract with its
`
`customers and violated California’s Unfair Competition Law, the California Constitution,
`
`and California fraud and privacy laws. Am. Compl. ¶¶ 119–222. Google again moves to
`
`dismiss. Mot. (dkt. 57). Finding this matter suitable for resolution without oral argument
`
`pursuant to Civil Local Rule 7-1(b), because Plaintiffs fail to cure the deficiencies outlined
`
`in the Court’s prior order, the Court GRANTS Google’s motion to dismiss.
`
`I.
`
`BACKGROUND
`
`In its prior order, the Court found that Plaintiffs had failed to state each of its ten
`
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`Northern District of California
`
`United States District Court
`
`

`

`Case 3:21-cv-09004-CRB Document 64 Filed 12/01/22 Page 2 of 25
`
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`claims: (1) common law intrusion upon seclusion; (2) invasion of privacy under the
`
`California Constitution; (3) violation of California Civil Code section 1709; (4) violations
`
`of the fraud, unlawful, and unfair prongs of California Civil Code section 17200 (“Unfair
`
`Competition Law” or “UCL”); (5) violation of California Civil Code section 1750
`
`(“California Consumers Legal Remedies Act” or “CLRA”); (6) breach of contract; (7)
`
`breach of implied contract; (8) unjust enrichment; (9) relief under the Declaratory
`
`Judgment Act; and (10) violation of California Penal Code section 631 (“California’s
`
`Invasion of Privacy Act” or “CIPA”). See Hammerling, 2022 WL 2812188. Despite
`
`noting that “many of the problems [outlined in the order would] be difficult to cure,” the
`
`Court granted Plaintiffs leave to amend. Id. at *18. Plaintiffs amended their complaint,
`
`leaving the vast majority of their allegations untouched; those facts are discussed in the
`
`Court’s prior order. See Hammerling, 2022 WL 2812188, at *1–2. In their amended
`
`complaint, Plaintiffs allege the following additional facts:
`
`First, Plaintiffs allege that data about their use of third-party apps provided “unique
`
`insights” into their lives; for example, through Hammerling’s use of the Fidelity
`
`Investments and Bank of America apps, Google knew where Hammerling “maintained her
`
`financial accounts.” Am. Compl. ¶ 18. Through other third-party apps downloaded to her
`
`Android smartphone, Google could deduce that Hammerling had a home security system,
`
`drove a Mazda, read the New York Times, and was physically active. Id. Similarly,
`
`through Jackson’s use of the Joel Osteen, YouVersion Bible, and Bible Trivia apps,
`
`Google knew Jackson’s religious beliefs. Id. ¶ 30.
`
`Second, Plaintiffs highlight five pieces of specific information collected from
`
`Hammerling’s use of third-party apps: (1) she visited the Wish app on March 10, 2021 and
`
`viewed a foot massager, and on March 3, 2021 and viewed “womens slippers size 9”; (3)
`
`she visited the Groupon app and viewed deals for “78% off Anti-inflammatory Meal
`
`subscriptions” on October 13, 2019 and “100% Extra Virgin Coconut Oil” on May 10,
`
`2020; and (3) she visited the Picsart Photo & Video Editor app on March 8, 2021. Id. ¶¶
`
`19–21. For two of these pieces of data, Plaintiffs included data notices from
`
`2
`
`Northern District of California
`
`United States District Court
`
`

`

`Case 3:21-cv-09004-CRB Document 64 Filed 12/01/22 Page 3 of 25
`
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`Hammerling’s Google account, which state that: “This activity was saved to your Google
`
`Account because the following settings were on: additional Web & App Activity. You can
`
`control these settings here.” Id. ¶¶ 19, 21. When Plaintiffs followed the link in that notice,
`
`they allege that the Web & App Activity Activity Control only states that Google will
`
`“Save[] your activity on Google sites and apps” and Google’s collection of Hammerling’s
`
`third-party app data from Groupon, Wish, and Picsart was in violation of this
`
`representation. Id. ¶ 23.1
`
`Third, Plaintiffs allege that Hammerling read Google’s Privacy Policy and that she
`
`“did not understand this policy to mean (and did not agree) that Google would collect
`
`sensitive data from” third-party apps she downloaded to her Android smartphone. Id. ¶ 25.
`
`Plaintiffs do not allege that Jackson ever read the Policy.
`
`Fourth and finally, Plaintiffs allege that this information was “not de-identified or
`
`anonymized,” but that their interactions with third-party apps are “directly associated with
`
`[their] Google Account[s].” See, e.g., id. ¶¶ 31, 65.
`
`II.
`
`LEGAL STANDARD
`
`Under Federal Rule of Civil Procedure 12(b)(6), the Court may dismiss a complaint
`
`for failure to state a claim upon which relief may be granted. Dismissal may be based on
`
`either “the lack of a cognizable legal theory or the absence of sufficient facts alleged under
`
`a cognizable legal theory.” Godecke v. Kinetic Concepts, Inc., 937 F.3d 1201, 1208 (9th
`
`Cir. 2019) (cleaned up). A complaint must plead “sufficient factual matter, accepted as
`
`true, to state a claim to relief that is plausible on its face.” Ashcroft v. Iqbal, 556 U.S. 662,
`
`678 (2009) (cleaned up). A claim is plausible “when the plaintiff pleads factual content
`
`that allows the court to draw the reasonable inference that the defendant is liable for the
`
`misconduct alleged.” Id. When evaluating a motion to dismiss, the Court “must presume
`
`all factual allegations of the complaint to be true and draw all reasonable inferences in
`
`
`1 While Plaintiffs do not allege that any specific data of this kind was collected from Jackson, they
`do allege that Google generally collected “highly specific data relating to” Jackson and that it also
`violated affirmative representations regarding WAA as applied to her. Id. ¶¶ 31–32, 34.
`3
`
`Northern District of California
`
`United States District Court
`
`

`

`Case 3:21-cv-09004-CRB Document 64 Filed 12/01/22 Page 4 of 25
`
`
`
`favor of the nonmoving party.” Usher v. City of Los Angeles, 828 F.2d 556, 561 (9th Cir.
`
`1987). “Courts must consider the complaint in its entirety, as well as other sources courts
`
`ordinarily examine when ruling on Rule 12(b)(6) motions to dismiss, in particular,
`
`documents incorporated into the complaint by reference, and matters of which a court may
`
`take judicial notice.” Tellabs, Inc. v. Makor Issues & Rights, Ltd., 551 U.S. 308, 322
`
`(2007).
`
`Claims for fraud must meet the pleading standard of Federal Rule of Civil
`
`Procedure 9(b), which requires a party “alleging fraud or mistake [to] state with
`
`particularity the circumstances constituting fraud or mistake.” Rule 9(b) “requires . . . an
`
`account of the time, place, and specific content of the false representations as well as the
`
`identities of the parties to the misrepresentations.” Swartz v. KPMG LLP, 476 F.3d 756,
`
`764 (9th Cir. 2007) (cleaned up). “This means that averments of fraud must be
`
`accompanied by the who, what, when, where, and how of the misconduct charged.” In re
`
`Google Assistant Priv. Litig., 546 F. Supp. 3d 945, 955 (N.D. Cal. 2021) (internal
`
`quotation marks omitted).
`
`If a court dismisses a complaint for failure to state a claim, it should “freely give
`
`leave” to amend “when justice so requires.” Fed. R. Civ. P. 15(a)(2). A court has
`
`discretion to deny leave to amend due to “undue delay, bad faith or dilatory motive on the
`
`part of the movant, repeated failure to cure deficiencies by amendment previously allowed,
`
`undue prejudice to the opposing party by virtue of allowance of the amendment, [and]
`
`futility of amendment.” Leadsinger, Inc. v. BMG Music Pub., 512 F.3d 522, 532 (9th Cir.
`
`2008).
`
`III. DISCUSSION
`
`This order first considers Google’s request for incorporation by reference and
`
`judicial notice. See Request for Judicial Notice (“RJN”) (dkt. 58). It next considers
`
`Google’s argument that Plaintiffs consented to the data collection they allege in their
`
`amended complaint. See Mot. at 5–8. It then addresses Google’s motion to dismiss in the
`
`following order: (1) fraud claims (Section 1709, UCL’s fraud prong, and CLRA); (2)
`
`4
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`Northern District of California
`
`United States District Court
`
`

`

`Case 3:21-cv-09004-CRB Document 64 Filed 12/01/22 Page 5 of 25
`
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`privacy claims (common law intrusion upon seclusion, invasion of privacy under the
`
`California Constitution, and CIPA); (3) contract claims (breach of contract, implied
`
`contract, and unjust enrichment); (4) UCL’s unlawful and unfair prongs; and (5)
`
`declaratory judgment claim.
`
`A.
`
`Incorporation by Reference (Exs. A–E, G–I)
`
`Google seeks incorporation by reference of eight documents: two versions of its
`
`Privacy Policy, RJN Exs. A & B; and the website and Android versions of its “Activity
`
`Controls,” RJN Exs. C–E; G–I. See RJN at 3. Plaintiffs do not oppose this request. See
`
`RJN Opp’n (dkt. 59).
`
`The incorporation-by-reference doctrine “treats certain documents as though they
`
`are part of the complaint itself.” Khoja v. Orexigen Therapeutics, Inc., 899 F.3d 988, 1002
`
`(9th Cir. 2018). Documents are subject to incorporation by reference if a plaintiff refers to
`
`them “extensively” or they form the basis of the complaint. Id. Courts may properly
`
`assume the truth of documents incorporated by reference. Id. at 1003. But “it is improper
`
`to assume the truth of an incorporated document if such assumptions only serve to dispute
`
`facts stated in a well-pleaded complaint.” Id.
`
`The Court’s prior order on Google’s first motion to dismiss found that both versions
`
`of Google’s Privacy Policy were incorporated by reference. They remain so for the same
`
`reasons, based on Plaintiffs’ many references to them in their amended complaint. See
`
`Hammerling, 2022 WL 2812188, at *3; see also, e.g., Am. Compl. ¶¶ 24, 33, 62–63, 73–
`
`74.
`
`The amended complaint, additionally, both quotes directly and references Google’s
`
`“Activity Controls,” or webpages through which Plaintiffs were able to choose what types
`
`of their data Google may retain. RJN Exs. C–E; G–I. Plaintiffs provide two notices from
`
`Hammerling’s Google account, both of which state that: “This activity was saved to your
`
`Google Account because the following settings were on: additional Web & App Activity.
`
`You can control these settings here.” Am. Compl. ¶¶ 19 fig. 1, 21 fig. 2. Plaintiffs then
`
`provide direct quotes from the page linked in both notices, but do not provide the full
`
`5
`
`Northern District of California
`
`United States District Court
`
`

`

`Case 3:21-cv-09004-CRB Document 64 Filed 12/01/22 Page 6 of 25
`
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`linked page. Id. ¶¶ 23, 32, 183. Google provides those linked pages (one before the Web
`
`& App Activity setting is enabled, the other after) as Exhibits C & D in its request for
`
`judicial notice. See Kanig Decl. (dkt. 58-1) at 1; RJN Ex. C; Ex. D (“WAA Disclosure”).
`
`Further, Google provides an additional disclosure that pops up when a user chooses to
`
`enable the “[i]nclude Chrome history and activity from sites, apps, and devices that use
`
`Google services” option on the Web & App Activity (“WAA”) page, which Google calls
`
`the “Additional Web & App Activity” (“AWAA”) disclosure. See Kanig Decl. at 1; RJN
`
`Ex. E (“AWAA Disclosure”). Exhibits G, H and I are those same pages, as they appear on
`
`Android smartphones. Kanig Decl. at 2; RJN Exs. G–I. Plaintiffs do not dispute the
`
`authenticity of these webpages, nor that they are provided when Android users alter their
`
`WAA settings, as Google explains in its declaration. See RJN Opp’n.
`
`The Court finds that each of these webpages are properly incorporated by reference.
`
`The Amended Complaint both references and quotes directly (though selectively) from the
`
`WAA Disclosure, which, in turn, when a particular setting is selected, allows the AWAA
`
`Disclosure to pop up. See Am. Compl. ¶¶ 23, 32; WAA Disclosure; AWAA Disclosure.
`
`These documents are thus part of a singular whole and must be considered together,
`
`particularly where Plaintiffs complain that they were not adequately informed about the
`
`types of data Google collects from their Android smartphones. Khoja, 899 F.3d at 1002;
`
`Al-Ahmed v. Twitter, Inc., No. 21-CV-08017-EMC, 2022 WL 1605673, at *4 (N.D. Cal.
`
`May 20, 2022); see also, e.g., Am. Compl. ¶¶ 19, 21, 23, 32, 34. Thus, the Court
`
`incorporates by reference Exhibits A–E and G–I to Google’s request for judicial notice.
`
`B.
`
`Judicial Notice (Exs. F, J, K)
`
`Google additionally seeks judicial notice of three documents: a page from its Help
`
`Center titled “Find & control your Web & App Activity”, see RJN Ex. F; a Privacy Policy
`
`dated September 20, 2021 from the third-party app Wish, see RJN Ex. J; and an undated
`
`disclosure from the Google Play Store regarding data collection by the third-party app
`
`Groupon, see RJN Ex. K. Plaintiffs do not oppose the request as to the Help Center
`
`webpage, but they do oppose the request as to the Wish Privacy Policy and Groupon
`
`6
`
`Northern District of California
`
`United States District Court
`
`

`

`Case 3:21-cv-09004-CRB Document 64 Filed 12/01/22 Page 7 of 25
`
`
`
`disclosure. RJN Opp’n at 3.
`
`Courts may take judicial notice of a fact that is “not subject to reasonable dispute,”
`
`i.e., that is “generally known” or “can be accurately and readily determined from sources
`
`whose accuracy cannot reasonably be questioned.” Fed. R. Evid. 201(b). “Publicly
`
`accessible websites and news articles are among the proper subjects of judicial notice.”
`
`Diaz v. Intuit, Inc., 15-cv-1778, 2018 WL 2215790, at *3 (N.D. Cal. May 15, 2018).
`
`Courts may not, however, “take judicial notice of disputed facts contained in [] public
`
`records.” Khoja, 899 F.3d at 999 (citation omitted).
`
`Because Plaintiffs do not dispute the accuracy of the contents of the Help Center
`
`webpage, and because webpages like this one are regularly the subject of judicial notice in
`
`this circuit, the Court takes judicial notice of Exhibit F. See, e.g., Brown v. Google LLC,
`
`No. 20-CV-03664-LHK, 2021 WL 6064009, at *6–7 (N.D. Cal. Dec. 22, 2021).
`
`Plaintiffs do, however, argue that it is improper to take judicial notice of the Wish
`
`Privacy Policy and the Groupon disclosure, because they “have nothing to do with
`
`Plaintiffs’ allegations, which concern only Google’s collection and interception of data
`
`from non-Google apps through Android OS,” and that “Google takes no steps to explain
`
`how or if Plaintiffs would have seen these documents in the course of purchasing and
`
`using their Android devices.” RJN Opp’n at 1 (emphasis omitted).
`
`The Court disagrees with Plaintiffs’ contention that such disclosures “have nothing
`
`to do with [their] allegations,” but declines to take judicial notice of them nonetheless.
`
`While it may be true that these are the most recent privacy policy and data disclosure for
`
`Wish and Groupon respectively, they may not contain the same disclosures that
`
`Hammerling may have read when she downloaded the apps or used them from 2019 to
`
`2021.2 They thus contain no facts that can be “judicially noticeable for [their] truth.”
`
`Khoja, 899 F.3d at 999. Whether and to what extent Wish and Groupon alerted
`
`Hammerling that her data might be shared, and whether or to what extent they proceeded
`
`
`2 The Court takes no position on whether Hammerling had the opportunity to review a privacy
`policy or data disclosure when she downloaded the Wish or Groupon apps and began using them.
`7
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`Northern District of California
`
`United States District Court
`
`

`

`Case 3:21-cv-09004-CRB Document 64 Filed 12/01/22 Page 8 of 25
`
`
`
`to share her data with third parties (perhaps Google), are questions of fact unresolved by
`
`these disclosures and inappropriate to resolve on a motion to dismiss.
`
`Thus, the Court takes judicial notice of Exhibit F but declines Google’s request to
`
`take judicial notice of Exhibits J and K.
`
`C.
`
`Consent
`
`Google argues that, by including five allegations of data collection from
`
`Hammerling’s Google account in the amended complaint, Hammerling admits to
`
`consenting to the data collection practices at issue. Because Google fails to satisfy the
`
`high bar for consent on a motion to dismiss, this argument fails.
`
`In their amended complaint, Plaintiffs allege that Google tracked Hammerling’s
`
`interaction with three third-party apps, including what product or service she viewed, the
`
`date and time at which she viewed it, and the Google product she used at the time. See
`
`Am. Compl. ¶¶ 19–21. Plaintiffs provide a notice from Google about the source of two
`
`pieces of that data. Under a “Why is this here?” heading, the notice states: “This activity
`
`was saved to your Google Account because the following settings were on: additional Web
`
`& App Activity. You can control these settings here.” Id. ¶¶ 19 fig. 1, 21 fig. 2. Plaintiffs
`
`claim that when they follow the link in those notices, Google states that if Web & App
`
`Activity is enabled on that page, it will only “Save[] your activity on Google sites and
`
`apps.” Id. ¶ 23. However, Google contends that Plaintiffs selectively quote from the Web
`
`& App Activity page. See, e.g., Mot. at 6. Google provides the full Web & App Activity
`
`disclosure, which also provides an additional choice for users to select: “Include Chrome
`
`history and activity from the sites, apps, and devices that use Google services.” WAA
`
`Disclosure; see also Ex. H (same). When users choose this setting, an additional
`
`disclosure pops up, clarifying the “activity from sites, apps, and devices that use Google
`
`services” that users may allow Google to collect, including: “app activity, including data
`
`that apps share with Google”; and “Android usage and diagnostics, like battery level, how
`
`often you use your device and apps, and system errors.” AWAA Disclosure; see also Ex. I
`
`(same). Google argues that, because the notice in Figures 1 and 2 in the amended
`
`8
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`Northern District of California
`
`United States District Court
`
`

`

`Case 3:21-cv-09004-CRB Document 64 Filed 12/01/22 Page 9 of 25
`
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`complaint indicates that the “additional Web & App Activity” setting was enabled, not just
`
`the “Web & App Activity” setting, then Hammerling must have “necessarily reviewed” the
`
`AWAA Disclosure in order to enable that setting. Reply (dkt. 61) at 3. It would follow
`
`that Hammerling consented to disclosure of her activity on third party apps “that use
`
`Google services,” because the AWAA Disclosure tells her so. Google argues that this
`
`consent requires dismissal of Plaintiffs’ fraud, privacy, and contract claims. Mot. at 7.
`
`This argument fails because Google’s provision of its current AWAA Disclosure
`
`does not support the conclusion that Hammerling “necessarily reviewed” the same AWAA
`
`Disclosure, and thus consented to it. Google provides only screenshots of the WAA and
`
`AWAA Disclosures taken in September 2022. See Kanig Decl. at 1. Assuming that
`
`Google’s Activity Controls were incorporated into its Privacy Policy, see id., there is no
`
`indication that the disclosures in Google’s Activity Controls were the same when
`
`Hammerling first enabled the setting, nor when her data was collected from third-party
`
`apps from 2019 to 2021. See Am. Compl. ¶¶ 15, 19–21. For their part, while Plaintiffs
`
`may admit that Hammerling enabled the setting at some point, and do admit that she
`
`“necessarily saw” the WAA Disclosure,3 Plaintiffs do not admit that Hammerling saw the
`
`AWAA Disclosure prior to Google’s request for judicial notice. See id. ¶ 23; see also
`
`Opp’n at 16. Thus, it is possible that Hammerling enabled AWAA and did not see the
`
`same, or any, disclosure regarding the additional data she was consenting to be collected
`
`by Google.4
`
`Google relies heavily on In re Facebook, Inc., Consumer Privacy User Profile
`
`Litigation to argue that consent can be found on these facts, but that case is inapposite. In
`
`
`3 It may be argued that because Plaintiffs admit that Hammerling “necessarily saw” the statement
`at the top of the WAA Disclosure (“Saves your activity on Google sites and apps”) that she
`necessarily saw (and chose) the additional setting (“Include . . . activity from sites, apps, and
`devices that use Google services”). But because the Court cannot conclude that the WAA
`Disclosure Hammerling saw was the same as the one provided by Google in its request for judicial
`notice, consent cannot be found on this basis.
`4 Indeed, it is not implausible that AWAA is, or at one point was, a default setting for Android
`users, and thus the setting was enabled without the user having necessarily seen an AWAA
`Disclosure.
`
`9
`
`Northern District of California
`
`United States District Court
`
`

`

`Case 3:21-cv-09004-CRB Document 64 Filed 12/01/22 Page 10 of 25
`
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`Facebook Consumer Privacy, Judge Chhabria found that language in Facebook’s
`
`Statement of Rights and Responsibilities and its Data Use Policy disclosed to users that
`
`others may share their information with app developers, and that users must take specific
`
`steps to prevent this. 402 F. Supp. 3d 767, 792 (N.D. Cal. 2019). It followed that users
`
`that did not adjust their settings accordingly were “deemed to have agreed to the language”
`
`in Facebook’s policies. Id. at 792–93. Google argues that it flows from Facebook
`
`Consumer Privacy that, by enabling “additional App & Web Activity,” consent must be
`
`found here and Plaintiffs’ fraud, privacy, and contract claims must be dismissed on this
`
`basis. Mot. at 7–8.
`
`But a key aspect of Facebook Consumer Privacy was that Judge Chhabria only
`
`found consent where the language in question was present at the time users signed up for
`
`Facebook accounts in 2009. 402 F. Supp. 3d at 793–94. Whether users who signed up
`
`before that language was added consented to it could not be resolved on a motion to
`
`dismiss. Id. So too here: Google has not shown that the current AWAA Disclosure was
`
`presented to users when Hammerling enabled the setting, and thus consent cannot be found
`
`at this early stage as to her.5 What disclosure Hammerling was shown, and whether that
`
`language is coextensive with the current AWAA Disclosure, would be questions of fact for
`
`a later stage in the case. Nevertheless, Plaintiffs’ claims do not survive this motion to
`
`dismiss because their amendments fail to cure the defects found in the Court’s prior order.
`
`D.
`
`Fraud Claims (Claims 3, 4, and 5)
`
`In its prior order, the Court dismissed Plaintiffs’ fraud claims because (1) Plaintiffs
`
`failed to allege that they actually relied on any alleged misrepresentation; and (2) Google
`
`lacked a duty to disclose any alleged omission. The Court dismissed the CLRA claim for
`
`the additional reason that Plaintiffs failed to allege a transaction under the CLRA.
`
`Because Plaintiffs fail to cure these deficiencies in the amended complaint,
`
`
`5 Because it is not clear from the amended complaint whether Jackson enabled the AWA or
`AWAA setting, nor which disclosures she saw when she enabled that setting, this argument also
`fails as applied to Jackson. See Am. Compl. ¶¶ 29, 32, 34.
`10
`
`Northern District of California
`
`United States District Court
`
`

`

`Case 3:21-cv-09004-CRB Document 64 Filed 12/01/22 Page 11 of 25
`
`
`
`Google’s motion to dismiss is again granted as to the CLRA, UCL fraud prong, and
`
`Section 1709 claims.
`
`1. Misrepresentation
`
`As the Court held in its prior order, to plausibly allege a CLRA, Section 1709, or
`
`UCL fraud claim on a misrepresentation theory, “a plaintiff must allege that they relied on
`
`a misrepresentation and suffered injury as a result.” Hammerling, 2022 WL 2812188, at
`
`*6 (citing Moore v. Apple, Inc., 73 F. Supp. 3d 1191, 1200 (N.D. Cal. 2014)). In their
`
`initial complaint, Plaintiffs merely alleged that they “relied upon” the alleged
`
`misrepresentations “when setting up their Android Smartphones.” Compl. (dkt. 1) ¶ 52.
`
`In their amended complaint, Plaintiffs identify additional alleged misrepresentations, see,
`
`e.g., Am. Compl. ¶¶ 23–24, and allege that one plaintiff, Hammerling, “read Google’s
`
`Privacy Policy,” and that she “did not understand this policy to mean (and did not agree)
`
`that Google would collect sensitive data from non-Google apps.” Id. ¶ 25.6 This statement
`
`again fails to plead reliance. The additional allegation that Hammerling read the Privacy
`
`Policy does not state when she read the policy, nor whether she purchased her Android
`
`smartphone in reliance on the alleged misrepresentations in the policy. See Hammerling,
`
`2022 WL 2812188, at *6 (citing Davidson v. Apple, Inc., 16-cv-4942, 2017 WL 976048,
`
`at *8 (N.D. Cal. Mar. 14, 2017), and Donohue v. Apple, Inc., 871 F. Supp. 2d 913, 925
`
`(N.D. Cal. 2012)).
`
`Plaintiffs make three arguments against dismissal based on reliance, all of which are
`
`unpersuasive.
`
`First, Plaintiffs argue that they need not plead actual reliance based on the Privacy
`
`Policy because “there is no indication that Google made a different statement or changed
`
`its policy before Plaintiff purchased her device to create a different result.” Opp’n at 14.
`
`Whether or not this is true, it is beside the point, which is whether Plaintiffs relied on
`
`particular alleged misrepresentations to purchase the phones, to their detriment.
`
`
`6 Plaintiffs do not allege that Jackson read the policy. See Am. Compl.
`11
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`Northern District of California
`
`United States District Court
`
`

`

`Case 3:21-cv-09004-CRB Document 64 Filed 12/01/22 Page 12 of 25
`
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`Hammerling, 2022 WL 2812188, at *6. If Hammerling read the Privacy Policy after she
`
`purchased the phone, even if it was unchanged from the policy that existed prior to her
`
`purchase, she did not purchase the phone in reliance upon the representations in the policy.
`
`Because Plaintiffs do not allege that Hammerling read the policy prior to her purchase, this
`
`argument fails.
`
`Second, Plaintiffs argue that their claims in the amended complaint arise not only
`
`from the Privacy Policy but also from “the misrepresentations Google made on its settings
`
`pages.” Opp’n at 15. Because Plaintiffs argue that they “could not have discovered” the
`
`misrepresentations in these pages “until after purchasing their devices,” they need not
`
`plead reliance prior to purchase. Id. Instead, they relied on these statements “by
`
`continuing to use a device (and supply Google with data) when they otherwise would not
`
`have if Google had disclosed the truth about its practices.” Id. But Plaintiffs cite only to
`
`paragraphs in their amended complaint that reference only the fact that, had they known
`
`“Google would collect [their] sensitive personal data without consent, [they] would not
`
`have purchased, or would have paid significantly less for, [their] Android Smartphones.”
`
`Am. Compl. ¶¶ 26, 35. They do not plead reliance based on continued use of their phones
`
`after viewing the settings pages,7 and thus this theory too fails.
`
`Third and finally, Plaintiffs argue that, with respect to their Section 1709 and UCL
`
`claims, they allege that “Google’s collection of highly sensitive individualized data is a
`
`cognizable harm,” and thus plead an injury of data collection separate and apart from their
`
`purchase of the Android Smartphones. Opp’n at 15. Maybe so, but Plaintiffs do not plead
`
`that they relied on a misrepresentation and suffered this injury as a result. See
`
`Hammerling, 2022 WL 2812188, at *6. Rather, they only state that Google’s data
`
`collection “necessarily occurs after Google misrepresented what data it would collect.”
`
`Opp’n at 15. Because this is not an allegation of reliance on the misrepresentation, but
`
`merely alleging that the alleged misrepresentation was made before the injury, this
`
`
`7 Indeed, they do not plead that Hammerling or Jackson saw or reviewed these settings pages prior
`to reviewing the privacy notices in the amended complaint.
`12
`
`Northern District of California
`
`United States District Court
`
`

`

`Case 3:21-cv-09004-CRB Document 64 Filed 12/01/22 Page 13 of 25
`
`
`
`argument also fails.
`
`Therefore, to the extent Plaintiffs’ fraud claims are based on a misrepresentation
`
`theory, they do not survive Google’s motion to dismiss.
`
`2.
`
`Omission
`
`In its prior order, the Court dismissed Plaintiffs’ fraud claims based on an omission
`
`theory because in order to plead that Google had a duty to disclose the omitted fact,
`
`Plaintiffs must allege that omitted information was “central to the product’s function.”
`
`Hammerling, 2022 WL 2812188, at *8–9 (quoting Hodsdon v. Mars, Inc., 891 F.3d 857,
`
`863 (9th Cir. 2018)). The Court concluded that because Google’s collection of data from
`
`non-Google apps does not render the Plaintiffs’ smartphones “incapable of use” and does
`
`not prevent their phones from “performing a critical or integral function,” any fraud claims
`
`based on an omission theory must be dismissed. Id. at *9 (quoting Knowles v. ARRIS
`
`Int’l PLC, 847 F. App’x 512, 513–14 (9th Cir. 2021), and Ahern v. Apple Inc., 411 F.
`
`Supp. 3d 541, 567 (N.D. Cal. 2019)). Plaintiffs’ argument on this point—that “Google’s
`
`secret collection of non-Google app data from Android device users impacts its ‘central
`
`function’ because privacy is a key—if not the only—consideration in selecting a mobile
`
`device”—is nearly identical to the one the Court dismissed in its prior order, and the Court
`
`is not persuaded a second time. Opp’n at 17; Hammerling, 2022 WL 2812188, at *8
`
`(finding that the argument that “[u]sing apps is at the heart of the smartphone experience”
`
`does not prevent a smartphone from “performing a critical or integral function” or
`
`otherwise render it “incapable of use”).8
`
`In addition, to the extent that Plaintiffs allege a partial omission theory by alleging
`
`that Hammerling reviewed the Privacy Policy, this new allegation still cannot survive a
`
`motion to dismiss because it still does not meet the 9(b) standard. In its prior order, the
`
`
`8 Plaintiffs’ reference to Flores-Mendez v. Zoosk, Inc., 20-cv-4929, 2022 WL 357500, at *4 (N.D.
`Cal.

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket