Clustered 2 filings across 1 jurisdiction · filing window Jan 19, 2021 → Jan 20, 2021. View entity profile → Other incidents for this victim →
incident inc_18b53bc4a666447a · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Identity (basic) · Financial account
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
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jul 31, 2020
When the intrusion reportedly occurred, per the linked filings
Nov 12, 2020
Reported by MAINE AG filings
Father Bill's & Mainspring reported an external system breach (hacking) occurring on July 31, 2020, discovered on November 12, 2020. The incident compromised names and financial account numbers for 1,168 individuals, including 2 Maine residents. The organization provided substitute notice and offered 12 months of credit monitoring via TransUnion.
Affected (this filing): 1,168
Father Bill's & Mainspring, a non-profit organization based in Brockton, MA, experienced an external system breach (hacking) on July 31, 2020. The incident affected 1,168 individuals, including 2 Maine residents. Compromised data included names and financial account numbers (combined with security codes/PINs). The organization provided substitute notice on January 14, 2021, and offered 12 months of credit monitoring and identity theft protection via TransUnion.
Affected (this filing): 1,168
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.