Clustered 3 filings across 3 jurisdictions · filing window Oct 11, 2025 → Jan 5, 2026. View entity profile → Other incidents for this victim →
incident inc_75484c92a7b943fa · merge_method human · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
IN VT
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 11, 2025
When the intrusion reportedly occurred, per the linked filings
Designs for Vision, Inc. specializes in high-quality magnificatio n and LED headlights for dental, medical, and low vision applicat ions. We will upload about 50gb of corporate documents soon. Lots of pr oject information, a bit of personal information, credit cards de tails and other financial and accounting information, contracts a nd agreements, NDA, etc.
Oct 13, 2025
Reported by VERMONT AG filing
Designs for Vision Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2025-10-11 and was reported on 2026-01-05. 28 Indiana residents were affected. 1,636 individuals affected in total.
Designs For Vision, Inc. notified consumers of a data breach where unauthorized access to its network occurred between October 11 and 13, 2025. The incident resulted in the exfiltration of names and associated data elements. The company engaged in network security and policy reviews and offered complimentary identity monitoring services through Kroll to affected individuals.
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.
Affected (this filing): 1,636