DisclosureLens
State AGConfirmed4 filings · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 4 filings

Minted, Inc. — May 2020 breach

Clustered 4 filings across 4 jurisdictions · filing window May 27, 2020 → May 28, 2020. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

4 filings

States

4

Affected · reported

4,280,000

First → last filing

May 27, 2020 → May 28, 2020

Merge confidence

100%

incident inc_fe301df6ac00430b · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings. The filings describe unauthorized access. Intrusion May 6, 2020, discovered May 15, 2020 — the first regulatory filing landed 12 days later. 4,280,000 individuals reported across the linked filings. Data reported: Authentication, Credentials, and Identity (basic). Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
12days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
1days

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 ≤30dOregon✓ OR AG ≤45dCalifornia✓ CA 60-day OK · 13dFull clock table in Litigation Timeline

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.

Minted, Inc. data breach (2020) — filings in 4 jurisdictions, May 2020 · DisclosureLens