[Enforcement library](/enforcement)

# In re Google Cloud Contact Center AI: Home Depot callers' CIPA claims dismissed over consent and intent

Consumers alleged that Google's Cloud Contact Center AI listened to their Home Depot customer-service calls without disclosure and could use the recordings to train its models. The court dismissed the CIPA § 631(a) claims: two accountholders consented through Home Depot's privacy statement, and none of the three pleaded that Google intended to listen without consent. The plaintiffs filed an amended complaint on the 12 November 2026 deadline.

## Key facts

- **Regulator or court:** US District Court, Northern District of California
- **Jurisdiction:** California, US
- **Framework:** CIPA § 631(a)
- **Record date:** 2026-10-22
- **Procedural status:** Motion to dismiss granted with leave to amend on 22 October 2026; amended complaint filed 12 November 2026 (Dkt. 142); other named plaintiffs sent to arbitration

A privacy statement that says call recordings go to service providers covered the AI vendor that listened in, for callers who had agreed to it. For a caller who had not, the claim still failed because nothing showed Google meant to listen without consent.

[Start a free scan](/run-free-codebase-scan)

- **Court**: US District Court for the Northern District of California (Judge Rita F. Lin)
- **Case number**: No. 3:23-cv-05437-RFL (consolidated putative class actions)
- **Parties**: In re Google Cloud Contact Center AI Privacy Litigation; remaining plaintiffs James Fox, Peter Samish and Christopher Barulich v. Google. Home Depot is not a party
- **Laws**: California Invasion of Privacy Act § 631(a)
- **Stage**: Motion to dismiss granted with leave to amend, 22 October 2026 (Dkt. 141); amended complaint filed 12 November 2026 (Dkt. 142); other plaintiffs compelled to arbitration (Dkt. 140)
- **Amount**: None
- **Source review**: 13 November 2026

## The problem

When a consumer calls a company that uses Google Cloud Contact Center AI, such as Home Depot, a Google "virtual agent" answers first without saying it is provided by Google. If the caller asks for a person, the call passes to the company's agent, and the plaintiffs alleged that Google keeps listening, giving the agent a real-time transcript, suggested articles and "smart replies", and can use the recordings to improve its own AI models ([Order, pp. 1 to 2](https://law.justia.com/cases/federal/district-courts/california/candce/3:2023cv05437/419848/141/)). The remaining named plaintiffs, James Fox, Peter Samish and Christopher Barulich, all called Home Depot and claimed one count under CIPA § 631(a).

## What the court found

| Question | Holding |
| --- | --- |
| Is consent an element or a defence? | An element the plaintiff must plead. The court followed Atkins v. Amplitude, Perry-Hudson v. Twilio and Smith v. YETI, and read Calhoun v. Google as not deciding the point |
| Accountholders (Fox and Samish) | No plausible lack of consent. Home Depot's account terms incorporated a privacy statement disclosing that customer-care call recordings go to "service providers that process information on \[Home Depot's\] behalf", which plainly covers Google. Real-time sharing and Google not being named did not take it outside that consent |
| Use for Google's own models | Not a § 631(a)(3) claim on its own: use is unlawful only if the information came from a violation of clauses (1) or (2), and Google had consent to listen |
| Non-accountholder (Barulich) | Lack of consent plausibly pleaded. Google did not show he saw or agreed to the privacy statement, and calls commonly being recorded does not establish consent to an unannounced third party |
| Intent (all three) | Not pleaded. § 631(a) requires that Google intended to listen without consent; the complaint only repeated the statutory words. Google's contract requiring Home Depot to obtain consent is relevant but does not end the case as a matter of law |

The court said it "seems unlikely" Fox and Samish could bring claims given the privacy statement, but allowed amendment ([Order, p. 6](https://law.justia.com/cases/federal/district-courts/california/candce/3:2023cv05437/419848/141/)).

## Technical issue

- **Data (alleged):** the audio and content of customer-service calls, live transcripts and call context used to suggest replies.
- **Recipient:** Google, as the provider of the contact-centre AI, with the alleged capability to use recordings to improve its own models.
- **Where:** the phone line, not a website; the consent analysis turned on the company's account terms and privacy statement.

**Inth's technical interpretation:** this is the same question as a chat widget or session-replay vendor on a website. A disclosure that names the category of recipient (service providers) protected the vendor for people who had agreed to it. It did nothing for a caller with no account, whose claim failed only on intent. Vendor contracts that make the customer responsible for consent matter, but the court would not treat them as a complete answer.

Bad:

```ts
// Live-chat or voice assistant loads a third-party AI vendor before any notice
loadVendorWidget('ai-agent');

// Show who is listening and record that the notice was shown first
showNotice('This conversation is handled with our AI service provider and may be recorded.');
consent.record({ purpose: 'support-ai', noticeVersion: 'v3' });
loadVendorWidget('ai-agent');
```

## Timeline

| Date | Event |
| --- | --- |
| 23 October 2023 | Misael Ambriz files the first suit (per a MassArbitration summary; not checked against the docket) |
| Not stated in the order | Cases consolidated; operative complaint Dkt. 112 |
| 22 October 2026 | Order compelling several plaintiffs to arbitration (Dkt. 140) and order granting Google's motion to dismiss the Home Depot callers (Dkt. 141) |
| 12 November 2026 | Deadline for an amended complaint. An amended complaint was filed that day (Dkt. 142, per the court's docket feed as shown by [CaseMagic](https://casemagic.ai/case/cand/3-23-cv-05437)); its contents were not reviewed |

## Outcome

Google's motion to dismiss was granted and the claims of Fox, Samish and Barulich were dismissed with leave to amend. They may not add new claims or parties without leave or a stipulation ([Order, pp. 8 to 9](https://law.justia.com/cases/federal/district-courts/california/candce/3:2023cv05437/419848/141/)). An amended complaint was filed on the 12 November 2026 deadline (Dkt. 142, [docket feed via CaseMagic](https://casemagic.ai/case/cand/3-23-cv-05437)), so the case continues. Which plaintiffs it names and what it alleges were not reviewed. No liability has been found and no money has changed hands.

## What it cost

| Item | Amount | Source |
| --- | --- | --- |
| Damages or settlement | None | [Order](https://law.justia.com/cases/federal/district-courts/california/candce/3:2023cv05437/419848/141/) |
| Defence costs | Not stated in the cited record |  |

## Why it matters

- **Category disclosures can cover AI vendors.** "Service providers" in an accepted privacy statement was enough for real-time AI listening by Google, at least at the pleading stage.
- **People who never accepted the terms are different.** Account holders and non-account callers got different consent results from the same call flow.
- **Intent now has to be pleaded with facts.** Plaintiffs must allege something showing the vendor knew consent was missing, not just repeat the statute.

Related pages: [CIPA § 631 wiretapping](/enforcement/laws/cipa-631-wiretapping), [Session replay and chat recording](/enforcement/issues/session-replay-and-chat-recording), [Notice, consent scope and assent](/enforcement/issues/notice-consent-scope-and-assent).

## How Inth catches this

- **Consent banner**: Shows notice and records consent before chat, voice or session-recording vendors load on your pages, so assent exists for visitors who never created an account.
- **Website audit**: Records which third parties receive chat transcripts, recordings or form content from each page, before and after a choice.

### Out of reach

- Phone lines and contact-centre platforms are outside what a website audit sees. Review them with the teams that run them.

Consent records with choice, notice and policy version and time, which is the kind of record that decided the accountholders' claims here.

[Start a free scan](/run-free-codebase-scan)

## Checks for your own systems

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

### In the repository

- [ ] List every chat, voice, transcription and AI-assist vendor and where it loads.
- [ ] Check vendor contracts for who must obtain consent and whether the vendor may use data for its own models.

### In the browser and network

- [ ] Open a support chat as a logged-out visitor and record what is sent to which vendor before any notice.
- [ ] Confirm the notice names the vendor category and any recording.

### With the people responsible

- [ ] Decide how consent is captured for callers and visitors without an account.
- [ ] Keep versions of privacy statements and account terms with their effective dates.

## Sources and limits

- [Order granting motion to dismiss, Dkt. 141](https://law.justia.com/cases/federal/district-courts/california/candce/3:2023cv05437/419848/141/), filed 22 October 2026
- [MassArbitration summary](https://massarbitration.co/news/google-ai-wiretap-lawsuit-arbitration-lin)
- [CaseMagic docket feed](https://casemagic.ai/case/cand/3-23-cv-05437), showing Dkt. 142 Amended Complaint filed 12 November 2026

The arbitration order (Dkt. 140), the complaint and the docket were not opened, so which plaintiffs and which companies' calls went to arbitration are not stated here. Facts about the product come from the plaintiffs' allegations as the order describes them. The 2023 filing date comes from a secondary summary. The amended complaint (Dkt. 142) was not opened; only its filing is confirmed from the court's docket feed.

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

## Related cases

[Every case in the Enforcement library](/enforcement)