Fox Valley Tax Solutions reported a data breach to the Indiana Attorney General. The breach occurred on 2026-05-06 and was reported on 2026-06-29. 20 Indiana residents were affected. 2,182 individuals affected in total.
Affected (this filing): 2,182
Clustered 2 filings across 2 jurisdictions · filed Jun 29, 2026. View entity profile → Other incidents for this victim →
incident inc_9d131d259e814772 · 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.
Identity (basic) · Government ID · Financial account
IN NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 6, 2026
When the intrusion reportedly occurred, per the linked filings
May 7, 2026
Reported by NEW HAMPSHIRE AG filing
Fox Valley Tax Solutions reported a data breach to the Indiana Attorney General. The breach occurred on 2026-05-06 and was reported on 2026-06-29. 20 Indiana residents were affected. 2,182 individuals affected in total.
Affected (this filing): 2,182
Fox Valley Tax Solutions notified the New Hampshire Attorney General on June 29, 2026, of a data event affecting two NH residents. Unauthorized access occurred between May 6-7, 2026, resulting in the copying of files containing names, SSNs, and financial account information. The company notified law enforcement/IRS and provided 12 months of credit monitoring via Kroll.
Affected (this filing): 2
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.