Opens the cited record in a new tab

CIPA §632 and §632.7: recording confidential communications in apps, chat and AI tools

Section 632 forbids recording a "confidential communication" without everyone's consent. Unlike §631, it reaches parties to the conversation as well as outsiders, and it has no "in transit" requirement. The hard element is confidentiality. A health app, a therapy chat or a medical call can meet it; an ordinary shopping session usually does not. Section 632.7 covers calls involving mobile and cordless phones and fits website traffic poorly.

Source review
17 October 2026

What the law says

Penal Code §632(a) applies to "A person who, intentionally and without the consent of all parties to a confidential communication, uses an electronic amplifying or recording device to eavesdrop upon or record the confidential communication". It covers communications "carried on among the parties in the presence of one another or by means of a telegraph, telephone, or other device, except a radio".

Section 632(c) defines "confidential communication" as "any communication carried on in circumstances as may reasonably indicate that any party to the communication desires it to be confined to the parties thereto". It excludes communications in circumstances "in which the parties to the communication may reasonably expect that the communication may be overheard or recorded". The fine is up to USD 2,500 per violation.

The elements are:

  • intentional use of an electronic amplifying or recording device;
  • to eavesdrop on or record;
  • a confidential communication;
  • without the consent of all parties.

The California Supreme Court reads §632 as requiring notice first. As quoted in Javier v. Assurance IQ, it "prohibits . . . a party . . . from recording [a] conversation without first informing all parties to the conversation that the conversation is being recorded" (Javier memorandum, p. 4, quoting Kearney v. Salomon Smith Barney, 137 P.3d 914, 930 (Cal. 2006)).

Section 632.7(a) covers anyone who, "without the consent of all of the parties to a communication, intercepts or receives and intentionally records" a communication "transmitted between two cellular radio telephones, a cellular radio telephone and a landline telephone, two cordless telephones" and similar pairs. "Communication" includes "voice, data, or image" (§632.7(d)(3)). The California Supreme Court held that §632.7 "prohibits parties as well as nonparties from intentionally recording" such communications (Smith v. LoanMe, S260391, 1 April 2021, p. 26).

Who can sue and what they can recover

Section 637.2 allows the greater of USD 5,000 per violation or three times actual damages, plus an injunction, with no need to prove actual damages. SB 690 limits private suits only for §638.51 (SB 690 text).

  • Limitations period (labelled uncertain). Federal courts apply one year to CIPA claims (Shah v. Politico, Dkt. 74, p. 8). We did not find a published California appellate decision on §632 website or app claims that fixes it.
  • Standing. Federal plaintiffs also need a concrete injury; see standing.

How it is used against websites and apps

There are three typical patterns:

  • Health and wellness apps. An SDK sends what users enter (cycle dates, symptoms, goals) to an ad platform. Frasco v. Flo Health is the leading example. The class certification order describes Google and Meta SDKs in the Flo app collecting "Custom Events" named for what users entered (order, Dkt. 605, 19 May 2025).
  • Patient portals and health sites. Analytics code sends page and form data from a provider's website to a vendor (Doe v. Adobe, about Kaiser's site).
  • Chat, calls and AI notetakers. A vendor records the conversation and keeps it for its own use (In re Otter.ai).

Plaintiffs plead §632 alongside §631 because it avoids the "in transit" fight. Defendants answer that the communication was not confidential, that nobody intended to record a confidential exchange, or that the user consented.

How courts have ruled

CaseCourtDateHolding
Smith v. LoanMeCal. Supreme Court1 April 2021§632.7 applies to parties as well as outsiders (a phone call case)
Doe v. AdobeLA Superior, Dept 1118 March 2024Tentative: demurrer to §632 overruled for analytics on Kaiser's patient website; intent inferred from alleged transmission to Adobe servers; §631 sustained with leave (ruling). Later tentatives of 19 September 2024 and 23 March 2026 were not reviewed
Heiting v. HarperCollinsLA Superior, Dept 915 May 2025Class certification denied in a website chat case; the named plaintiff, a self-described tester, had tested 27 sites that day. The §632.7 count had been dismissed without leave in July 2024 (ruling)
Frasco v. Flo HealthN.D. Cal.1 August 2025Jury verdict against Meta under §632 after Flo, Google and Flurry settled: the jury found Meta intentionally eavesdropped on or recorded the conversation using an electronic device, users had a reasonable expectation it was not being recorded, and there was no consent (verdict form, Dkt. 756). Post-trial motions denied 17 September 2025 (Dkt. 776)
In re Otter.aiN.D. Cal.13 August 2026A plaintiff who spoke "with a medical professional" pleaded a confidential communication; "private" or "sensitive" without detail was not enough (order, p. 17)

What divides the cases. Courts look at the subject matter and setting. A medical conversation or a health-app entry can be confidential. A general website visit or a retail chat rarely is, because users can expect the business to keep records. Section 632.7 claims over website chat depend on the visitor using a mobile phone and on treating a web server as the other device. In HarperCollins the §632.7 count did not survive demurrer. Federal rulings on §632.7 chat claims are not uniform, and we have not reviewed them in full.

Status and what is changing

Status, 17 October 2026: in force, unchanged. The Senate version of SB 690 (29 May 2025) would have exempted any "commercial business purpose" from §632 and §632.7. The Assembly removed that in July 2026, and the enacted text amends only §637.2 for §638.51 claims (bill history).

In Frasco, no judgment against Meta has been entered. The court held that §637.2's USD 5,000 per violation is fixed by statute (Dkt. 776, p. 22). Plaintiffs seek a partial judgment of USD 1,110,575,000 for 222,115 class members they can name, at USD 5,000 each. Meta opposes, and the motion is set for hearing on 29 October 2026 (motion, Dkt. 846, pp. 1, 4; opposition, Dkt. 851). Nothing has been awarded. The settlement amounts are on the Flo, Google and Flurry case page. Expect §632 to be pleaded more often against AI chat and notetaker tools, following Otter.ai.

What this means for your implementation

The question for engineers is where users tell you something they would expect to stay between you and them. Treat those surfaces separately:

  • symptom checkers;
  • intake forms;
  • therapy or support chat;
  • AI assistants;
  • recorded calls.

On those surfaces:

  • Keep third-party SDKs and analytics off, or limit them to non-content events with no free text.
  • Show recording notice before a chat or call starts, not in a footer.
  • Check whether chat, transcription or AI vendors may keep or train on transcripts, and turn that off where you can.
  • Give events neutral names. In Frasco, custom event names described what the user had entered.

How Inth catches this

  • Code audit: flags a pull request that adds an analytics or ad SDK, chat widget or transcription vendor to an intake, health or support flow, and traces form fields and event names to the vendor.
  • Website audit: records which vendor domains receive requests from chat and form pages, and whether they fire before the visitor chose.
  • Consent banner: under an opt-in policy, chat (for example Intercom or Crisp) and analytics wait for consent. Inth's default California policy is opt-out, so configure a California opt-in policy for these surfaces if recording claims are a concern.
  • Evidence: consent records and runtime observations with page, time and consent state.

Inth cannot see in-app SDK traffic that never passes through a web page, or what a vendor does with a transcript after receipt.

Sources and limits

Source review: 17 October 2026. This page summarises the statutes and the cited rulings at their procedural stage. A jury verdict is not a final judgment until entered, and may be appealed. It is not legal advice. Inth wrote the technical checks; they cannot decide which laws apply or prove compliance.