Clustered 3 filings across 3 jurisdictions · filing window Dec 6, 2023 → Jul 17, 2024. View entity profile → Other incidents for this victim →
incident inc_704a2d61d9e54e24 · merge_method human · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Materiality delta · SEC filing delay — no SEC 8-K in this cluster.
PII · Government ID · Financial account
ME NH
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Aug 6, 2023 → Nov 17, 2023
When the intrusion reportedly occurred, per the linked filings
Nov 17, 2023
Reported by NEW HAMPSHIRE AG, MAINE AG filings
Sagent provides a comprehensive array of network services and helps their clients lower the cost of network ownership by using business analytics and network support services.The main office of the company is located at 120 Dividend Dr Ste 160, Coppell, Texas, 75019, United States
Sagent, LLC notified New Hampshire residents of unauthorized network access between August 6 and November 17, 2023. The incident was discovered on November 17, 2023. Personal information (names and data elements) was compromised. Sagent engaged forensic specialists, notified law enforcement, and offered credit monitoring via Kroll.
Sagent, LLC (Coppell, TX) experienced unauthorized access to its computer network between August 6, 2023 and November 17, 2023, discovered on November 17, 2023. The review concluded April 9, 2024. Potentially compromised data includes names, Social Security numbers, driver's license numbers, and financial account information. One Maine resident was affected out of 826 total. Notifications sent July 17, 2024. Twelve months of Kroll identity monitoring offered 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
Affected (this filing): 1