Herbert W. Auger PA reported a data breach to the Indiana Attorney General. The breach occurred on 2026-02-17 and was reported on 2026-03-27. 1 Indiana residents were affected. 5,102 individuals affected in total.
Affected (this filing): 5,102
Clustered 2 filings across 2 jurisdictions · filing window Mar 27, 2026 → Mar 30, 2026. View entity profile → Other incidents for this victim →
incident inc_cb5569f16f6f4ca7 · 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 ME
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Feb 17, 2026
When the intrusion reportedly occurred, per the linked filings
Mar 4, 2026
Reported by MAINE AG filing
Herbert W. Auger PA reported a data breach to the Indiana Attorney General. The breach occurred on 2026-02-17 and was reported on 2026-03-27. 1 Indiana residents were affected. 5,102 individuals affected in total.
Affected (this filing): 5,102
Herbert W. Auger, P.A., a North Carolina law firm ("Other Commercial"), reported a data breach to the Maine AG affecting 5,102 individuals nationwide, including 2 Maine residents. The breach occurred on 02/17/2026 and was discovered on 03/04/2026. The description was filed as 'Other' with no specific information categories enumerated. Written notification was sent on 03/27/2026 and 12 months of credit monitoring (Epiq Privacy Solutions ID) was offered. Submitted by outside counsel Gursharon Shergill of Wagner Hicks PLLC.
Affected (this filing): 5,102
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.