Confirmed breach. Intrusion Mar 5, 2026, discovered Mar 6, 2026 — the first regulatory filing landed 55 days later. 709 individuals reported across the linked filings.
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.
Regulatory clocksLeak gap⏱ Leak >30dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
709
Data types
—
Jurisdictions
2
IN NH
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Mar 5, 2026
When the intrusion reportedly occurred, per the linked filings
AEC Holdco LLC dba Grace Design Studios LLC reported a data breach to the Indiana Attorney General. The breach occurred on 2026-03-05 and was reported on 2026-04-30. 21 Indiana residents were affected. 709 individuals affected in total.
Affected (this filing): 709
Leak >30d
⛰️New Hampshire State AGMost recentlinked via multistate filing link · 100%
AEC Holdco, LLC d/b/a Grace Design Studios, LLC, a Louisiana architecture and design firm, reported a ransomware incident to the New Hampshire Attorney General. The company discovered unauthorized access on March 6, 2026, which involved the encryption of systems and exfiltration of employee personal information, including names and Social Security numbers. One New Hampshire resident was identified. The company took systems offline, engaged forensic investigators, and notified the affected individual on April 30, 2026, offering credit monitoring services.
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.