Vocatura Spagnuolo & Company reported a data breach to the Indiana Attorney General. The breach occurred on 2025-07-16 and was reported on 2025-11-13. 2 Indiana residents were affected. 983 individuals affected in total.
Affected (this filing): 983
Clustered 2 filings across 2 jurisdictions · filing window Nov 13, 2025 → Dec 17, 2025. View entity profile → Other incidents for this victim →
incident inc_aae6c26a69384086 · merge_method deterministic · confidence 95%
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
IN VT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jul 16, 2025
When the intrusion reportedly occurred, per the linked filings
Jul 16, 2025
Reported by VERMONT AG filing
Vocatura Spagnuolo & Company reported a data breach to the Indiana Attorney General. The breach occurred on 2025-07-16 and was reported on 2025-11-13. 2 Indiana residents were affected. 983 individuals affected in total.
Affected (this filing): 983
Vocatura, Spagnuolo & Company reported unauthorized access to a single email account on July 16, 2025. The incident involved an unknown actor viewing emails without permission. Affected data included names, Social Security numbers, dates of birth, and addresses. Approximately 22 Rhode Island residents were impacted. The firm offered complimentary identity monitoring services and notified affected individuals.
Affected (this filing): 22
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.