Clustered 2 filings across 2 jurisdictions · filed Sep 5, 2024. View entity profile → Other incidents for this victim →
incident inc_b13e97ac0b2c437b · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
PII · Financial · Credentials
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.
ME VT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 15, 2024
When the intrusion reportedly occurred, per the linked filings
May 15, 2024
Reported by VERMONT AG filing
May 16, 2024
Reported by MAINE AG filing
On May 15, 2024, a Rockland Trust vendor inadvertently shared inactive Bill Pay account data with an unaffiliated third-party financial institution. Exposed data included names, addresses, emails, bill pay IDs, member IDs, SSNs, and funding account numbers. The recipient certified data destruction. 2,614 individuals affected total; 3 Maine residents. Notifications sent August 29, 2024.
Affected (this filing): 3
Rockland Trust notified customers of an operational incident on May 15, 2024, where personal information from inactive Bill Pay accounts was inadvertently shared with an unaffiliated third-party financial institution by a vendor. Data exposed included names, addresses, SSNs, and account numbers. The vendor and recipient confirmed data deletion. Rockland Trust offered two years of Experian IdentityWorks.
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.