Charter Township of Ypsilanti reported a data breach to the Indiana Attorney General. The breach occurred on 2024-04-18 and was reported on 2024-05-09. 1 Indiana residents were affected. 381 individuals affected in total.
Affected (this filing): 381
Clustered 2 filings across 2 jurisdictions · filed May 9, 2024. View entity profile → Other incidents for this victim →
incident inc_d805da04159d4eeb · 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
Apr 18, 2024
When the intrusion reportedly occurred, per the linked filings
Apr 18, 2024
Reported by NEW HAMPSHIRE AG filing
Charter Township of Ypsilanti reported a data breach to the Indiana Attorney General. The breach occurred on 2024-04-18 and was reported on 2024-05-09. 1 Indiana residents were affected. 381 individuals affected in total.
Affected (this filing): 381
Charter Township of Ypsilanti notified the NH AG of a data breach on May 9, 2024, involving the inadvertent disclosure of 2022 Form W-2s for one NH resident. The incident occurred on April 18, 2024, when an employee's email account was compromised via phishing. Data exposed included personal information from W-2s. The Township provided free credit monitoring services to the affected individual.
Affected (this filing): 1
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.