throbber
Case 5:20-cv-05146-NC Document 1 Filed 07/27/20 Page 1 of 93
`
`
`
`Lesley Weaver (Cal. Bar No.191305)
`Angelica M. Ornelas (Cal. Bar No. 285929)
`Joshua D. Samra (Cal. Bar No. 313050)
`BLEICHMAR FONTI & AULD LLP
`555 12th Street, Suite 1600
`Oakland, CA 994607
`Tel.: (415) 445-4003
`Fax: (415) 445-4020
`lweaver@bfalaw.com
`aornelas@bfalaw.com
`jsamra@bfalaw.com
`
`
`
`Laurence D. King (Cal. Bar No. 206423)
`Mario Choi (Cal. Bar No. 243409)
`KAPLAN FOX & KILSHEIMER LLP
`1999 Harrison Street, Suite 1560
`Oakland, CA 94612
`Tel.: (415) 772-4700
`Fax: (415) 772-4707
`lking@kaplanfox.com
`mchoi@kaplanfox.com
`
`Attorneys for Plaintiffs
`
`
`Mitchell M. Breit (pro hac vice to be sought)
`Jason ‘Jay’ Barnes (pro hac vice to be sought)
`An Truong (pro hac vice to be sought)
`Eric Johnson (pro hac vice to be sought)
`SIMMONS HANLY CONROY LLC
`112 Madison Avenue, 7th Floor
`New York, NY 10016
`Tel.: (212) 784-6400
`Fax: (212) 213-5949
`mbreit@simmonsfirm.com
`jaybarnes@simmonsfirm.com
`atruong@simmonsfirm.com
`ejohnson@simmonsfirm.com
`
`David A. Straite (pro hac vice to be sought)
`Aaron L. Schwartz (pro hac vice to be sought)
`KAPLAN FOX & KILSHEIMER LLP
`850 Third Avenue
`New York, NY 10022
`Tel.: (212) 687-1980
`Fax: (212) 687-7715
`dstraite@kaplanfox.com
`aschwartz@kaplanfox.com
`
`
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE NORTHERN DISTRICT OF CALIFORNIA
`SAN JOSE DIVISION
`
`
`
`PATRICK CALHOUN, ELAINE
`CRESPO, HADIYAH JACKSON and
`CLAUDIA KINDLER, on behalf of
`themselves and all others similarly situated,
`
`v.
`
`
`
`
`GOOGLE LLC,
`
`
` Plaintiffs,
`
` Defendant.
`
`
`No. ___________________________
`
`
`CLASS ACTION COMPLAINT
`
`
`DEMAND FOR JURY TRIAL
`
`PUBLIC REDACTED VERSION WITH PLAINTIFFS’ SENSITIVE PERSONAL
`INFORMATION PROVISIONALLY REDACTED PENDING MOTION TO SEAL
`
`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
`
`
`
`
`
`
`
`
`
`
`
`
`
`CLASS ACTION COMPLAINT
`
`Case No.
`
`
`
`

`

`
`
`I.
`
`II.
`
`Case 5:20-cv-05146-NC Document 1 Filed 07/27/20 Page 2 of 93
`
`TABLE OF CONTENTS
`
`Page
`
`INTRODUCTION ................................................................................................................ 1
`
`JURISDICTION AND VENUE ........................................................................................... 3
`
`A.
`
`B.
`
`C.
`
`Personal Jurisdiction ................................................................................................ 3
`
`Subject Matter Jurisdiction ...................................................................................... 3
`
`Venue ....................................................................................................................... 3
`
`III.
`
`THE INTRADISTRICT ASSIGNMENT ............................................................................. 4
`
`IV.
`
`PARTIES .............................................................................................................................. 4
`
`V.
`
`FACTUAL ALLEGATIONS ............................................................................................... 5
`
`A.
`
`B.
`
`C.
`
`D.
`
`E.
`
`F.
`
`G.
`
`H.
`
`I.
`
`J.
`
`Contract Formation .................................................................................................. 5
`
`Relevant Contract Terms.......................................................................................... 8
`
`Google Improperly Collects Personal Information from Un-Synched
`Chrome Users Without Consent and in Breach of Contract .................................. 10
`
`1.
`
`2.
`
`3.
`
`4.
`
`5.
`
`Definition of Personal Information ............................................................ 10
`
`An IP Address + User Agent Is Personal Information ............................... 12
`
`Persistent Cookies Are Personal Information ............................................ 13
`
`X-Client Data Headers Are Personal Information ..................................... 16
`
`Browsing History is Personal Information ................................................. 19
`
`Chrome’s Promise Not To Share PI With Google if Not Synched Was
`Intended To Encourage, Not Diminish, User Engagement .................................... 20
`
`How Google Instructs Chrome to Report PI to Google ......................................... 23
`
`A Sample Visit to The San Jose Mercury News Website Using Chrome –
`Comparison Between a “Synched” Session and “Un-synched” Session ............... 28
`
`Plaintiffs’ Personal Experiences ............................................................................ 33
`
`Google’s Improper Collection of PI from Plaintiffs and Other Un-Synched
`Chrome Users is a Serious Invasion of the Privacy and is Highly Offensive ........ 50
`
`Plaintiffs’ PI Is Property Owned by the Plaintiffs and Has Economic Value ........ 52
`
`Plaintiffs Have Suffered Economic Injury ............................................................. 55
`
`K.
`
`Google Has Been Unjustly Enriched ..................................................................... 58
`
`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
`
`VI.
`
`CLASS ACTION ALLEGATIONS ................................................................................... 63
`
`28
`
`VII. COUNTS ............................................................................................................................. 65
`
`
`
`
`
`
`- i -
`CLASS ACTION COMPLAINT
`
`Case No.
`
`
`
`

`

`Case 5:20-cv-05146-NC Document 1 Filed 07/27/20 Page 3 of 93
`
`
`
`TABLE OF CONTENTS (cont’d.)
`
`COUNT ONE WIRETAP ACT: UNAUTHORIZED INTERCEPTION
`OF ELECTRONIC COMMUNICATIONS ....................................................................... 65
`
`Page
`
`
`COUNT TWO WIRETAP ACT – UNAUTHORIZED DISCLOSURES BY
`AN ECS 18 U.S.C. § 2510, et. seq. ..................................................................................... 68
`
`COUNT THREE STORED COMMUNICATIONS ACT – UNAUTHORIZED
`ACCESS TO STORED ECS COMMUNICATIONS 18 U.S.C. § 2701 ........................... 70
`
`COUNT FOUR STORED COMMUNICATIONS ACT – UNAUTHORIZED
`DISCLOSURES OF STORED COMMUNICATIONS BY AN ECS
`18 U.S.C. § 2701 ................................................................................................................. 72
`
`COUNT FIVE VIOLATION OF THE CALIFORNIA INVASION OF
`PRIVACY ACT (“CIPA”) Cal. Penal Code §§ 631 ........................................................... 72
`
`COUNT SIX INVASION OF PRIVACY ......................................................................... 74
`
`COUNT SEVEN INTRUSION UPON SECLUSION ....................................................... 76
`
`COUNT EIGHT BREACH OF CONTRACT ................................................................... 77
`
`COUNT NINE BREACH OF THE IMPLIED COVENANT OF GOOD
`FAITH AND FAIR DEALING .......................................................................................... 78
`
`COUNT TEN QUASI-CONTRACT (RESTITUTION AND UNJUST
`ENRICHMENT) (IN ALTERNATIVE TO CONTRACT CLAIMS)................................ 79
`
`COUNT ELEVEN VIOLATION OF COMPUTER FRAUD AND ABUSE ACT
`(“CFAA”) 18 U.S.C. §1030(g) ........................................................................................... 79
`
`COUNT TWELVE VIOLATION OF CALIFORNIA COMPUTER DATA
`ACCESS AND FRAUD ACT Cal. Penal Code § 502 ...................................................... 80
`
`COUNT THIRTEEN STATUTORY LARCENY California Penal Code
`§§ 484 and 496 .................................................................................................................... 82
`
`COUNT FOURTEEN VIOLATIONS OF THE CALIFORNIA UNFAIR
`COMPETITION LAW (“UCL”) Cal. Bus. & Prof. Code § 17200, et seq. ........................ 83
`
`COUNT FIFTEEN PUNITIVE DAMAGES Cal. Civ. Code § 3294 ................................ 85
`
`COUNT SIXTEEN DECLARATORY RELIEF 28 U.S.C. § 2201(a) .............................. 85
`
`VIII. PRAYER FOR RELIEF ...................................................................................................... 86
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`IX.
`
`JURY TRIAL DEMAND ................................................................................................... 87
`
`25
`
`26
`
`27
`
`28
`
`
`
`
`
`
`
`
`
`
`- ii -
`CLASS ACTION COMPLAINT
`
`Case No.
`
`
`
`

`

`Case 5:20-cv-05146-NC Document 1 Filed 07/27/20 Page 4 of 93
`Case 5:20-cv-05146-NC Document 1 Filed 07/27/20 Page 4 of 93
`TABLE OF EXHIBITS
`
`DOCUMENT DESCRIPTION
`
`1
`
`Chart of Documents Constituting the Relevant Contract by Date
`
`Google Chrome and Chrome OS Additional Terms of Service dated
`
`Google Terms of Service dated April 14, 2014
`
`Google Terms of Service dated Oct. 25, 2017
`
`Google Terms of Service dated March 31, 2020
`
`Chrome Terms of Service dated Aug. 12, 2010
`
`March 31, 2020
`
`Google Privacy Policy dated June 28, 2016
`
`Google Privacy Policy dated Aug. 29, 2016
`
`Google Privacy Policy dated March 1, 2017
`
`Google Privacy Policy dated April 17, 2017
`
`Google Privacy Policy dated Oct. 2, 2017
`
`Google Privacy Policy dated Dec. 18, 2017
`
`Google Privacy Policy dated May 25, 2018
`
`5
`
`7
`
`2
`
`3
`
`1 l
`
`n Google Privacy Policy dated Jan. 22, 2019
`
`l
`
`5
`
`l
`
`7
`
`2
`
`0
`
`l
`
`2
`
`22
`
`Google Privacy Policy dated Oct. 15, 2019
`
`Google Privacy Policy dated Dec. 19, 2019
`
`Chrome Privacy Notice dated June 21, 2016
`
`Chrome Privacy Notice dated August 30, 2016
`
`Chrome Privacy Notice dated Oct. 11, 2016
`
`Chrome Privacy Notice dated Nov. 30, 2016
`
`Chrome Privacy Notice dated Jan. 24, 2017
`
`Chrome Privacy Notice dated March 7, 2017
`
`Chrome Privacy Notice dated April 25, 2017
`
`Case No.
`- iii -
`ASS CTION 0MPLAINT
`
`
`\OOONON
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`

`

`Case 5:20-cv-05146-NC Document 1 Filed 07/27/20 Page 5 of 93
`Case 5:20-cv-05146-NC Document 1 Filed 07/27/20 Page 5 of 93
`TABLE OF EXHIBITS
`
`.,
`
`Chrome anacy Notice dated Mar 12 2019
`
`,
`
`~
`Chrome anacy Notlce dated Oct 31 2019
`
`.,
`Chrome Privacy Notlce dated Dec 10 2019
`
`Chrome Plivacy Notlce dated March 17 2020
`
`Chrome Privacy Notice dated May 20 2020
`
`- iV -
`(TASS KCTION COMPLAINT
`
`Case No.
`
`\DOONO
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`

`

`Case 5:20-cv-05146-NC Document 1 Filed 07/27/20 Page 6 of 93
`
`
`
`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
`
`I.
`
`INTRODUCTION
`
`1.
`
`This is a nationwide data privacy class action brought by and on behalf of Google
`
`Chrome users who chose not to “Sync” their browsers with their Google accounts while browsing
`
`the web (“Un-Synched Chrome Users”) from July 27, 2016 to the present (the “Relevant Period”).
`
`2.
`
`Google expressly promises Chrome users that they “don’t need to provide any
`
`personal information to use Chrome” and that “[t]he personal information that Chrome stores won’t
`
`be sent to Google unless you choose to store that data in your Google Account by turning on
`
`sync[.]”
`
`3.
`
`Despite these express and binding promises, Google intentionally and unlawfully
`
`causes Chrome to record and send users’ personal information to Google regardless of whether a
`
`user elects to Sync or even has a Google account.
`
`4.
`
`Examples of personal data improperly created and sent to Google by Chrome
`
`include:
`
`a.
`
`b.
`
`c.
`
`d.
`
`IP addresses linked to user agents;
`
`Unique, persistent cookie identifiers including the Client ID;
`
`Unique browser identifiers called X-Client Data Headers; and
`
`Browsing history.
`
`5.
`
`This Complaint provides specific examples of the personal data flow that Chrome
`
`sent from Plaintiffs’ devices as they used Chrome while not Synched, demonstrating that Chrome
`
`secretly sends personal information to Google even when a Chrome user does not Sync.
`
`6.
`
`Google’s contract with Chrome users designates California law, and consistent with
`
`California law, defines “Personal Information” as “information that you provide to us which
`
`personally identifies you . . . or other data that can be reasonably linked to such information by
`
`Google, such as information we associate with your Google Account.”
`
`7.
`
`Each category of data identified above is “personal information” because it either
`
`personally identifies the user or can be reasonably linked to such information. Furthermore, Google
`
`affirmatively discloses that it associates data gathered from Chrome with users. Google has
`
`therefore breached its contract with Un-Synched Chrome Users.
`
`
`
`
`
`
`- 1 -
`CLASS ACTION COMPLAINT
`
`Case No.
`
`
`
`

`

`Case 5:20-cv-05146-NC Document 1 Filed 07/27/20 Page 7 of 93
`
`
`
`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
`
`8.
`
`The improperly collected web browsing history also consists of electronic
`
`communications that contain content protected by California and federal wiretap laws. Google
`
`collects the content contemporaneously with the communications; Google does not obtain consent
`
`from Un-Synched Chrome Users to intercept these communications; and Google is not a party to
`
`them. Google is thus violating the federal Electronic Communications Privacy Act and analogue
`
`California statutes.
`
`9.
`
`Google’s actions are a serious violation of user privacy. Google tracking code is
`
`found on websites accounting for more than half of all internet traffic and Chrome is the dominant
`
`web browser (used on a majority of desktop computers in the United States), giving Google
`
`unprecedented power to surveil the lives of more than half of the online country in real time. And
`
`because some of Google’s third-party tracking cookies are disguised as first-party cookies to
`
`facilitate cookie synching, Google is misrepresenting its privacy practices in ways that have been
`
`successfully challenged by the FTC in the past.1
`
`10.
`
`Google’s extensive network of affiliates—Google Sites, Google Apps, Google
`
`Account, Google Drive, Google AdWords—as well as its business partnerships means that sharing
`
`information with Google feeds it into a massive interconnected database of surveillance material.
`
`Google’s surveillance of the Plaintiffs and other Un-Synched Chrome Users directly contradicts its
`
`promises to honor users’ choice not to share data. This is a serious and irreversible invasion of
`
`privacy that is invisible to Google users.
`
`11.
`
`Google’s actions also constitute rank theft. Plaintiffs’ PI is a form of property
`
`recognized under California law and has economic value in the marketplace. Taking Plaintiffs’ PI
`
`from their computers without consent is larceny; any profits earned on the PI are unjustly earned at
`
`the expense of Plaintiffs and must be disgorged. Had Google been transparent about its level of
`
`surveillance, user engagement—a key metric for Google’s sales—would have decreased.
`
`12.
`
`Google’s actions also constitute unlawful computer intrusion under California and
`
`federal law. Google introduced computer code into Plaintiffs’ computers and caused damage
`
`
`1 United States v. Google, Inc., 12-cv-4177-SI (N.D. Cal.), complaint dated Aug. 8, 2012, at ¶ 46-
`47.
`
`
`
`
`
`
`- 2 -
`CLASS ACTION COMPLAINT
`
`Case No.
`
`
`
`

`

`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
`
`Case 5:20-cv-05146-NC Document 1 Filed 07/27/20 Page 8 of 93
`
`
`
`without authorization by turning the computers into surveillance machines that reported Plaintiffs’
`
`personal information, including private web browsing, to Google, in real time.
`
`13.
`
`Plaintiffs and the other Un-Synched Chrome Users have suffered privacy harm and
`
`economic harm as a result of Google’s wrongful acts. Plaintiffs therefore bring contract, statutory,
`
`common law and equitable claims against Google for money damages, restitution, disgorgement,
`
`punitive damages and injunctive relief.
`
`II.
`
`JURISDICTION AND VENUE
`
`A.
`
`14.
`
`Personal Jurisdiction
`
`This Court has personal jurisdiction over Defendant because Defendant is
`
`headquartered in this District. Google also concedes personal jurisdiction in the current and prior
`
`general Google Terms of Service. See Exhibits 2 through 4.
`
`B.
`
`15.
`
`Subject Matter Jurisdiction
`
`This Court has subject matter jurisdiction over the federal claims in this action,
`
`namely the Federal Wiretap Act, 18 U.S.C. § 2511 (the “Wiretap Act”), the Stored Communication
`
`Act, 18 U.S.C. § 2701 (“SCA”), the Computer Fraud and Abuse Act, 18 U.S.C. § 1030 (the
`
`“CFAA”) and request for Declaratory Relief under 18 U.S.C. § 2201, pursuant to 28 U.S.C. § 1331.
`
`16.
`
`This Court also has subject matter jurisdiction over this entire action pursuant to the
`
`Class Action Fairness Act (“CAFA”), 28 U.S.C. § 1332(d), because this is a class action in which
`
`the amount in controversy exceeds $5,000,000, and at least one member of the class is a citizen of
`
`a state other than California or Delaware.
`
`17.
`
`This Court also has supplemental jurisdiction over the state law claims in this action
`
`pursuant to 28 U.S.C. § 1367 because the state law claims form part of the same case or controversy
`
`as those that give rise to the federal claims.
`
`C.
`
`18.
`
`Venue
`
`Venue is proper in this District because the Defendant is headquartered in this
`
`District. In addition, in the current Google general Terms of Service and prior versions, Google
`
`purports to bind Plaintiffs to bring disputes in this District. See Exhibits 2 through 4.
`
`
`
`
`
`
`- 3 -
`CLASS ACTION COMPLAINT
`
`Case No.
`
`
`
`

`

`Case 5:20-cv-05146-NC Document 1 Filed 07/27/20 Page 9 of 93
`Case 5:20-cv-05146-NC Document 1 Filed 07/27/20 Page 9 of 93
`
`III.
`
`THE INTRADISTRICT ASSIGNMENT
`
`19.
`
`Assignment of this case to the San Jose Division is proper pursuant to Civil Local
`
`Rule 3-2(c)(e) because a substantial part of the events or omissions giving rise to Plaintiffs’ claims
`
`occurred in Santa Clara County, California.
`
`IV.
`
`PARTIES
`
`20.
`
`Plaintiff Patrick Calhoun is an adult domiciled in Florida. Plaintiff has used the
`
`Chrome browser on his personal
`
`laptop for numerous activities,
`
`including exchanging
`
`communications with state governmentagencie=.
`
`Plaintiff has also routinely used the Chrome browser to exchange communications about news,
`
`politics, and more. Plaintiff has not enabled Sync with his Google accounts on his personal laptop
`
`and never consented to Chrome sharing his Personal Information, including the contents of his
`
`Intemet communications, with Google. Despite his lack of consent and expressly promising
`
`otherwise, Chrome shared Calhoun’s personal information with Google, including the content of
`
`his communications. Plaintiff has temporarily stopped using Chrome but wishes to use it again
`
`once Google stops tracking un-synched users.
`
`21.
`
`Plaintiff Elaine Crespo is an adult domiciled in Florida. Plaintiff has used the
`
`Chrome browser on her personal
`
`laptop for numerous activities,
`
`including exchanging
`
`communications relating to banking, her children’s education, and for her employment. Plaintiff
`
`has not enabled Sync with her Google accormts on her personal laptop and never consented to
`
`\OOONQ
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`Chrome share her personal information, including the contents of her Internet communications,
`
`with Google. Despite her lack of consent and expressly promising otherwise, Chrome shared
`
`Crespo’s personal information with Google,
`
`including the contents of her communications.
`
`Plaintiff has temporarily stopped using Chrome but wishes to use it again once Google stops
`
`tracking un-synched users.
`
`22.
`
`Plaintiff Hadiyah Jackson is an adult domiciled in Pennsylvania. Plaintiff and her
`
`family have used the Chrome browser on her personal laptop for numerous activities, including
`
`exchanging communications with state government agencies regarding anE
`
`Plaintiff has not enabled Sync with her Google accounts on her personal
`
`——
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`- 4 -
`CEASS KCTION COMPLAINT
`
`Case No.
`
`

`

`Case 5:20-cv-05146-NC Document 1 Filed 07/27/20 Page 10 of 93
`
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`laptops and never consented to Chrome sharing her Personal Information, including the contents of
`
`her Internet communications, with Google. Despite her lack of consent and expressly promising
`
`otherwise, Chrome shared Jackson’s personal information with Google, including the content of
`
`her communications. Plaintiff has temporarily stopped using Chrome but wishes to use it again
`
`once Google stops tracking un-synched users.
`
`23.
`
`Plaintiff Claudia Kindler is an adult domiciled in California. Plaintiff has used the
`
`Chrome browser on her personal laptop for numerous activities, including exchanging
`
`communications with her banks, healthcare providers, and continuing education providers for her
`
`employment. Kindler has also routinely used the Chrome browser to exchange communications
`
`about politics and more. Plaintiff has not enabled Sync with her Google accounts on her personal
`
`laptops and never consented to Chrome sharing her Personal Information, including the contents of
`
`her Internet communications, with Google. Despite her lack of consent and expressly promising
`
`otherwise, Chrome shared Kindler’s personal information with Google, including the content of
`
`her communications. Plaintiff has temporarily stopped using Chrome but wishes to use it again
`
`once Google stops tracking un-synched users.
`
`24.
`
`Google LLC (“Google”) is a Delaware Limited Liability Company based at
`
`1600 Amphitheatre Way, Mountain View, California, whose memberships interests are entirely
`
`held by its parent holding company, Alphabet, Inc. (“Alphabet”), headquartered at the same
`
`address. Alphabet trades under the stock trading symbols GOOG and GOOGL. Alphabet generates
`
`revenues primarily by delivered targeted online advertising through the Google LLC subsidiary.
`
`All operations relevant to this complaint are run by Google LLC.
`
`25.
`
`In this Complaint, “Google” refers to Google LLC unless otherwise specified
`
`23
`
`V.
`
`FACTUAL ALLEGATIONS
`
`A.
`
`26.
`
`Contract Formation
`
`The current contract governing the relationship between Google and Chrome with
`
`respect to Chrome consists of three documents: the Google general Terms of Service dated
`
`March 31, 2020 (Exhibit 4) (“General TOS”); the Google Chrome and Chrome OS Additional
`
`24
`
`25
`
`26
`
`27
`
`28
`
`
`
`
`
`
`- 5 -
`CLASS ACTION COMPLAINT
`
`Case No.
`
`
`
`

`

`Case 5:20-cv-05146-NC Document 1 Filed 07/27/20 Page 11 of 93
`Case 5:20-cv-05146-NC Document 1 Filed 07/27/20 Page 11 of 93
`
`Terms of Service dated March 31, 2020 (Exhibit 6) (“Chrome TOS”); and the Chrome Privacy
`
`Notice dated May 20, 2020 (Exhibit 33) (“Chrome Privacy Notice” .2
`
`27.
`
`These documents are revised frequently, see chart in Exhibit 1, but the core contract
`
`terms relevant to this Action are the same throughout the Relevant Period.
`
`28.
`
`The General TOS incorporates by reference and hyperlinks to “service-specific
`
`additional terms and policies” as illustrated below and in Exhibit 4. The General TOS provides that
`
`certain identified services are governed by the General TOS as well as “additional terms and
`
`policies that apply to that particular service.” It continues, “[t]he Terms of Service, additional terms
`
`andpolicies define our relationship and mutual expectations as you use these services”:
`
`llST OF SFPVICFS 8. SERVICF-SPECIFIC ADDITIONAL TERMS
`
`relationship and mutual expectations as you use these services.
`
`Services that use Google’s Terms of Service & their service-specific
`
`additional terms and policies
`
`Google's Terms of Service applies to me services listed below Next to eacr serwce, we also list additional terms ard
`
`policies that apply to that particclar serv cet T'te Te’ms of Ser/ice‘ additional terms and Do icies define ocr
`
`2 Prior to March 31, 2020, the contract also included a foruth document, the Google general Privacy
`Policy (Exhibits 7 through 16).
`
`- 6 -
`CEASS KCTION COMPLAINT
`
`Case No.
`
`AWN
`
`\OOONON
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`

`

`Case 5:20-cv-05146-NC Document 1 Filed 07/27/20 Page 12 of 93
`Case 5:20-cv-05146-NC Document 1 Filed 07/27/20 Page 12 of 93
`
`29.
`
`The General TOS then identifies Chrome as a “service” and identifies (and
`
`hyperlinks to) three documents that govern the use of Chrome and together constitute the contract:
`
`9 Chrome and Chrome 08
`
`Terms of Service
`
`Google Chrome Privacy Notice E
`
`Google Chrome and Chrome OS Additional Terms of ServiceZ
`
`30.
`
`The General TOS contains 15 separate references and links to the “service-specific
`
`additional terms and policies.” Every time this term is referenced, a hyperlink is included that
`
`incorporates and links users to the “List of services & service-specific additional terms.”
`
`31.
`
`Prior to March 31, 2020, the Chrome TOS itself also expressly incorporated the
`
`Chrome Privacy Notice as a part of the contract. The Chrome TOS dated Aug. 12, 2010 states that
`
`users’ “agreement with Google” includes “the terms set forth” in the General TOS as well as
`
`“Google Chrome Additional Terms of Service and terms of any Legal Notices applicable to the
`
`Services.” See Ex. 5.
`
`32.
`
`The Chrome TOS further states that “[flor more information about Google’s data
`
`protection practices, please read Google’s privacy policy at http://www.google.com/privacy.html
`
`and at https://www.google.com/intl/en/chrome/privacyl.” These two URLs link to the web pages
`
`where the Google Privacy Policy and the Chrome Privacy Notice were publicly available.
`
`33.
`
`Finally, the General TOS specifies that “service-specific additional terms” govern
`
`where there is a conflict with the General TOS:
`
`If these terms conflict with the servicespecific additional terms, the additional terms will govern for that service.
`
`- 7 -
`CEASS KCTION COMPLAINT
`
`Case No.
`
`\OOONON
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`

`

`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
`
`Case 5:20-cv-05146-NC Document 1 Filed 07/27/20 Page 13 of 93
`
`
`
`34.
`
`At all times during the Relevant Period, therefore, the Chrome Privacy Notice was
`
`a part of the contract between Plaintiffs and Google and supersedes any conflicting term in the
`
`General TOS.
`
`B.
`
`35.
`
`Relevant Contract Terms
`
`The Chrome Privacy Notice represents that it is the place where users can “Learn to
`
`control the information that’s collected, stored, and shared when you use the Google Chrome
`
`browser[.]” See Ex. 33.
`
`36.
`
`In the Chrome Privacy Notice, Google promised that Chrome would not send any
`
`Personal Information to Google unless the Chrome User affirmatively chose to Sync the browser
`
`with his or her Google Account.
`
`37.
`
`Specifically, from June 2016 to present, all versions of the Chrome Privacy Notice
`
`have promised that “You don’t need to provide any personal information to use Chrome.” See
`
`Exs. 17-33.
`
`38.
`
`In addition, all versions of the Chrome Privacy Notice have promised that Chrome
`
`will not send Personal Information to Google unless the Chrome user chooses to Sync the browser
`
`with his or her Google account:
`
`a.
`
`From January 30, 2019 to the present, Google promises that “the personal
`
`information that Chrome stores won’t be sent to Google unless you choose to
`
`store that data in your Google Account by turning on sync.” See Exs. 28-33.
`
`b.
`
`From September 24, 2018 to January 30, 2019, Google promised that “the
`
`personal information that Chrome stores won’t be sent to Google unless you
`
`choose to store that data in your Google Account by turning on Chrome
`
`sync.” See Exs. 25-27.
`
`c.
`
`Prior to September 24, 2018, the Chrome Privacy Notice promised “The
`
`personal information that Chrome stores won’t be sent to Google unless you
`
`choose to store that data in your Google Account by signing in to Chrome.
`
`Signing in enables Chrome’s synchronization feature.” See Exs. 17-24.
`
`
`
`
`
`
`- 8 -
`CLASS ACTION COMPLAINT
`
`Case No.
`
`
`
`

`

`Case 5:20-cv-05146-NC Document 1 Filed 07/27/20 Page 14 of 93
`Case 5:20-cv-05146—NC Document 1 Filed 07/27/20 Page 14 of 93
`
`39.
`
`The Chrome Privacy Notice has always promised that Sync will only be enabled by
`
`your choice to take an affirmative act. Synching has never been a default setting during the Relevant
`
`Period. For example, from September 24, 2018 to present, 3 Chrome user had to take the follow
`
`affmnative steps to enable Sync:
`
`a.
`
`On a desktop,3 the user can enable Sync by taking “open[ing] Chrome,
`
`clicking the “Profile” icon at the top right, signing in to the user’s “Google
`
`Account,” clicking “Turn on sync” and then “Turn on.” An example is shown
`
`here:
`
`Sign in and turn on sync
`
`To turn on sync, you'll need a Google Account
`
`A If you want to sync your info across all your devices. click Turn on sync > Turn on
`
`1 On your computer, open Chrome.
`
`2. At the top right, click Profile
`
`3 Sign in to your Google Account
`
`b.
`
`On a mobile device, a user downloads the Chrome app, clicks the “. . .” to the
`
`right of the address bar, clicks “Settings,” then clicks “Sign in to Chrome,”
`
`then “Tap the account [the user] want[s] to use,” tap “Continue,” and then tap
`
`“OK, Got it.” An example of these steps for Android users is shown below:4
`
`Help,
`Chrome
`Google
`Chrome,
`in
`of
`and
`on
`sync
`3 Turning
`https://support.google.com/chrome/answer/ 1 85277?co=GENIE.Platform%3DDesktop&oco=1
`(last visited July 19, 2020).
`
`Help
`Chrome
`Google
`Chrome,
`in
`of
`and
`on
`sync
`4 Turn
`https://support.google.com/chrome/answer/ l 85277?co=GENIE.Platfonn%3DAndroid&oco=1
`(last visited July 19, 2020).
`
`- 9 -
`CEASS KCTION COMPLAINT
`
`Case No.
`
`\OOONONUI-RWNH
`
`NNNNNNNNNI—I—i—i—i—i—i—i—i—i—OONONUI-hWNI-‘OOOONONUI-RWNI-‘O
`
`

`

`Case 5:20-cv-05146-NC Document 1 Filed 07/27/20 Page 15 of 93
`Case 5:20-cv-05146—NC Document 1 Filed 07/27/20 Page 15 of 93
`
`Sign in to Chrome
`
`To turn on sync. you‘ll need a Google Account.
`
`4 Tap Continue > 0K, Got it
`
`1. On your Android phone or tablet, open the Chrome app 0 if you don't yet have the Google Chrome app,
`download It from Google Play E
`
`2, To the right of the address bar, tap More 5
`3 Tap the account you want to use.
`
`> Settings > Sign in to Chrome.
`
`40.
`
`Prior to September 24, 2018, the process was different but still required at least four
`
`affirmative steps to enable Chrome synchronization through the Chrome sign-in feature.5
`
`I! you have more than one account or you share your computer wrth others, find out how to manage multiple people in
`Chrome.
`
`inlormation to share across other devuces where you're Signed in to Chrome.
`
`1. Open Chrome.
`
`2. In the top-right, click the button with your name or People 3.
`
`3. Click Sign in to Chrome.
`
`4. Sign in with your Google Account.
`
`5. To customise your sync settings, click More 2
`
`> Settings > Advanced sync settings. You can choose what
`
`41.
`
`On mobile devices, users had to take similar steps to enable Chrome.6
`
`C.
`
`Google Improperly Collects Personal Information from Un-Synched Chrome
`Users Without Consent and in Breach of Contract
`
`1.
`
`Definition of Personal Information
`
`42.
`
`43.
`
`The contract designates California law as the governing law.
`
`California law defines “Personal Information” as, and it is used in this Complaint to
`
`mean: “information that identifies, relates to, describes, is reasonably capable ofbeing associated
`
`with, or could reasonably be linked, directly or indirectly, with a particular consumer or household.
`
`5 Sign in to Chrome, Chrome Help, https://web.archive.org/web/20170411045120
`/https://support.google.com/chrome/answer/l 85277 (archived on Apr. 1 1, 2017).
`6 See e.g., Travis Boylss, How to Svnc Bookmarks on Chrome on iPhone or iPad, WikiHow
`(Dec. 24, 2017), https://www.wikihow.tech/SyncBookmarks-on—Chrome-on—iPhone-or—iPad.
`
`- 10 -
`Cfiss KCTION COMPLAINT
`
`Case No.
`
`\OOONQUIAUJNI—
`
`NNNNNNNNNl—‘l—‘l—‘l—‘l—‘l—l—l—I—il—i
`
`OONQUIAUJNI—OOOONQUIAWNI—O
`
`

`

`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
`
`Case 5:20-cv-05146-NC Document 1 Filed 07/27/20 Page 16 of 93
`
`
`
`Personal information includes, but is not limited to, the following if it identifies, relates to,
`
`describes, is reasonably capable of being associated with, or could be reason

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