Clustered 2 filings across 1 jurisdiction · filed Feb 17, 2026. View entity profile → Other incidents for this victim →
incident inc_69c221e9768a4649 · merge_method deterministic · confidence 100%
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
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Aug 14, 2024
When the intrusion reportedly occurred, per the linked filings
TABB Inc on behalf of Crudem Foundation reported a data breach to the Indiana Attorney General. The breach occurred on 2024-08-14 and was reported on 2026-02-17. 26 Indiana residents were affected. 2,539 individuals affected in total.
Affected (this filing): 2,539
TABB Inc on behalf of Crudem Foundation reported a data breach to the Indiana Attorney General. The breach occurred on 2024-08-14 and was reported on 2026-02-17. 26 Indiana residents were affected. 2,539 individuals affected in total.
Affected (this filing): 2,539
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.