Disclosures Claims Reports Entities Incidents Pulse

Feed live

DisclosureLens

Structured extracts of public breach disclosures — regulator filings (SEC, HHS, state AGs, EU DPAs) alongside threat-actor leak-site claims and press reports. SEC and HHS filings render inline from the originating regulator’s public record under the fair report privilege; other sources link out to the source URL. AI-extracted with full per-record audit trail (model, prompt version, confidence).

ai_assisted: true · Article 50 disclosure on every record

Product

Disclosures feed
Pulse · analytics
Entities
Breach notifications by state

Methodology

How extraction works
Confidence & review
About the bot

Trust

Security
Self-disclosure commitment
API documentation
API keys

v0.1.0 · coverage growing weekly

New Horizons Behavioral Health data breach (2026) · DisclosureLens

All incidents View linkage analytics →

Incident · single filing

New Horizons Behavioral Health

One linked filing — more sources may join as they report · filed Mar 18, 2026. View entity profile → Other incidents for this victim →

Confirmed breach. 500 individuals reported across the linked filings.

incident inc_4df6fed30e62404b · merge_method deterministic

Litigation Timing

Not recorded for this incident

Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.

Regulatory clocksHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

HHS OCRConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmoderate sensitivity

Affected (total reported)

500

Data types

PHI

Jurisdictions

Linked filings

all HHS OCR

Timeline

Earliest sighting first · deep chronology in Litigation Timeline

GAHHS OCRFirst filing
Filed Mar 18, 2026bd_ecf1432a25411db3
New Horizons Behavioral Health, a Georgia-based healthcare provider, reported a Hacking/IT Incident to HHS OCR on March 18, 2026. The breach involved a network server and affected approximately 500 individuals. No business associate was involved. No further details on attack vector, threat actor, or remediation were disclosed in the OCR breach portal entry.
Affected (this filing): 500
HHS notified

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.