Clustered 2 filings across 2 jurisdictions · filing window Oct 23, 2024 → Oct 24, 2024. View entity profile → Other incidents for this victim →
incident inc_957ea27034c14ca9 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
PII · Credentials · Financial
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
ME NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 7, 2024 → May 9, 2024
When the intrusion reportedly occurred, per the linked filings
May 8, 2024
Reported by MAINE AG, NEW HAMPSHIRE AG filings
Between May 7-9, 2024, an unauthorized actor accessed Wise Construction Corporation's systems, potentially acquiring files. Discovered May 8, 2024. Compromised data: names, SSNs, and/or financial account info. 5 Maine residents affected (460 total). Written notice sent Oct 23, 2024. 12 months credit monitoring via TransUnion/Cyberscout offered.
Affected (this filing): 5
Wise Construction Corporation notified New Hampshire residents of a security incident detected on May 8, 2024. Unauthorized access occurred between May 7-9, 2024. Personal information of 41 NH residents was potentially affected. Wise notified law enforcement, offered credit monitoring via TransUnion, and is reviewing security policies.
Affected (this filing): 41
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.