Clustered 2 filings across 2 jurisdictions · filing window Jun 7, 2022 → Jun 23, 2022. View entity profile → Other incidents for this victim →
incident inc_2b3742937cd9439e · merge_method llm · confidence 57%
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.
Government ID · Identity (basic)
ME NJ
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Nov 15, 2021 → Nov 18, 2021
When the intrusion reportedly occurred, per the linked filings
Mar 29, 2022
Reported by MAINE AG filing
Bergen's Promise, Inc. reported to HHS on 2022-06-07 a Hacking/IT Incident affecting 7349 individuals. Breached information located on Email. Employees were subjects of an email phishing attack exposing PHI including names, addresses, DOB, driver's license numbers, SSNs, diagnoses, and financial/insurance information. The BA provided credit monitoring and identity theft protection.
Affected (this filing): 7,349
Bergen's Promise, Inc. reported an external system breach involving email phishing. The incident occurred between November 15-18, 2021, and was discovered on March 29, 2022. Approximately 7,513 individuals were affected, including 4 Maine residents. The breach compromised names and Social Security Numbers. Written notifications were sent on June 3, 2022, offering 12 months of credit monitoring services.
Affected (this filing): 7,513
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.