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

© DisclosureLens — Every breach. Every angle.Report an error / Request removalTermsPrivacy

v0.1.0 · coverage growing weekly

YouthCare data breach (2020) · DisclosureLens

All incidents View linkage analytics →

Incident · single filing

YouthCare

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

Confirmed breach. 3,410 individuals reported across the linked filings.

incident inc_29ca97db11754253 · 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.

State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced

Affected (total reported)

3,410

Data types

—

Jurisdictions

1

WA

Linked filings

1

all State AG

Timeline

Earliest sighting first · deep chronology in Litigation Timeline

🌲Washington State AGFirst filing
Filed Sep 11, 2020bd_801cff6125522b5a
YouthCare, a non-profit/charity sector entity reported a ransomware incident to the Washington Attorney General. 3,410 Washington residents were affected.
Affected (this filing): 3,410

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.