The Real Reason a 1988 VHS Law Is Wrecking Modern Websites

The Real Reason a 1988 VHS Law Is Wrecking Modern Websites

The Supreme Court is weighing whether a 1988 video rental law turns everyday website visitors who sign up for a newsletter into protected "consumers" when tracking pixels log the videos they watch. In Salazar v. Paramount Global, argued on October 14, 2026, the justices are deciding who counts as a consumer under the Video Privacy Protection Act (VPPA) and how far a statute built for neighborhood videotape shops stretches across modern media and ad tech.

At stake is a wave of class-action lawsuits carrying $2,500 per violation in statutory liquidated damages. One misplaced line of analytics code on a site with embedded video clips can turn routine traffic into multi-million-dollar exposure.

How a Confirmation Fight Became a Digital Shakedown

History has a wry habit of recycling old scandals into new compliance nightmares. In 1987, during Supreme Court nominee Robert Bork's confirmation battle, a reporter obtained and published a list of videotapes Bork had rented from a local shop. Congress reacted swiftly by passing the VPPA in 1988 so clerks could not casually leak what people watched.

Back then, privacy had a physical bottleneck. A clerk had to pull a paper card or check a terminal inside a brick-and-mortar store to hand over your rental history.

Today, the bottleneck is invisible. A publisher embeds a short video player on a sports page, a news article, or a product walkthrough. A third-party tracking pixel—a snippet of code often tied to an advertising network—fires in the user's browser. If the visitor is simultaneously logged into an external platform or passes an identifiable token, plaintiff lawyers argue the site knowingly disclosed personally identifiable information (PII) linking a real person to specific video content without proper consent.

Congress wrote the VPPA to stop physical clerks from gossiping about VHS rentals, yet plaintiff attorneys now wield its $2,500 statutory floor against automated browser scripts.

Even Congress's 2012 update—which modernized the statute to allow electronic consent—left the core definition of a "consumer" untouched. That statutory freeze is why courts are tearing their hair out. When lawmakers draft around the technology of one era and leave the definitions frozen across three more, judges end up playing linguistic archaeologists with words like "subscriber," "goods or services," and "video tape service provider".

Why the Circuit Split Exists Over a Newsletter

The fight in Salazar v. Paramount Global hinges on a deceptively narrow question of statutory text. The VPPA defines a consumer as any renter, purchaser, or subscriber of "goods or services from a video tape service provider".

In the underlying dispute, Michael Salazar signed up for an online newsletter on Paramount's 247Sports site and watched videos while logged into Facebook, alleging that tracking code sent his identifier and viewing activity to Facebook without consent. Was signing up for a text newsletter enough to make him a protected consumer?

Federal appeals courts have split sharply on that exact question:

  • Broad reading (Second and Seventh Circuits): Courts in these circuits have read "goods or services" more expansively, allowing claims to proceed where a plaintiff subscribed to a broader digital offering—such as a free newsletter—even if that specific subscription was not a paid or dedicated video streaming plan.
  • Narrow audiovisual reading (Sixth and D.C. Circuits): Courts on the other side have tied the definition of "consumer" more closely to the video-service context of the statute, holding that subscribing to non-video goods or newsletters does not automatically convert a reader into a VPPA video consumer.

The practical absurdity is hard to miss. Two publishers can run nearly identical video players and analytics tags, yet face radically different legal risk depending on where the lawsuit lands and which circuit precedent governs.

Legal Question Narrow Reading View Broad Reading View Operational Impact on Publishers
Who counts as a "subscriber"? Someone tied to video or audiovisual offerings Anyone subscribing to covered goods or services, including newsletters Newsletter sign-ups become high-stakes triggers if video pixels fire
What triggers liability? Disclosure linked to an audiovisual consumer relationship Knowingly sharing PII tied to specific video requests without consent Ad pixels and SDKs require strict auditing on video pages
Financial stakes per claimant Often dismissed early if no video subscription exists Survives pleading stage; faces $2,500 statutory minimum per violation Class actions settle in the millions even without proven out-of-pocket harm

The Overlooked Reality of Ad Tech and Consent

Coverage of VPPA litigation often treats websites as either innocent storytellers or mustache-twirling data brokers. Reality in digital media operations is much messier.

Most publishers do not hand-craft tracking pixels from scratch. They drop in tag managers, content management plugins, embedded players, and marketing automation scripts built by third parties. A marketing team might add a conversion pixel to measure newsletter sign-ups or ad attribution, unaware that a neighboring script on the same template captures video URLs or user identifiers.

Meanwhile, consent mechanics are a legal minefield. Some courts have scrutinized whether standard privacy policies or buried terms of use satisfy the VPPA's specific consent requirements, while other rulings—such as Lakes v. Ubisoft in federal court in California in April 2025—have found layered disclosures and consent flows sufficient to dismiss claims early. Even when a company believes its cookie banner is compliant, plaintiff lawyers test whether the notice explicitly covers video-viewing disclosures rather than generic analytics.

Consider a hypothetical example to see how easily a routine workflow goes sideways. Suppose a mid-sized regional news site runs a free morning briefing newsletter and embeds two-minute local news clips inside articles. A developer adds an analytics tag to measure how newsletter readers engage with video stories. If that tag transmits a persistent user ID alongside the video identifier before clear, specific consent is recorded, the newsroom has created the exact fact pattern plaintiffs love to plead.

There is also a counter-argument worth taking seriously. Consumer privacy advocates argue that strict enforcement forces companies to stop surreptitious cross-site tracking when people watch media online. If a website wants to use third-party trackers on video pages, asking clearly or stripping identifying tokens is entirely doable. Calling a rule "outdated" does not automatically mean the underlying privacy harm is imaginary.

Yet the blunt instrument of $2,500 statutory damages creates severe distortion. A technical misconfiguration affecting tens of thousands of visitors generates theoretical statutory exposure in the tens or hundreds of millions of dollars, even where no viewer suffered financial loss or public humiliation like Robert Bork did in 1987. That asymmetry is why defense lawyers call it asymmetric leverage and plaintiffs' lawyers call it deterrence.

What Supreme Court Clarification Will and Won't Fix

A ruling in Salazar v. Paramount Global—expected after the October 2026 argument—will likely resolve the circuit split on whether subscribing to non-video offerings like a newsletter makes someone a VPPA consumer. Even if the justices lean toward allowing suits to move forward, as observers noted during oral argument, the opinion will still leave other fights standing.

Courts still wrestle over what counts as "personally identifiable information" in digital environments and when a company "knowingly" discloses it. Different appeals courts have applied different standards—including tests looking at what a reasonable provider would foresee a recipient understanding—and petitions like Golden v. NBCUniversal have kept those adjacent questions in front of the Court.

State privacy laws add another layer of friction. Lawmakers across states have continued amending and enacting privacy statutes and remedies—such as California's amendments to Penal Code section 637.2 taking effect January 1, 2027—meaning companies cannot treat federal VPPA rulings as a silver bullet that erases state-level wiretap or privacy exposure.

Nor is a Supreme Court ruling a substitute for engineering hygiene. Courts interpret statutory text; they do not clean up stray pixels inside a website's tag container.

Concrete Steps for Digital Teams Right Now

Waiting for a Supreme Court opinion before inspecting how your site handles video and tracking scripts is a gamble with poor odds. Legal teams and product engineers can reduce exposure immediately with disciplined operational checks:

  1. Map every video surface and third-party tag: Inventory every page or app screen that hosts or embeds video, and list every pixel, SDK, and analytics script firing on those routes.
  2. Trace outbound data payloads: Verify whether any tag sends user identifiers, account tokens, or hashed emails together with video titles, IDs, or watch events to external parties.
  3. Separate newsletter and account flows from unconsented video tracking: Audit what happens when someone subscribes to a newsletter or logs in and then views video content on the same property.
  4. Tighten consent gating and data minimization: Gate non-essential third-party video pixels behind clear, documented consent—or strip identifying parameters before data leaves your environment.

A law born from a 1987 video rental leak was never meant to serve as a general-purpose architecture manual for the modern web. Until Congress rewrites the statute or the Supreme Court draws a sharper line, the safest defense for any site running video is knowing—byte for byte—what its code actually broadcasts.

IB

Isabella Brooks

As a veteran correspondent, Isabella Brooks has reported from across the globe, bringing firsthand perspectives to international stories and local issues.