Munoz v. LG Electronics: the lawsuit built on a half-second consent flip
Most session-replay lawsuits allege that a recording script ran without consent. Munoz v. LG Electronics goes one step further and more damning: it alleges the site had a consent mechanism, the plaintiff used it to say no — and then, according to the complaint, a tracking integration flipped the consent flag from "false" back to "true" in about half a second, and the recording continued anyway.
That detail matters because it turns an abstract wiretap claim into something concrete and timestamped. If a visitor's opt-out is recorded, and a machine-readable log shows that opt-out being silently reversed moments later, the plaintiff isn't just asserting that tracking happened — they're pointing to a "consent artifact," a piece of evidence that the "no" was overridden. Filed in October 2026 under California's wiretap statute, this case is a preview of where session-replay litigation is heading: from "did it record?" to "did your own logs prove you ignored the opt-out?"
Case snapshot
- Case name
- Munoz v. LG Electronics
- Case number
- No. 2:26-cv-12759
- Court
- U.S. District Court, Central District of California
- Status
- Active litigation — newly filed (October 2026); allegations unproven
- Statute
- California Invasion of Privacy Act — CIPA §631(a) (wiretapping)
- Technology
- FullStory session-replay; iAdvize integration alleged to have reset a consent flag
- Core allegation
- Session-replay tracking allegedly continued after the plaintiff invoked "Do Not Sell or Share," with a consent flag flipped false→true in ~0.5 seconds
- Damages sought
- CIPA statutory damages ($5,000 per violation under Cal. Penal Code §637.2) and related relief
- Key date
- Filed October 2026
What the case is about
The complaint concerns LG Electronics' consumer website and the tracking technologies running on it. At the center is session-replay software — in this case, FullStory — which records what a visitor does on a page: clicks, scrolling, mouse movement, and, critically, what they type into forms. The recording can be played back later like a video of the visit.
The plaintiff, Munoz, alleges that this recording happened without valid consent — and, in the detail that distinguishes this case, that it continued after an opt-out. According to the complaint, the plaintiff invoked a "Do Not Sell or Share My Personal Information" choice, which should have stopped non-essential tracking. But the complaint alleges that a separate integration on the site — associated with iAdvize, a customer-engagement/chat vendor — reset a consent flag from "false" to "true" within roughly half a second, effectively re-enabling the tracking the opt-out was supposed to disable.
The legal theory is California's wiretap statute, CIPA §631(a): that capturing the plaintiff's interactions and inputs in real time, and routing them to a third-party recorder without consent, is an unlawful interception of the contents of a communication. LG has not yet responded to the complaint, and the allegations are unproven. But the fact pattern — opt-out invoked, consent silently reversed, recording continued — is exactly the kind a court and a jury find compelling, because it isn't about whether a banner existed; it's about whether the site honored the answer.
Why the half-second matters: a consent flag flipping from false to true in ~0.5 seconds isn't something a human does — it's an automated integration overriding a user's choice faster than the user could perceive. If the complaint's allegation holds up, it's close to a perfect piece of evidence: a timestamped, machine-generated record that the opt-out was registered and then reversed. That's the "consent artifact" that turns a hard-to-prove wiretap claim into a documented one.
How session replay works — and why it's a wiretap theory
To understand the claim, you have to understand what session-replay software actually does. It's a JavaScript snippet embedded in a page that captures DOM changes and user interactions as they happen — clicks, mouse movements, scrolling, and keystrokes. Because it records form fields as the visitor types, it can capture names, addresses, email addresses, payment details, and search terms. The session is reconstructed and can be replayed like a video.
Plaintiffs characterize this as an interception of the "contents" of a communication "in transit" under CIPA §631. The theory: the visitor's inputs and actions are the communication, and the replay script captures them while they're being sent — not after they're stored. That "in transit" framing is what brings the conduct within a wiretap statute written decades before session replay existed.
The vendor angle sharpens it. In the plaintiffs' framing, the replay vendor is cast as a third-party eavesdropper and the website as its accomplice. What moves a tool "from tape recorder to eavesdropper in court" is vendor data use — if the vendor processes or benefits from the recordings, it looks less like a passive tool and more like a party listening in. We cover the mechanics and the leading cases in our deep dives on session replay and CIPA (Hotjar, Clarity, FullStory) and specifically FullStory and CIPA.
The $5,000 engine: CIPA carries statutory damages of $5,000 per violation, with no proof of actual harm required. For a session-replay class spanning thousands or millions of visits, that per-violation figure is what makes the theory so potent — and why even a newly filed case commands attention. The math is the leverage.
Is session-replay software recording on your site before consent? Most teams can't say for sure — the script is invisible to a casual look. ConsentPixel's free scanner shows exactly what fires before a visitor consents, and whether an opt-out actually stops it.
Run a free privacy scan →The "consent artifact": the evidence that changes the game
What makes Munoz worth studying isn't that session replay ran — it's how the complaint alleges the opt-out was defeated. This is the emergence of what we'd call the consent-artifact fact pattern, and it's a meaningful escalation in session-replay litigation.
In the typical case, a plaintiff has to establish that tracking occurred without consent — which can turn into a technical argument about banners, implied consent, and what the visitor "should have known." The consent-artifact pattern short-circuits that. If the site's own technology generated a machine-readable log showing a consent signal set to "false" (opt-out) and then changed to "true" (tracking enabled) milliseconds later, the plaintiff isn't arguing about what the visitor understood. They're pointing at the defendant's own records and saying: your system registered the "no," and then your system reversed it.
That shift — from disputed inference to documented reversal — is why this detail is the heart of the case. It's also a warning about how these integrations fail. The alleged culprit here isn't the session-replay script acting alone; it's a second integration (iAdvize) interfering with the consent state, re-enabling tracking the opt-out should have stopped. That's a configuration failure, not a deliberate policy — which is exactly what makes it so common and so dangerous.
How a consent flag gets silently flipped
The mechanism the complaint describes is mundane, which is the scary part. On a modern site, consent state is often a shared value that multiple tags and integrations read and write. When several vendors each manage their own consent logic, they can step on each other:
- A consent-management platform sets the flag to "false" when the user opts out.
- A separate vendor integration — loaded independently, with its own defaults — initializes and writes "true," not knowing (or not respecting) the opt-out that just happened.
- The race between them resolves in milliseconds, and the last writer wins. If the vendor's "true" lands after the opt-out's "false," tracking proceeds.
No one intended to override the user. But intent isn't the question under a statute with per-violation statutory damages — the question is whether the tracking happened without consent, and the consent artifact answers it.
Why session replay is the strongest wiretap target of all
Not all trackers are equal in the eyes of a wiretap statute. CIPA §631 turns on intercepting the contents of a communication — and session replay captures more "contents" than almost anything else on a page. That's worth spelling out, because it's why replay cases are harder for defendants to shrug off than ordinary analytics suits.
| Technology | What it captures | Strength as a "contents" claim |
|---|---|---|
| Basic analytics tag | Page views, referrers, aggregate events | Weaker — often metadata, not message contents |
| Advertising pixel | Identifiers, page URLs, some event data | Moderate — depends on what rides along |
| Session replay | Clicks, scrolling, mouse movement, and keystrokes / form inputs as typed | Strongest — the actual words and inputs a user enters are hard to call anything but "contents" |
When a plaintiff can allege that a script recorded what they typed — a name, an address, a search for a product, a message in a chat box — the "that's just metadata" defense collapses. Those keystrokes are the content of the communication by any plain reading. That's why session replay, more than any pixel, sits at the sharp end of the §631 theory, and why a replay case paired with a consent artifact is a particularly uncomfortable combination for a defendant.
The compounding factor: replay doesn't just capture more — it captures it in a form that's easy to show a jury. A reconstructed "video" of a user typing their details into a form, recorded despite an opt-out, is visceral in a way a log of cookie IDs never is. The evidentiary power of the medium is part of what makes these cases settle.
Why this case matters beyond LG
- It raises the evidentiary stakes for everyone. If plaintiffs can point to consent artifacts — logs showing an opt-out reversed — the "did they consent?" question gets much easier to prove. Every site with multiple consent-writing integrations is exposed to this.
- The failure is a configuration problem, not a policy one. LG presumably intended its opt-out to work. The alleged flaw is that a second integration quietly undid it. That can happen to any site that bolts on vendors without testing how they interact.
- Session replay remains a prime target. Because it captures keystrokes and form inputs, replay is the richest, most sensitive thing a tag can record — and the most clearly "contents of a communication" for a wiretap claim.
- "Do Not Sell or Share" is a tested promise. The opt-out link isn't decorative. When a plaintiff uses it and the tracking continues, the gap between the promise and the behavior is the case.
- It's a template others will copy. A newly filed case with a clean, technical fact pattern tends to get replicated. Expect more "consent artifact" complaints as plaintiffs' firms learn to look for the flipped flag.
How to find out if your site has this problem
The unnerving thing about the Munoz fact pattern is that you can't see it by looking at your banner — it lives in the interaction between integrations, in the milliseconds after an opt-out. But you can test for it directly.
- Opt out, then watch. Load your site in a fresh browser, invoke your "Do Not Sell or Share" or reject option, and then watch the Network tab. If session-replay or tracking requests keep firing after the opt-out, you have the core problem.
- Inspect the consent state over time. Using developer tools, watch the consent flag or signal your CMP sets. Does any other script write to it after the opt-out? A value that changes from opt-out back to opt-in is the consent-artifact pattern on your own site.
- Enumerate who writes consent. List every integration that reads or writes consent state — the CMP, chat/engagement tools (like iAdvize), analytics, replay. The more writers, the higher the risk one overrides another.
- Test integrations in combination, not isolation. A vendor that behaves in a demo can misbehave alongside your other tags. The failure is in the interaction, so test the real, combined stack.
- Confirm replay is consent-gated. The single most protective step: ensure the session-replay script never initializes for a visitor who hasn't consented, and genuinely stops for one who opts out. (More in how to audit website trackers.)
See whether your opt-out actually stops session replay. ConsentPixel loads your site, invokes the opt-out, and shows you whether tracking really stops — the exact test behind the Munoz fact pattern. Catch a flipped consent flag before a plaintiff does.
Scan your site free →The fix: make consent authoritative, not advisory
The root problem the Munoz complaint describes is that consent was advisory — a value integrations could read, ignore, or overwrite — rather than authoritative, a gate that actually prevents tracking from firing. The defensible architecture inverts that.
- Gate at the source, not the signal. Non-essential scripts, including session replay, should not load or initialize at all until consent is given. A tag that never loads can't be re-enabled by another integration flipping a flag.
- Give consent a single source of truth. One authoritative consent state, which all integrations must honor, beats several vendors each keeping their own. Reduce the number of things that can write "true."
- Make opt-out terminal. When a user opts out, the result should be that the relevant scripts stop and cannot be restarted within the session by another tag. Verify this, don't assume it.
- Monitor the consent state for reversals. Build or buy monitoring that flags when a consent signal is changed after an opt-out — the consent artifact is your evidence too, and you want to catch it before a plaintiff does.
- Re-test after every integration change. A new chat widget or analytics tag can reintroduce the race condition. The combined stack is what matters, and it changes over time.
Consent as code: the mental shift the case demands
The deepest lesson of Munoz isn't about any one vendor — it's about how teams think about consent. Most organizations treat consent as a UI problem: get the banner right, log the choice, show the opt-out link. The case exposes that as insufficient. Consent is really a systems problem, and it has to be enforced in code, not just presented in an interface.
Here's the distinction that matters. In a UI-centric model, consent is a record — a note that says "this user chose X." Integrations are trusted to read that note and behave. In a code-centric model, consent is a control — the thing that actually determines whether a script can run at all. The difference is the difference between asking your tags to behave and preventing them from misbehaving.
| Consent as a record (fragile) | Consent as a control (robust) |
|---|---|
| A flag tags are expected to read and respect | A gate that physically prevents non-consented scripts from loading |
| Any integration can read, ignore, or overwrite it | One authoritative source of truth that scripts can't override |
| Opt-out is a value; enforcement is hoped for | Opt-out is terminal; the script stops and can't restart in-session |
| Failures are invisible until a plaintiff finds them | Reversals are monitored and alerted on |
The Munoz complaint describes a failure of the left column: a consent value that a second integration could — and allegedly did — overwrite. The defensible posture is the right column, where the opt-out isn't a request the tags might honor but a gate they physically cannot get past. When consent is enforced as code, there's no flag to flip, because the script that would have been re-enabled never loaded in the first place.
Key takeaways
What Munoz v. LG Electronics tells you
- The opt-out is the case. The complaint alleges tracking continued after a "Do Not Sell or Share" choice, with a consent flag flipped false→true in ~0.5 seconds — a documented reversal, not just alleged tracking.
- Session replay is the technology. FullStory-style replay captures keystrokes and form inputs, which plaintiffs frame as the "contents" of a communication intercepted in transit under CIPA §631.
- The "consent artifact" raises the stakes. A machine-readable log of an opt-out being reversed turns a hard-to-prove wiretap claim into a documented one.
- It's a configuration failure. A second integration (iAdvize) allegedly overrode the consent state — the kind of race condition any multi-vendor site can have without intending to.
- Make consent authoritative. Gate scripts at the source so they never load before consent, give consent a single source of truth, and make opt-out terminal.
Frequently asked questions
What does Munoz v. LG Electronics allege?
What is a "consent artifact," and why does it matter?
How does session-replay software trigger a wiretap claim?
How can a consent flag get flipped without anyone intending it?
How do I check whether my site has this problem?
What's the fix?
The bottom line
Munoz v. LG Electronics is a newly filed case, and its allegations are unproven — but the fact pattern it describes is a signal every site owner should read. Session-replay wiretap claims have been building for years; what's new here is the consent artifact: the allegation that the site's own technology recorded an opt-out and then reversed it in half a second. That moves the fight from "did you track me?" to "your logs show you ignored my 'no'" — a far harder thing to defend.
The lesson is architectural. If consent on your site is a value that vendors can read, ignore, and overwrite, you have the same exposure, whether or not you know it. Make consent a gate that actually prevents tracking from loading, give it a single source of truth, make opt-out terminal, and watch for reversals. Do that, and there's no flipped flag for a plaintiff to find — because the "no" actually held.
Make sure your "no" actually holds. Run a free ConsentPixel scan to see whether your opt-out stops tracking — and catch a flipped consent flag before it becomes a complaint. Then try the full platform free for 14 days, no credit card required, to gate every script behind real consent.
Get your free privacy scan →Sources
- Court record — Munoz v. LG Electronics, No. 2:26-cv-12759, U.S. District Court, Central District of California (filed October 2026). Allegations unproven; case-specific details reflect the complaint as reported in case-tracking sources and may be refined as the docket develops.
- pii.ai — "Session Replay" (CIPA & wiretap litigation glossary): technical mechanism of session replay and the §631 "contents in transit" theory; vendor-as-eavesdropper framing; $5,000-per-violation damages.
- Morrison & Foerster — "Privacy Litigation Year in Review: Web Analytics 'Session Replay' Wiretap Litigation."
- ConsentPixel — session replay and CIPA, FullStory and CIPA, and how to audit website trackers.
- Statute — California Invasion of Privacy Act, Cal. Penal Code §631(a) and §637.2.