Asian Cultural Council, Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2025-02-11 and was reported on 2025-05-07. 2 Indiana residents were affected. 356 individuals affected in total.
Affected (this filing): 356
Clustered 2 filings across 2 jurisdictions · filed May 7, 2025. View entity profile → Other incidents for this victim →
incident inc_a4cf56422b1f4f86 · 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.
PII
IN ME
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Feb 11, 2025
When the intrusion reportedly occurred, per the linked filings
Apr 7, 2025
Reported by MAINE AG filing
Asian Cultural Council, Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2025-02-11 and was reported on 2025-05-07. 2 Indiana residents were affected. 356 individuals affected in total.
Affected (this filing): 356
Asian Cultural Council (ACC), a non-profit based in New York, notified the Maine AG of a ransomware incident suffered by Linear Technologies, Inc. (LTI), a managed IT service provider retained by ACC since 2007. LTI experienced deployment of ransomware and encryption of data it maintained on behalf of ACC. The breach occurred on 02/11/2025, was discovered on 04/07/2025, and affected 1 Maine resident out of 356 total individuals. No identity theft protection services were offered.
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.