On Q Financial reported a data breach to the Indiana Attorney General. The breach occurred on 2024-02-21 and was reported on 2024-03-29. 587 Indiana residents were affected. 211,650 individuals affected in total.
Affected (this filing): 211,650
Clustered 2 filings across 2 jurisdictions · filed Mar 29, 2024. View entity profile → Other incidents for this victim →
incident inc_f303170871e549e6 · 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
DE IN
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Feb 24, 2021
Reported by DELAWARE AG filing
Feb 21, 2024
When the intrusion reportedly occurred, per the linked filings
On Q Financial reported a data breach to the Indiana Attorney General. The breach occurred on 2024-02-21 and was reported on 2024-03-29. 587 Indiana residents were affected. 211,650 individuals affected in total.
Affected (this filing): 211,650
On Q Financial, Inc. disclosed a data breach occurring between Feb 22-23, 2021, discovered on Feb 24, 2021. Customer data, including names, addresses, SSNs, FICO scores, and bank account info, was exposed from a backup storage location. On Q secured the storage, increased monitoring, and offered 12 months of credit monitoring via NortonLifeLock.
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.