Skip to content
Opens the cited record in a new tab

Calhoun v. Google: a product-specific privacy promise can override your general policy

If one of your products has its own privacy notice, a court will read it alongside, and possibly above, your company-wide policy. Google's Chrome notice told users their personal information would not go to Google unless they turned on Sync. The Ninth Circuit held that a reasonable user could rely on that, whatever the general policy said.

Regulator
US Court of Appeals, Ninth Circuit
Law
California privacy and federal interception claims
Stage
Summary judgment reversed 2024; class certification denied; administratively closed 22 September 2026 pending another appeal. Opinion or order

The problem

The plaintiffs used Chrome without syncing it to a Google account. Chrome's privacy notice said: "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" (Op. pp. 5–6). They alleged that Chrome still sent Google their cookie identifiers, browsing activity, IP address, user agent and a Chrome-specific identifier whenever they visited a site that used Google services.

What was alleged

ClaimWhat the law requiresFacts allegedResult
CIPA, intrusion, contract, implied covenant, larceny, UCLEach fails if the plaintiff consented; consent is Google's burdenChrome sent data to Google despite the no-Sync promiseSummary judgment for Google reversed; consent is for trial
Class claimsCommon questions must predominateMillions of un-synced Chrome usersClass certification denied, June 2025 (reported by Reuters)

Technical issue

  • Tools or vendors: Google's own browser and the Google services embedded in third-party sites.
  • Where: any website "that includes Google surveillance source code", in the complaint's words.
  • What data: "unique, persistent cookie identifiers"; browsing history in GET requests; in many cases the contents of POST communications; IP address and user agent; and the x-client-data header, which with IP and user agent "uniquely identifies every individual download[ed] version of the Chrome browser" (Op. pp. 7–8).
  • When: regardless of whether the user had turned on Sync, from 27 July 2016.
  • How it came to light: expert evidence; the district court held a 7.5-hour evidentiary hearing on whether the collection was "browser-agnostic" (p. 17).

Inth's technical interpretation: most of the data flows here are ordinary third-party requests: a page loads Google code, the browser sends Google's cookies and the request details. The district court found them the same in every browser and treated the general policy as controlling. The Ninth Circuit said that technical fact was beside the point: what matters is what the product's own notice led users to expect. A team that writes "we don't send X unless you turn on Y" must check every path that sends X.

Illustrative pattern, not the defendant's code.
// Bad: the settings screen says "nothing leaves your device unless Sync is on",
// but a shared telemetry client runs for everyone
telemetry.send({ event: 'page_visit', url: location.href, clientId });

Timeline

  1. Motion to dismiss on consent denied (Judge Koh) (Dkt. 142; Op. pp. 9–11)

  2. Summary judgment for Google on consent (Reuters)

  3. Ninth Circuit reverses and remands (opinion)

  4. Class certification denied (Reuters)

  5. Google's motion to dismiss individual claims largely denied (reported by DiCello Levitt)

  6. Case administratively closed pending Williams v. Capital One, 9th Cir. No. 26-5547 (Dkt. 1149)

Outcome

The Ninth Circuit held that the district court should have asked "whether a reasonable user reading them would think that he or she was consenting to the data collection" (Op. p. 17), and instead let the case turn on a technical question. "[T]he governing standard is what a 'reasonable user' of a service would understand they were consenting to, not what a technical expert would" (Op. p. 18). Read together, Google's general policy and the Chrome notice's "affirmative statement" meant a reasonable user "would not necessarily understand" they had consented (p. 21). The court added that the reasonable user is not "an experienced business lawyer" (p. 22). Consent went back for trial, assuming a class was certified. The opinion is published and binds courts in the Ninth Circuit.

After remand. Judge Gonzalez Rogers denied class certification with prejudice in June 2025, writing that "[i]nquiries relating to Google's implied consent defense will overwhelm the damages claims for all causes of action" (reported by Reuters). The named plaintiffs continued individually, and class counsel report that in June 2026 Wiretap Act, invasion of privacy, CDAFA and declaratory claims survived a motion to dismiss (DiCello Levitt). On 22 September 2026, at the parties' request, the court closed the case administratively until the Ninth Circuit decides Williams v. Capital One Financial Corporation, No. 26-5547 (Dkt. 1149).

What it cost

ItemRecord
Damages or settlementNone
Data preservationGoogle was ordered to keep preserving data under a special preservation order after remand (Dkt. 1067); cost not stated
Fees and defense costsNot stated in the cited record

Why it matters

  • Specific beats general. Courts now read product notices, help pages and settings copy against the general privacy policy. Lakes v. Ubisoft distinguished Calhoun because Ubisoft had no contrary product promise (Lakes v. Ubisoft); Rack Room's "not personally identifiable" line did the same damage as Chrome's (Smith v. Rack Room Shoes).
  • Consent cuts both ways. The same consent question that kept Calhoun alive on appeal later defeated class certification, as it did in Ingraham v. Capital One.
  • See Notice, consent scope and assent.

How Inth catches this

  • Code audit

    Traces a data flow from the client to an external destination and connects it to the consent state and policy record it affects, so a promise in a settings screen can be checked against the code path that sends data.

  • Website audit

    Records requests to Google domains with the page, time, region and consent state, and surfaces policy drift when production stops matching your disclosures.

  • Consent banner

    Under an opt-in policy, the Google tag loads with Google Consent Mode v2 defaults set to denied, and an update is sent when the visitor chooses. Inth's default California policy is opt-out, so tags run until the visitor opts out.

Out of reach

  • This case is about a browser vendor's own first-party collection; a website audit of your site cannot observe what a browser sends home.

Finding history and consent records show which disclosure applied to a given visitor.

Start a free scan

Checks for your own systems

Your ticks stay on this page. Inth does not save or send them.

0 of 5 done

In the repository

0 of 2 done

In the browser and network

0 of 1 done

With the people responsible

0 of 2 done

Sources and limits

Source review: 17 October 2026. This page describes the cited records and procedural stage. It does not audit Google's current systems. Inth wrote the technical checks; they cannot decide which laws apply or prove compliance.