The 1911 Trust Company, LLC reported a data breach to the Indiana Attorney General. The breach occurred on 2023-05-31 and was reported on 2024-01-29. 1 Indiana residents were affected. 19 individuals affected in total.
Affected (this filing): 19
Clustered 2 filings across 2 jurisdictions · filed Jan 29, 2024. View entity profile → Other incidents for this victim →
incident inc_6ee2b8997481477c · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
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.
IN NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 31, 2023
When the intrusion reportedly occurred, per the linked filings
Nov 30, 2023
Reported by NEW HAMPSHIRE AG filing
The 1911 Trust Company, LLC reported a data breach to the Indiana Attorney General. The breach occurred on 2023-05-31 and was reported on 2024-01-29. 1 Indiana residents were affected. 19 individuals affected in total.
Affected (this filing): 19
The 1911 Trust Company, LLC reported a data security incident to the New Hampshire Attorney General on January 29, 2024. The incident involved a third-party vendor, Paycor, which experienced a cybersecurity event exploiting the MOVEit zero-day vulnerability. The breach impacted the names and Social Security numbers of 1911 Trust's employees and dependents. 1911 Trust notified 3 potentially impacted New Hampshire residents and offered credit monitoring services.
Affected (this filing): 3
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.