Saint Francis Ministries — May 2020 breach
One linked filing — more sources may join as they report · filed Dec 23, 2020. View entity profile → Other incidents for this victim →
incident inc_24649dba600a453f · merged by deterministic
Litigation Timing
Discovered → first regulatory filing
Not recorded for this incident
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.
Sensitive data
identity_governmentIncident timeline
Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.
Member cascade — every filing about this breach
- DEC 23NH AGNH AG noticeonly filing · 1 NH residentsday 0
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- May 1, 2020 – May 20, 2020 NH AG
- Discovered
- Oct 6, 2020· 158d undetected NH AG
- Data types
- Government ID · Identity (basic) · Financial account NH AG
- Attack vector
- Third-Party / Supply Chain NH AG
- Response
- Began an investigation to determine the nature and scope of the incident · Provided written notice of this incident to all affected individuals · Provided access to credit monitoring services for one year, through Epiq, to individuals whose personal information was potentially affected by this incident, at no cost to these individuals NH 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
No leak-site claim on record for this incident.
No press coverage linked yet.
Unlocks: discovery date, data types, affected count, compliance clock.
No SEC filing or victim statement yet.
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.