Clustered 3 filings across 1 jurisdiction · filing window Dec 23, 2022 → Mar 20, 2023. View entity profile → Other incidents for this victim →
incident inc_336b53ceac844a0e · merge_method deterministic · confidence 99%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Identity (basic) · PII
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
NH
all State AG
per-filing reported counts
State AGs report only their own residents; bars show per-filing counts.
Earliest sighting first · deep chronology in Litigation Timeline
Sep 7, 2022 → Sep 14, 2022
When the intrusion reportedly occurred, per the linked filings
Sep 7, 2022
Reported by NEW HAMPSHIRE AG filings
Sep 14, 2022
Reported by NEW HAMPSHIRE AG filing
Emtec, Inc. filed a supplemental notice with the New Hampshire AG regarding unauthorized access to personal information of 5 NH residents. Access occurred Sept 7-14, 2022. Emtec engaged third-party experts and law enforcement, terminated access, and provided 24 months of credit monitoring.
Affected (this filing): 5
Emtec, Inc. reported a supplemental data breach to New Hampshire AG. Unauthorized third parties accessed files containing personal information (names, addresses) of 13 NH residents between Sept 7-14, 2022. Emtec detected the incident, engaged third-party experts and law enforcement, terminated access, and provided 24 months of credit monitoring.
Affected (this filing): 13
Emtec, Inc. reported unauthorized access to employee/contractor personal information (name, address, etc.) from Sept 7-14, 2022. 14 NH residents affected. Emtec engaged third-party experts and law enforcement, contained the breach, and provided 24 months of credit monitoring. This is a supplemental notice.
Affected (this filing): 14
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.