Organized Living reported a data breach to the Indiana Attorney General. The breach occurred on 2024-03-13 and was reported on 2024-04-04. 913 Indiana residents were affected. 1,061 individuals affected in total.
Affected (this filing): 1,061
Clustered 2 filings across 2 jurisdictions · filing window Apr 4, 2024 → Apr 9, 2024. View entity profile → Other incidents for this victim →
incident inc_3514aa45d8364a97 · 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
Mar 13, 2024
When the intrusion reportedly occurred, per the linked filings
Mar 13, 2024
Reported by NEW HAMPSHIRE AG filing
Organized Living reported a data breach to the Indiana Attorney General. The breach occurred on 2024-03-13 and was reported on 2024-04-04. 913 Indiana residents were affected. 1,061 individuals affected in total.
Affected (this filing): 1,061
Organized Living notified the NH Attorney General on April 9, 2024, of a phishing ransomware attack discovered on March 13, 2024. The incident affected 1,061 current and former employees, including 1 New Hampshire resident. Breached data included employment and hiring information. The company locked down systems, notified law enforcement, hired IT consultants, and sent notification letters with identity theft protection information to affected individuals on April 5, 2024.
Affected (this filing): 1,061
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.