Clustered 3 filings across 2 jurisdictions · filing window Dec 20, 2024 → Feb 12, 2025. View entity profile → Other incidents for this victim →
incident inc_2d6b6aff94954cbc · 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
per-filing reported counts
State AGs report only their own residents; bars show per-filing counts.
Earliest sighting first · deep chronology in Litigation Timeline
Mar 5, 2024 → Mar 18, 2024
When the intrusion reportedly occurred, per the linked filings
Nov 21, 2024
Reported by MAINE AG filing
On November 21, 2024, Intuit Inc. discovered a data breach that occurred between March 5, 2024, and March 18, 2024. The breach affected one resident of Maine. In response, Intuit offered 12 months of identity theft restoration and credit monitoring services through Experian IdentityWorks. The specific type of breach and the data types involved were not specified in the notification.
Affected (this filing): 1
Intuit Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2024-03-05 and was reported on 2024-12-20. 1 Indiana residents were affected.
Affected (this filing): 1
Intuit Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2025-01-12 and was reported on 2025-02-12. 1 Indiana residents were affected.
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.