Clustered 3 filings across 3 jurisdictions · filing window Dec 9, 2024 → Mar 10, 2025. View entity profile → Other incidents for this victim →
incident inc_05ddd2e9f62d47bf · merge_method human · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
MD NH
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Nov 18, 2024
Reported by MARYLAND AG filing
For more than 50 years, BCNC has been providing new immigrants, especially Asians, with the support and resources they need to thrive in the United States. With deep roots in Boston's Chinatown neighborhood, BCNC now serves people from three locations in Greater Boston and the South Shore We present you with personal data of employees, contracts and much more.
Boston Chinatown Neighborhood Center, Inc. notified the Maryland Attorney General on March 6, 2025, of a network security incident discovered on November 18, 2024. The breach affected one Maryland resident, exposing their first and last name and Social Security number. The organization engaged third-party forensic experts, offered complimentary credit monitoring, and advised the resident on fraud alerts and security freezes. No identity fraud has been reported.
State AG filing for Boston Chinatown Neighborhood Center, Inc. in New Hampshire. The source document provided is empty (no text content in the attachment or HTML body). No breach details, dates, or data types could be extracted.
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.
Affected (this filing): 1