DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79
State AGConfirmed3 filings · 1 stateLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmoderate sensitivity
Merged incident · 3 filings

St. Mary's Credit Union

Clustered 3 filings across 1 jurisdiction · filing window Jan 16, 2026 → Jan 30, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

3 filings

States

1

Affected · reported

1

First → last filing

Jan 16, 2026 → Jan 30, 2026

Merge confidence

100%

incident inc_f3fc89978df34a15 · merged by deterministic · confidence 100%

Confirmed breach. One breach, 3 legal records. 1 individuals reported across the linked filings. Notifications rolled out on a 14-day schedule across 3 filings beginning Jan 16, 2026. This page is the deduped roll-up; each member filing remains the legal record for its jurisdiction.

Litigation Timing

Filing span
14days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.

Incident timeline

? — ?breach window unknown
Jan 16, 2026first filing
Jan 30, 2026most recent filing

No discovery date is recorded on any filing in this cluster, so the notification delay is not computable. Dashed segments fill in as filings merge.

Member cascade — every filing about this breach

  1. JAN 16MA AGMA AG noticefirst filing · 1 MA residentsday 0
  2. JAN 23MA AGMA AG notice1 MA residents+7d
  3. JAN 30MA AGMA AG noticemost recent · 1 MA residents+14d
  4. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
—
Discovered
—
Data types
Financial account · PII
MA AG
Attack vector
Unauthorized Access
MA AG
Response
Lowered daily limits on debit cards to $210 for ATM withdrawals and $500 for POS purchases · Issued new debit cards to affected members · Deactivated compromised debit cards by 2/3/2026
MA AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing3 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

14 days

Cadence

~1 / 7d

vs. multi-state median

2.8× slower

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.