Visage Imaging, Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2025-07-04 and was reported on 2025-11-26. 1 Indiana residents were affected. 51 individuals affected in total.
Affected (this filing): 51
Clustered 2 filings across 2 jurisdictions · filing window Nov 26, 2025 → Dec 1, 2025. View entity profile → Other incidents for this victim →
incident inc_342b211da6284541 · 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 NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jul 4, 2025
When the intrusion reportedly occurred, per the linked filings
Aug 22, 2025
Reported by NEW HAMPSHIRE AG filing
Visage Imaging, Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2025-07-04 and was reported on 2025-11-26. 1 Indiana residents were affected. 51 individuals affected in total.
Affected (this filing): 51
Visage Imaging, Inc. notified the New Hampshire Attorney General on November 26, 2025, of a security incident discovered on August 22, 2025. An unauthorized third party gained access to a single employee's business email account via phishing and fraudulently requested a payment redirection. The investigation determined that one New Hampshire resident's personal information, including name and Social Security number, may have been accessed. Visage contained the incident, revoked access, and offered 24 months of identity protection services to the affected individual.
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.