FirstAlerts

LexisNexis Class Action Dismissed After Company Answers Privacy Request Allegations

A federal court dismissed a proposed Fair Credit Reporting Act class action after LexisNexis responded to claims over its handling of roughly 18,607 privacy requests.

2 reports on this incident · first at Sep 10, 2026, 4:22 p.m. ET

By AI ReporterWritten Sep 10, 2026, 4:23 p.m. ET
A federal district court has a proposed class action accusing LexisNexis of violating the Fair Credit Reporting Act in its response to consumer privacy requests, according to natlawreview.com. The dismissal followed LexisNexis's answer to the allegations. LexisNexis reportedly placed security freezes on approximately 18,607 files, maintaining that it could not redact the protected information from consumer reports without doing so, natlawreview.com reported. The court declined to certify a class of people seeking damages over that response. The matter was proceeding in federal district court and is now , according to natlawreview.com. No further details on the court's reasoning or the terms of the dismissal were available in the report.

Earlier reports

  1. Sep 10, 2026, 4:22 p.m. ETFirst report

    Federal Court Declines to Certify FCRA Class Over LexisNexis Privacy Request Response

    A federal district court declined to certify a class of people seeking damages over LexisNexis's response to privacy requests that allegedly violated the Fair Credit Reporting Act, natlawreview.com reported. The proceeding is at the dismissed stage, according to the outlet.

    LexisNexis reportedly placed security freezes on approximately 18,607 files, maintaining that it could not redact the protected information from consumer reports without doing so, natlawreview.com reported. The outlet reported the allegations; the court has not certified the class.

Was this report accurate and useful?

Sources

Revision history

  1. Version 110 Sept 2026, 20:23current

    First published.

  2. Version 110 Sept 2026, 20:22current

    First published.

How we work

This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.

Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.

Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.

None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.