DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
HHS OCRState AGConfirmed16 filings · 11 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 16 filings

ReproSource Fertility Diagnostics, Inc. — August 2021 breach

Clustered 16 filings across 11 jurisdictions · filing window Oct 8, 2021 → Feb 4, 2022. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

16 filings

States

11

Affected · reported

350,000

First → last filing

Oct 8, 2021 → Feb 4, 2022

Merge confidence

100%

incident inc_b4b53ce7b69f49d6 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 16 regulatory filings. Intrusion Aug 8, 2021–Aug 10, 2021, discovered Aug 8, 2021 — the first regulatory filing landed 61 days later (flagged late). 350,000 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 4 more. Notifications rolled out on a 119-day schedule across 16 filings beginning Oct 8, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
61days

Discovered → first regulatory filing

Discovery variance
2days

Range of discovered_at dates across filings

Filing span
119days

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 clocksMaine✗ ME AG >90d · 174dOregon✗ OR AG >45dWashington⏱ WA AG >30dSouth Carolina✓ SC CRA notice dueMassachusetts✓ MA credit monitoring dueHIPAA✓ HHS notifiedCalifornia✓ CA 60-day OK · 45dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 8, 2021breach begins
Aug 8, 2021discovered · members disagree
notification delay · 61 days
Oct 8, 2021first filing
Feb 4, 2022most 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. OCT 8MT AGMT AG noticefirst filing · 267 MT residentsday 0
  2. OCT 8SC AGSC AG notice1,788 SC residentsday 0
  3. OCT 8ME AGME AG notice102 affectedday 0
  4. OCT 8CA AGCA AG noticeno count statedday 0
  5. OCT 8WA AGWA AG noticestates nationwide total 7,781day 0
  6. OCT 8MA AGMA AG notice1,736 MA residentsday 0
  7. OCT 8DE AGDE AG noticeno count statedday 0
  8. OCT 8OR AGOR AG noticestates nationwide total 350,000day 0
  9. OCT 8HHS OCRHHS OCR noticestates nationwide total 253,774day 0
  10. OCT 8IN AGIN AG noticestates nationwide total 350,000day 0
  11. OCT 14NH AGNH AG notice173 NH residents+6d
  12. JAN 1IL AGIL AG noticeno count stated+85d
  13. JAN 27CA AGCA AG noticeno count stated+111d
  14. JAN 31ME AGME AG noticestates nationwide total 350,000+115d
  15. JAN 31OR AGOR AG noticestates nationwide total 350,000+115d
  16. FEB 4NH AGNH AG noticemost recent · 2,047 NH residents+119d
  17. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 8, 2021
MT AG
Discovered
Aug 8, 2021IL AGAug 10, 2021MT AG + SC AG + ME AG +5filings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PHI · PII
MT AG + SC AG + ME AG +6
Attack vector
Ransomware
MT 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)

350,000

Sum of filed state slices

8,751· 2.5% of stated

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

US350,000
NH2,047
SC1,788
MA1,736
WA1,085
ME989
IN839
MT267

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 filing16 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

119 days

Cadence

~1 / 7.9d

vs. multi-state median

14.9× slower

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.