Skip to content

Inth is now agentic by default. Use it from Claude, ChatGPT or Cursor.

See how
Opens the cited record in a new tab

Garcia v. Butterfly Network: a chat vendor that routes transcripts through its servers can support an aiding claim

In California state court, a short complaint about a chat widget can survive a demurrer if it says the vendor receives and uses the transcripts. Check what your chat vendor receives, where it is routed and what its terms let it do with the content.

Regulator
Los Angeles Superior Court
Law
CIPA
Stage
Tentative: Demurrer overruled. Tentative ruling

The problem

Silvia Garcia alleged that Butterfly Network allowed Drift, a chat vendor, to embed code in the chat feature on butterflynetwork.com. The chat was "routed through Drift's servers so they may simultaneously collect a transcript of that chat, along with other user data", and Butterfly did not tell users (Tentative ruling, citing Complaint ¶¶ 10, 29–35).

What was alleged

ClaimWhat the law requiresFacts allegedResult
CIPA §631, aidingA third party reads or uses chat contents in transit without consent, and the site aids itAs the tentative summarizes the complaint, Drift collected transcripts in real time and "exploited, monetized, and used the data it gathered through the chat feature in real time" (¶ 27); plaintiff used a smartphone (¶ 32) (tentative)Demurrer overruled: violation by Drift and aiding by Butterfly adequately alleged

Technical issue

  • Tools or vendors: Drift chat, embedded in Butterfly's website.
  • Where: the website chat feature.
  • What data: chat transcripts "along with other user data".
  • When: during the chat, with no disclosure alleged.
  • How it came to light: the complaint. No technical evidence was tested.

Inth's technical interpretation: a hosted chat widget loads the vendor's script and iframe, and each message goes to the vendor's servers before an agent or bot sees it. That is how such products work, so the legal question becomes what the vendor may do with the transcript. The court relied on Valenzuela v. Nationwide, where the complaint alleged the vendor used chat data and the site contracted for its benefit (tentative).

Illustrative pattern, not the defendant's code. Widget loads on every page with no notice:

Illustrative pattern, not the defendant's code. Widget registered with c15t, with a notice shown before the first message:

<script>
  // vendor chat loader, runs for every visitor on page load
  (function () {
    var s = document.createElement('script');
    s.src = 'https://chat.vendor.example/widget.js';
    document.head.appendChild(s);
  })();
</script>

Timeline

  1. Complaint filed (Trellis docket)

  2. First amended complaint

  3. Demurrer to the first amended complaint filed

  4. Tentative ruling overrules the demurrer (tentative); docket records the result as overruled and a minute order that day (Trellis)

  5. Notice of settlement

  6. Request for dismissal of the entire action with prejudice, entered 9 January 2025

Outcome

The court held: "The Court finds that the Complaint sufficiently alleges facts showing that Drift violated CIPA. Plaintiff has also stated facts alleging that Defendant aided the violations of Drift" (tentative). It treated federal district court decisions as persuasive but not binding, and said citing unpublished superior court rulings is improper. The parties settled about six weeks later. The amount was not filed. A pleading ruling is not a finding that Drift intercepted anything.

What it cost

ItemRecord
SettlementNot stated in the cited record
Fee awardNot stated in the cited record
Defense costsNot stated in the cited record

Why it matters

  • State court is where chat claims survive the pleadings. Federal courts have required evidence that a vendor actually read messages; see Gutierrez v. Converse. LA Superior Court accepted allegations of vendor use at the demurrer stage.
  • Individual suits settle early. This was an individual action, and it ended in a settlement within weeks of the ruling.
  • See Session replay and chat recording and CIPA §631.

How Inth catches this

  • Code audit

    Flags a pull request that adds a chat SDK and maps chat content to the vendor's endpoints and policy record.

  • Website audit

    Records the chat vendor's scripts and domains on each page, with time, region and consent state.

  • Consent banner

    Chat waits behind the banner where the policy is opt-in. Inth's default California policy is opt-out, so a chat widget can load there before any choice unless you configure California opt-in.

Out of reach

  • Inth cannot see what a chat vendor does with transcripts on its servers; that is in the vendor contract.

Finding history shows when the chat vendor was added and approved.

Start a free scan

Checks for your own systems

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

0 of 3 done

In the repository

0 of 1 done

In the browser and network

0 of 1 done

With the people responsible

0 of 1 done

Sources and limits

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