DisclosureLens
State AGConfirmed8 filings · 8 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 8 filings

Nuna Baby Essentials, Inc. — March 2020 breach

Clustered 8 filings across 8 jurisdictions · filed Jan 21, 2022. View entity profile → Other incidents for this victim →

1 cross-filing discrepancyMerge100%

Determination

Confirmed

Members

8 filings

States

8

Affected · reported

21,799

First → last filing

Jan 21, 2022

Merge confidence

100%

incident inc_51970aea6aab44a3 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings. The filings describe hacking. Intrusion Mar 26, 2020–Apr 7, 2021, discovered Dec 22, 2021 — the first regulatory filing landed 30 days later. 21,799 individuals reported across the linked filings. Data reported: PCI, Financial account, Identity (basic), and 2 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
30days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
0days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delayno leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksOregon OR AG ≤45dMaine ME AG ≤30d · 30dCalifornia CA 60-day OK · 30dFull clock table in Litigation Timeline

Sensitive data

financial_credentials

Incident timeline

Mar 26, 2020breach begins
Dec 22, 2021discovered
notification delay · 30 days
Jan 21, 2022first filing
watching for filings

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

Member cascade — every filing about this breach

  1. JAN 21OR AGOR AG noticefirst filing · states nationwide total 21,799day 0
  2. JAN 21MT AGMT AG notice83 MT residentsday 0
  3. JAN 21MA AGMA AG notice816 MA residentsday 0
  4. JAN 21IN AGIN AG noticestates nationwide total 21,779day 0
  5. JAN 21WA AGWA AG notice816 WA residentsday 0
  6. JAN 21NH AGNH AG noticeno count statedday 0
  7. JAN 21ME AGME AG noticestates nationwide total 21,779day 0
  8. JAN 21CA AGCA AG noticemost recent · no count statedday 0
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 26, 2020Apr 7, 2021
OR AG
Discovered
Dec 22, 2021· 636d undetected
OR AG + MT AG + WA AG +3
Data types
Financial account · Financial credentials · Identity (basic) · PCI · PII
MT AG + MA AG + WA AG +3
Attack vector
Unauthorized Access
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)

21,799

Sum of filed state slices

2,042· 9.4% of stated

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

US21,799
MA816
WA816
IN198
ME129
MT83

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

0 days

Cadence

~1 / 0d

vs. multi-state median

20.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.