Wiretap Risk for Product Builders: What to Check Before You Ship (Especially With Vibe Coding)

    Updated 2026-11-16 · 2 cases cited · 7 outbound resources

    AI coding tools make it easy to ship a chatbot, analytics, session replay, or an AI assistant in an afternoon. They also make it easy to send what your users type to a third party before anyone decided that was acceptable. California’s Invasion of Privacy Act (CIPA) and other wiretap laws are now regularly raised against exactly these features. This guide covers what to take into account while building. It reflects sources checked November 16, 2026 and is general information, not legal advice.

    TL;DR

    • —Wiretap claims usually focus on communication contents (messages, search terms, form inputs, chat text) reaching a third party while in transit, without the consent the law requires.
    • —Vibe-coded apps often add tracking scripts, chat widgets, replay tools, and AI APIs by default. Every one of them is a recipient you chose, even if a prompt chose it for you.
    • —Consent timing matters: scripts that load before a user agrees, or keep running after Reject All, are a common factual theme in these lawsuits.
    • —Keep an inventory of what data each feature sends where, test it with real browser traffic, and review it with counsel before launch, not after a demand letter.

    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?.

    Why product builders should care about wiretap law

    Wiretap statutes were written for phones, but plaintiffs apply them to websites and apps. CIPA § 631 addresses reading or learning the contents of a communication in transit without consent of all parties, and aiding someone who does. § 632 addresses recording confidential communications. § 637.2 provides a civil remedy of the greater of $5,000 per violation or three times actual damages. The federal Wiretap Act is generally a one-party consent statute but has its own exceptions and limits.

    The common pattern in website cases: a visitor communicates with your product (types a message, searches, fills a form), and a third-party script or service receives that content at the same time. Plaintiffs argue the third party was an eavesdropper and the site owner helped. Defendants respond with consent, party-to-the-communication, and other defenses. Courts have reached different results depending on the facts. See our § 631 guide for how those arguments play out.

    This is why architecture choices matter. Whether a vendor only stores data for you, or can use it for its own purposes, is a recurring fact in these disputes. That is a product decision as much as a legal one.

    What changes with vibe coding

    When you ask an AI tool to “add analytics,” “add a support chat,” or “track conversions,” it usually picks a popular vendor and pastes its snippet into your page head, where it loads for every visitor before any consent step. It rarely asks what the vendor collects, whether it records inputs, or what your consent banner should block.

    Typical defaults to watch for: a pixel or tag manager in the root layout, session replay with input capture left on, a chat widget whose transcripts go to the vendor, form libraries that post to a third-party endpoint, and AI features that forward full user messages to a model provider with logging on. None of these is automatically unlawful. Each is a data flow someone should consciously approve.

    Generated code also tends to be copied forward. A tracking call added to one page can end up in shared components, checkout flows, or account pages where users type more sensitive information. Review the generated diff for new third-party domains, not just whether the feature works.

    Features that most often raise wiretap questions

    Chatbots and live chat: transcripts are communications by definition. If a vendor receives them and may use them for its own purposes, that is the core theory in chatbot wiretapping suits. Disclose the vendor clearly before the first message and check the vendor’s data-use terms.

    Session replay: tools that record keystrokes, clicks, and form fields can capture what users type in real time. Mask inputs by default and avoid loading replay before consent. See session replay lawsuits.

    Pixels and analytics: event payloads can include URLs, search terms, button text, and form values. Advertising pixels are the basis of most pixel litigation. Strip query strings and inputs you do not need, and gate ad pixels on consent.

    Identifiers and fingerprinting: tools that collect device, IP, or routing information have been challenged under CIPA’s pen-register provision, § 638.51. California’s SB 690 narrows private enforcement of some of those claims starting January 1, 2027, but does not touch § 631. See our SB 690 guide.

    AI features: sending user prompts to a model provider is a third-party transmission. Know whether the provider retains or trains on that data, tell users, and avoid forwarding more context than the feature needs.

    A builder’s checklist before shipping

    1. Map the data flows. For every feature, list what the user sends, which domains receive it, and whether the recipient can use it for itself. Open the browser network tab and look at real requests, not the vendor’s marketing page.

    2. Load third parties after consent, not before. Put non-essential scripts behind your consent manager, and confirm that Reject All actually stops them, including after page reloads and on later steps like checkout. Honor Global Privacy Control signals where required; see the California Privacy Protection Agency FAQ.

    3. Minimize what you send. Mask form inputs in replay, drop search terms and query parameters from analytics events, and avoid forwarding full chat transcripts unless you need to.

    4. Prefer first-party or processor-style setups. Self-hosted analytics or vendors contractually limited to processing for you change the facts courts look at. They do not guarantee an outcome.

    5. Disclose at the point of collection. Tell users before they type into a chat or form that a named vendor receives the content. Consent obtained after the interception is a weak position; see Javier v. Assurance IQ.

    6. Write it into your prompts and reviews. Ask your AI tool to load third-party scripts only after consent and to list every new external domain it adds. Treat a new vendor domain in a diff like a new dependency that needs review.

    7. Retest after every release. Tag managers, app installs, and generated refactors change what fires. A check that passed last month says nothing about today’s build.

    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 this guide does not tell you

    Wiretap liability is fact-specific. Whether a vendor is a third party or an extension of your business, whether data is “contents,” whether consent was valid, and which state’s law applies are questions for counsel. Courts have ruled both ways on similar technology, and the law keeps moving.

    Wiretap law is also only one piece. Consumer privacy laws like the CCPA, sector rules, and general security expectations (see the FTC’s Start with Security guidance) apply separately. Our CIPA compliance guide covers how website teams organize a broader review.

    Test what your product actually sends

    The free got cipa? scan loads a page you submit from California, clicks Reject All, and shows which trackers still fire. It is a quick screen of one page, not a legal opinion or a full product review. Test only sites you are authorized to audit.

    got pixels? is the full product for deeper testing: chatbot conversations, add to cart and checkout, and contact forms, with and without consent, plus help fixing and retesting what it finds.

    Key cases

    In re Facebook, Inc. Internet Tracking Litigation

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

    Reversed dismissal of wiretap and privacy claims over logged-out tracking and rejected a party-to-the-communication defense for the challenged collection. Fact-specific; it did not declare all tracking unlawful.

    Read source

    Javier v. Assurance IQ, LLC

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

    Held that consent obtained after session-replay recording began did not retroactively cover the earlier recording under § 631. Unpublished and not generally binding precedent.

    Read source

    FAQ

    Is using analytics or a chatbot illegal under CIPA?

    Not automatically. Claims depend on what content is sent, to whom, when, what users agreed to, and available defenses. The point is to know and control those flows.

    Does the AI tool that wrote my code share responsibility?

    Assume not. The site or app operator chooses what ships and is the usual defendant. Review generated code for third-party data flows.

    Does a cookie banner solve this?

    Only if it actually blocks scripts until consent and stops them after rejection. Test real network traffic rather than relying on the banner’s appearance.

    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.