Falls v. Blue Cross Blue Shield of Michigan Mutual Insurance Company

Published by Crandall Consulting · Informational litigation intelligence · Last substantive update: August 23, 2026

Summary

Miller Canfield reports that a putative class action, Falls v. Blue Cross Blue Shield of Michigan, was filed in the Eastern District of Michigan alleging that the defendant used third‑party tracking pixels and session‑replay tools that captured and transmitted visitors' personally identifiable information to outside vendors. The complaint asserts claims under the Federal Wiretap Act and Michigan's eavesdropping statute and is described as one of nearly 4,000 similar suits nationwide since 2022.

Litigation Status

Status, direction, and weight describe how tracked public sources characterize this matter as of our last review — they are informational classifications, not legal assessments.

Procedural Posture

The publication reports a putative class action filed in the Eastern District of Michigan alleging that Blue Cross Blue Shield of Michigan deployed third‑party tracking pixels and session‑replay tools that collected and transmitted visitors' personally identifiable information to outside vendors. The complaint is described as asserting claims under the Federal Wiretap Act and the Michigan Eavesdropping Statute and joining thousands of similar filings nationwide since 2022.

Significance

Neutral / mixed significance. Characterizations of significance describe how the matter has generally been discussed in tracked public sources; individual holdings are often narrow, procedural, or fact-specific, and this page does not state or imply broader holdings than the sources support.

What This Page Does and Does Not Say

This page reports what our tracked public sources say about this matter — including, where identified, the procedural posture (for example, a ruling on a motion to dismiss is not a final merits decision). It does not report legal conclusions beyond those sources, does not predict outcomes, and does not constitute legal advice.

Technologies at Issue

• session replay
• third‑party tracking pixels
• website analytics
• third‑party advertising/analytics data sharing

Third parties named or identified in tracked sources: third‑party tracking vendors, outside technology vendors, third parties (unspecified).

Statutes Invoked

• Federal Wiretap Act (18 U.S.C. §2510 et seq.); Michigan Eavesdropping Statute (MCL 750.539a et seq.)

Claims Asserted

Claims identified in tracked public sources; pleadings may include additional or amended claims.

• Federal Wiretap Act (18 U.S.C. §2510 et seq.)
• Michigan Eavesdropping Statute (MCL 750.539a et seq.)

What This Matter May Mean for Website Operators

For operators using similar technologies, the recurring factual questions in matters like this one are when session recording begins relative to consent and whether input masking covers every field; whether advertising pixels transmit page URLs or hashed form data before a consent choice; what page URLs and query strings analytics tools share with third parties. Our scanner tests these behaviors empirically.

Because this matter is pending, anything reported here is procedural — allegations and interim rulings, not final determinations.

Detection of a similar technology on a website is an informational risk indicator, not a legal conclusion, and nothing in this section is legal advice.

Related Intelligence

Sources

• The Privacy Map Expands: Michigan Emerges in Website Tracking Litigation — Miller Canfield · Tier C (Professional analysis) · 2026-02-18

About This Page

Publisher: Inspection-Ready Institute, Inc. (DBA Crandall Consulting), an independent website compliance and risk consultancy. We are not a law firm and nothing on this page is legal advice.

How this content is produced: Facts are extracted from publicly available sources — court and government materials, recognized legal press, professional analysis, and industry reports — by our litigation intelligence engine, stored with full source provenance, and rendered from the database. Risk guidelines are computed by a deterministic formula, never by an AI model directly. See the full methodology.

Limitations: Counts labeled "Tracked" reflect matters identified in our source set and are not official court statistics. We report what courts decided and did not decide; we do not predict outcomes.

Corrections: If you believe anything on this page is inaccurate, contact us via the contact page and we will review the underlying sources promptly.