Confirmed breach. Intrusion Feb 27, 2023, discovered Apr 7, 2023 — the first regulatory filing landed 25 days later. 329 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksMaine✓ ME AG ≤30d · 25dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
329
Data types
2
Government ID · Identity (basic)
Jurisdictions
1
ME
Linked filings
1
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Feb 27, 2023
When the intrusion reportedly occurred, per the linked filings
Martin, Inc. reported an external system breach (hacking) occurring on 02/27/2023, discovered on 04/07/2023. The incident compromised names and Social Security Numbers of 329 individuals, including 1 Maine resident. The company provided written notification on 05/02/2023 and offered 24 months of identity protection services through Experian.
Affected (this filing): 329
ME AG ≤30d · 25d
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.