Is having LogRocket on my site illegal?

No. The complaints do not claim the script is illegal; they claim it recorded a visitor before the visitor consented, or kept recording after the visitor declined. Loading LogRocket only after consent, or removing it when it is not used, is what removes the pattern the complaints describe.

How do I know if LogRocket fires before consent on my site?

Run the free scan. It loads your pages without clicking anything and checks every request that leaves the browser against its tracker catalog, recording the millisecond each match fired. If LogRocket appears, it fired before consent. When your banner has a reject button, the scan clicks it and reports whether the script kept firing.

Where do the case counts on this page come from?

From the complaint text of verified California Invasion of Privacy Act filings. When a complaint names this script, the case is linked to it. Complaints that are not yet available in the public record are not counted, so the number is a floor.

Session replay from LogRocket

LogRocket and website tracking lawsuits

LogRocket records visitor sessions so developers can replay bugs, capturing clicks, typing, and page changes.

What Suitcast knows about LogRocket

Critical risk

Type: Session replay
Complaints naming it, 12 months: 2

Requests the scanner matches to it

cdn.logrocket.io
cdn.lr-ingest.io
r.lr-ingest.io
cdn.lr-in.com
r.lr-in.com
cdn.lr-in-prod.com
r.lr-in-prod.com
.logrocket.io
.logrocket.com
.lr-ingest.io
.lr-in.com
.lr-in-prod.com

The short answer

LogRocket is a session replay tool from LogRocket. Suitcast rates its risk under the California Invasion of Privacy Act, CIPA, as critical, because complaints describe scripts like it recording visitors before they consent. It is named in 2 verified complaints in the last 12 months. The fix is to load it only after a visitor accepts, or to remove it when it is not used.

Why complaints name it

Complaints describe this kind of recording as intercepting a visitor's communications with your site before they agreed.

The act allows $5,000 per violation, which is why firms look for scripts that run the moment a page opens.

The fix

How to stop LogRocket firing before consent

Written for the person who runs the site, with the setting to change.

Ask your developer to start LogRocket only after the visitor accepts your cookie banner and to turn on input masking for all form fields.
If it was added for a past project and nobody reviews it, remove it.

How the scan checks this

Loads your pages like a first visit. A real browser, nothing clicked, nothing accepted.
Checks every request before the banner is answered. A request to cdn.logrocket.io is matched to LogRocket and recorded with the millisecond it fired.
Clicks reject and watches again. When the banner has a reject button, the scan presses it; if LogRocket keeps firing, the report says so.

Scanner rules and limits are on the methodology page.

Trend

Complaints naming LogRocket, month by month

Verified tracking complaints whose text names this script, by the month they were filed.

Website accessibility (ADA) Website tracking (CIPA)

November 2025 to October 2026, current month to date

Court records

Latest verified complaints naming LogRocket

Newest first. Every row links to the court record.

TrackingFiled Sep 30, 2026
RUBIO v. FIVE BELOW, INC.
E.D. Pennsylvania, filed by Edelson Lechtzin LLP, Edelson Lechtzin LLP. Attributed to Pennsylvania
Court recordfor RUBIO v. FIVE BELOW, INC. (opens in a new tab)
TrackingFiled Dec 2, 2025
Smith v. Advance America, Cash Advance Centers, Inc.
N.D. California, filed by Bursor & Fisher, P.A.. Attributed to South Carolina
Court recordfor Smith v. Advance America, Cash Advance Centers, Inc. (opens in a new tab)

Same type

Other session replay tools the scanner checks

Scripts of the same kind carry the same pattern in complaints, and the same fix.

Questions owners ask

Whether LogRocket is a problem, how to check your site, and where the counts come from.

Is having LogRocket on my site illegal?: No. The complaints do not claim the script is illegal; they claim it recorded a visitor before the visitor consented, or kept recording after the visitor declined. Loading LogRocket only after consent, or removing it when it is not used, is what removes the pattern the complaints describe.
How do I know if LogRocket fires before consent on my site?: Run the free scan. It loads your pages without clicking anything and checks every request that leaves the browser against its tracker catalog, recording the millisecond each match fired. If LogRocket appears, it fired before consent. When your banner has a reject button, the scan clicks it and reports whether the script kept firing.
Where do the case counts on this page come from?: From the complaint text of verified California Invasion of Privacy Act filings. When a complaint names this script, the case is linked to it. Complaints that are not yet available in the public record are not counted, so the number is a floor.

Keep going

Does LogRocket fire before consent on your site?

The free scan checks every request your pages make before the banner is answered, shows the millisecond LogRocket fired, and whether it kept firing after reject.

Suitcast identifies risk indicators. It is not legal advice and does not determine compliance.