DisclosureLens
State AGConfirmed6 filings · 1 stateLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 6 filings

Rockland Trust Company

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

data types agreeMerge100%

Determination

Confirmed

Members

6 filings

States

1

Affected · reported

First → last filing

Jan 13, 2026 Apr 30, 2026

Merge confidence

100%

incident inc_9aadfbf65d8e49dc · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings. The filings describe an accidental exposure. Data reported: Government ID, PII, Identity (basic), and 1 more. Notifications rolled out on a 107-day schedule across 6 filings beginning Jan 13, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Filing span
107days

Time between earliest and latest filing

Not recorded for this incident

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

Sensitive data

identity_government

Incident timeline

? — ?breach window unknown
Jan 13, 2026first filing
Apr 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 13MA AGMA AG noticefirst filing · no count statedday 0
  2. FEB 19MA AGMA AG noticeno count stated+37d
  3. MAR 11MA AGMA AG noticeno count stated+57d
  4. MAR 11MA AGMA AG noticeno count stated+57d
  5. MAR 26MA AGMA AG noticeno count stated+72d
  6. APR 30MA AGMA AG noticemost recent · no count stated+107d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Discovered
Data types
Financial account · Identity (basic) · Government ID · PII
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 filing6 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

107 days

Cadence

~1 / 21.4d

vs. multi-state median

13.4× 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. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.