Clustered 2 filings across 2 jurisdictions · filing window Feb 7, 2026 → May 22, 2026. View entity profile → Other incidents for this victim →
incident inc_7698820bb4364afa · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
OR 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
Dec 1, 2025
When the intrusion reportedly occurred, per the linked filings
Dec 1, 2025
Reported by OREGON AG, TEXAS AG filings
The Phia Group, LLC reported a data breach to the Oregon Attorney General. The breach was reported on 2026-02-07. The breach occurred during 12/1/2025. The breach was discovered on 12/1/2025. 40,366 individuals were affected. Notice was sent on 12/4/2025.
Affected (this filing): 40,366
The Phia Group, LLC based in Canton, Massachusetts, a other entity reported a data breach to the Texas Attorney General. The breach was discovered on 2025-12-01 and reported on 2026-05-22. 121,354 Texas residents were affected. 1,512,742 individuals affected in total. Types of information involved: Name of individual;Address;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 Posted at company website or special website;U.S. Mail;Broadcast on Texas-wide Media.
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.
Affected (this filing): 121,354