DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed10 filings · 10 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcritical sensitivity
Merged incident · 10 filings

Apria Healthcare LLC — April 2019 breach

Clustered 10 filings across 10 jurisdictions · filing window May 22, 2023 → May 31, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

10

Affected · reported

1,869,598

First → last filing

May 22, 2023 → May 31, 2023

Merge confidence

100%

incident inc_4f6ac37575fe4dfc · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. The filings describe unauthorized access. Intrusion Apr 4, 2019–Oct 10, 2021, discovered Sep 1, 2021 — the first regulatory filing landed 628 days later (flagged late). 1,869,598 individuals reported across the linked filings. Data reported: Biometric, Government ID, Financial, and 7 more. Notifications rolled out on a 9-day schedule across 10 filings beginning May 22, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
628days

Discovered → first regulatory filing

Discovery variance
30days

Range of discovered_at dates across filings

Filing span
9days

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.

Regulatory clocksWashington✗ WA AG >90dOregon✗ OR AG >45dMaine✗ ME AG >90d · 598dMassachusetts✓ MA credit monitoring dueSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

biometricidentity_government

Incident timeline

Apr 4, 2019breach begins
Sep 1, 2021discovered · members disagree
notification delay · 628 days
May 22, 2023first filing
May 31, 2023most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. MAY 22WA AGWA AG noticefirst filing · 69,686 WA residentsday 0
  2. MAY 22IN AGIN AG noticestates nationwide total 1,869,598day 0
  3. MAY 22OR AGOR AG noticestates nationwide total 1,869,598day 0
  4. MAY 22CA AGCA AG noticeno count statedday 0
  5. MAY 22MA AGMA AG notice24,429 MA residentsday 0
  6. MAY 22DE AGDE AG noticeno count statedday 0
  7. MAY 22ME AGME AG noticestates nationwide total 1,869,598day 0
  8. MAY 22MT AGMT AG notice5 MT residentsday 0
  9. MAY 23SC AGSC AG notice16,003 SC residents+1d
  10. MAY 31NH AGNH AG noticemost recent · 8,566 NH residents+9d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 5, 2019 – Oct 10, 2021
WA AG
Discovered
Sep 1, 2021WA AG + OR AG + CA AG +4Oct 1, 2021ME AGfilings disagree on discovery
Data types
Biometric · Credentials · Financial · Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PHI · PII
WA AG + MA AG + ME AG +5
Attack vector
Unauthorized Access
WA AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

1,869,598

Sum of filed state slices

167,872· 9.0% of stated

91% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US1,869,598
WA69,686
IN42,021
MA24,429
SC16,003
NH8,566
ME7,162
MT5

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing10 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Jun 12, 2026 · at least one link edge was human-adjudicated
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

9 days

Cadence

~1 / 1d

vs. multi-state median

1.0× faster

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. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.