Art Jetter & Company reported a data breach to the Indiana Attorney General. The breach occurred on 2026-02-21 and was reported on 2026-05-04. 2 Indiana residents were affected. 150 individuals affected in total.
Affected (this filing): 150
Clustered 2 filings across 2 jurisdictions · filed May 4, 2026. View entity profile → Other incidents for this victim →
incident inc_5e803244ff90445f · 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 ME
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Feb 21, 2026
When the intrusion reportedly occurred, per the linked filings
Feb 23, 2026
Reported by MAINE AG filing
Art Jetter & Company reported a data breach to the Indiana Attorney General. The breach occurred on 2026-02-21 and was reported on 2026-05-04. 2 Indiana residents were affected. 150 individuals affected in total.
Affected (this filing): 150
Art Jetter & Company (Omaha, NE) reported to the Maine AG that an external system breach (hacking) occurred on 02/21/2026 and was discovered on 02/23/2026. A total of 150 persons were affected, including 4 Maine residents. Written consumer notifications were sent on 05/04/2026, and Kroll identity theft protection services (12 months — credit monitoring, fraud consultation, identity theft restoration) were offered. The filing does not specify the categories of information acquired.
Affected (this filing): 150
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.