CIPA § 631 Explained: California Wiretap Law and Website Tracking

    Updated 2026-11-13 · 2 cases cited · 5 outbound resources

    CIPA § 631 is California’s wiretapping law. In website cases, plaintiffs may allege that a pixel, session-replay tool, or chat vendor reads visitor communications in transit without all parties’ consent, or that the site operator assists prohibited conduct. This guide explains the statute, consent timing, civil remedies, and what website teams should review. A pixel’s presence alone does not establish liability; the actual data flow, consent sequence, and facts still matter.

    TL;DR

    • —Read the statutory elements rather than equating every third-party request with a wiretap.
    • —Javier is an unpublished consent-timing memorandum, not a controlling ruling that every analytics pixel violates CIPA.
    • —§ 637.2 provides civil remedies for an established violation; tracker totals are not automatic damages calculations.
    • —Shopify teams should review consent through search, cart, and hosted checkout, not only the homepage.

    Got a demand letter? Start by checking your Shopify or ecommerce page after Reject All. For checkout testing and help fixing consent and pixel issues, explore got pixels?.

    What § 631 actually addresses

    Section 631’s text addresses wire/line tapping or unauthorized connection; reading or attempting to read message contents while in transit without all parties’ consent; and using information so obtained or assisting prohibited conduct. Website complaints often focus on reading communications in transit and assistance by the operator. These are legal allegations that require evidence, not classifications derived from a tracker name.

    Contents, timing, and the parties’ roles

    Review the destination, payload, triggering action, and timing of a challenged request. A script download is not the same as sending a search term or form value. Whether a recipient is a party, an independent interceptor, or a service provider depends on facts and applicable authority. In re Facebook rejected a party argument for the challenged logged-out tracking and reversed dismissal of certain claims; it did not resolve all website tracking.

    Javier reversed dismissal based on retroactive consent in a session-replay dispute. It left prior implied consent and other issues unresolved. The memorandum expressly is not precedent except as Ninth Circuit rules allow; do not treat it as a universal opt-in requirement for every request.

    Civil remedies are not a tracker-count calculator

    Section 637.2 provides the greater of $5,000 or three times actual damages for an established violation and says actual damages are not required to bring an action. It does not establish that each request, page view, or visitor is a separately recoverable violation. Liability, standing, counting, defenses, and any limitation period need legal assessment.

    The chaptered text of SB 690, approved September 30, 2026, changes civil enforcement of specified § 638.51 website/app claims from January 1, 2027 and includes a pending-claim provision. It does not eliminate § 631 claims or exempt all website tracking. Read our SB 690 guide for its scope, timing, and leading sources; counsel should assess application to your facts.

    Got a demand letter? Start by checking your Shopify or ecommerce page after Reject All. For checkout testing and help fixing consent and pixel issues, explore got pixels?.

    Shopify example: rejection followed by checkout

    Our Shopify checkout and CIPA guide links to a captured journey where Meta requests disappeared after rejection and reload, then returned in a later shopping/checkout segment. The report does not establish the precise consent-setting cause or a violation. Its value is showing why homepage behavior alone cannot describe the whole purchase journey.

    A practical website-team review

    Inventory actual recipients and transmitted fields; preserve the banner wording and consent sequence; test whether the approved choice reaches each integration; and distinguish cookie storage from network transmission. Google Consent Mode, a vendor contract, or server-side tagging is not a legal safe harbor. Keep CCPA sale/sharing opt-outs and GPC separate from CIPA consent questions.

    Use the California Invasion of Privacy Act compliance guide for the review workflow and pixel litigation guide for broader claims. The free scan screens the submitted page after rejection. got pixels? supports deeper checkout, chatbot, and form journeys. Neither certifies legal compliance.

    Key cases

    Javier v. Assurance IQ, LLC

    No. 21-16351 (9th Cir. May 31, 2022) (unpublished)

    Reversed dismissal based on retroactive consent in a session-replay case. The memorandum interpreted § 631 to require prior consent, left prior implied consent and other issues unresolved, and is not precedent except as Ninth Circuit Rule 36-3 allows.

    Read source

    In re Facebook, Inc. Internet Tracking Litigation

    956 F.3d 589 (9th Cir. 2020)

    Reversed dismissal of several claims involving tracking of logged-out users on third-party sites and remanded. Rejected Facebook’s party-to-the-communication argument for the challenged collection; did not determine that every pixel or third-party request violates CIPA.

    Read source

    FAQ

    Is a cookie banner enough for § 631 review?

    No. Review what the visitor is told, when collection occurs, what choice was made, and whether that choice controls the relevant integration. Have counsel assess statutory elements and defenses.

    Does CIPA matter to an out-of-state Shopify merchant?

    Potentially. Location, jurisdiction, alleged conduct, and the visitor’s circumstances matter. Briskin addressed jurisdiction on pleaded checkout facts, not automatic liability for every out-of-state merchant.

    Does Reject All prove a later request is illegal?

    No. It records a choice that matters to the review, but the request’s contents, purpose, recipient, timing, and applicable law still need assessment.

    Can we calculate exposure as $5,000 times tracker hits?

    No. A technical request total does not establish the number of legally recoverable violations.

    Further reading

    Related reading

    Understand the tracking behind your demand letter

    Start with a free Reject All scan of your Shopify or ecommerce page. Enter your email to unlock detailed findings and reports for your team and lawyer. got pixels? goes deeper into checkout and other journeys, helps with remediation, and lets you retest changes. A scan cannot confirm or dismiss a legal claim.

    This article is general information about California Invasion of Privacy Act litigation, not legal advice. Case citations are drawn from public dockets and law-firm commentaries; verify before relying on them. Consult qualified counsel for advice on your specific situation.