Clustered 2 filings across 2 jurisdictions · filing window Nov 18, 2025 → Nov 19, 2025. View entity profile → Other incidents for this victim →
incident inc_06433a43c3624bb4 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
ME TX
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 1, 2025 → May 6, 2025
When the intrusion reportedly occurred, per the linked filings
Oct 10, 2025
Reported by MAINE AG, TEXAS AG filings
Optima Tax Relief, LLC experienced an external system breach, or hacking incident, which was discovered on October 10, 2025. The breach occurred between May 1, 2025, and May 6, 2025, affecting 30 Maine residents. The company offered one year of credit monitoring and identity theft protection services through Kroll.
Affected (this filing): 30
Optima Tax Relief, LLC based in Santa Ana, California, a financial services entity reported a data breach to the Texas Attorney General. The breach was discovered on 2025-10-10 and reported on 2025-11-19. 2,351 Texas residents were affected. 19,732 individuals affected in total. Types of information involved: Name of individual;Social Security Number Information;Driver’s License number;Financial Information (e.g. account number, credit or debit card number);Medical Information;Health Insurance Information. Consumers were notified via U.S. Mail.
Affected (this filing): 2,351
About this clustering
DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.