Clustered 2 filings across 2 jurisdictions · filing window Oct 8, 2025 → Oct 9, 2025. View entity profile → Other incidents for this victim →
incident inc_1a558e8ec3154b8f · 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
Feb 3, 2025
When the intrusion reportedly occurred, per the linked filings
Aug 13, 2025
Reported by MAINE AG, TEXAS AG filings
Strategic Retail Partner experienced an external system breach (hacking) on February 3, 2025, which was discovered on August 13, 2025. The company notified affected Maine residents on October 8, 2025, and offered 12 months of credit monitoring and identity theft protection services through TransUnion. The specific types of information acquired were not detailed in the notice.
Strategic Retail Partners based in Castle Rock, Colorado, a business – retail or merchant entity reported a data breach to the Texas Attorney General. The breach was discovered on 2025-08-13 and reported on 2025-10-09. 271 Texas residents were affected. 4,097 individuals affected in total. Types of information involved: Social Security Number Information;Driver’s License number;Government-issued ID number (e.g. passport, state ID card);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): 271
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.