Clustered 4 filings across 2 jurisdictions · filing window Mar 15, 2024 → May 1, 2024. View entity profile → Other incidents for this victim →
incident inc_bde445ce9fb141f1 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
IN ME
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
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
Jun 4, 2023
When the intrusion reportedly occurred, per the linked filings
Feb 27, 2024
Reported by MAINE AG filing
Intuit Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2023-06-04 and was reported on 2024-03-15. 4 Indiana residents were affected.
Affected (this filing): 4
Intuit Inc. reported an account takeover incident that affected one resident of Maine. The breach, which occurred from December 23, 2023, to February 21, 2024, was discovered on February 27, 2024. The compromised information included the resident's name and Social Security number. Intuit offered a 12-month membership to Experian IdentityWorks for identity theft protection.
Affected (this filing): 1
Apr 2, 2024
Reported by MAINE AG filing
Intuit Inc. experienced an account takeover incident affecting one Maine resident. The breach occurred on July 12, 2023, was discovered on April 2, 2024, and led to the exposure of a name and Social Security number. The company provided written notification and offered a 12-month membership to Experian IdentityWorks.
Affected (this filing): 1
Intuit Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2023-11-01 and was reported on 2024-05-01. 2 Indiana residents were affected.
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.