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

Divvy Up, Inc. — May 2020 breach

Clustered 15 filings across 8 jurisdictions · filing window May 3, 2021 → Aug 2, 2021. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

15 filings

States

8

Affected · reported

46,958

First → last filing

May 3, 2021 → Aug 2, 2021

Merge confidence

100%

incident inc_7f2a40f9cc8c4a37 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 15 regulatory filings. Intrusion May 10, 2020–Jun 18, 2021, discovered Mar 10, 2021 — the first regulatory filing landed 54 days later (flagged late). 46,958 individuals reported across the linked filings. Data reported: Financial account, Financial credentials, Identity (basic), and 2 more. Notifications rolled out on a 91-day schedule across 15 filings beginning May 3, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
54days

Discovered → first regulatory filing

Discovery variance
100days

Range of discovered_at dates across filings

Filing span
91days

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 clocksOregon✗ OR AG >45dWashington⏱ WA AG >30dMaine⏱ ME AG >30d · 55dFull clock table in Litigation Timeline

Sensitive data

financial_credentials

Incident timeline

May 10, 2020breach begins
Mar 10, 2021discovered · members disagree
notification delay · 54 days
May 3, 2021first filing
Aug 2, 2021most 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 3WA AGWA AG noticefirst filing · 1,137 WA residentsday 0
  2. MAY 3OR AGOR AG noticestates nationwide total 46,958day 0
  3. MAY 3MT AGMT AG notice113 MT residentsday 0
  4. MAY 3CA AGCA AG noticeno count statedday 0
  5. MAY 3WA AGWA AG notice1,137 WA residentsday 0
  6. MAY 3NH AGNH AG notice229 NH residentsday 0
  7. MAY 3IN AGIN AG noticestates nationwide total 46,958day 0
  8. MAY 4ME AGME AG noticestates nationwide total 46,958+1d
  9. MAY 4MA AGMA AG notice1,614 MA residents+1d
  10. JUL 30MA AGMA AG notice996 MA residents+88d
  11. JUL 30MT AGMT AG notice92 MT residents+88d
  12. JUL 30CA AGCA AG noticeno count stated+88d
  13. JUL 30ME AGME AG noticestates nationwide total 38,505+88d
  14. JUL 30IN AGIN AG noticestates nationwide total 38,505+88d
  15. AUG 2NH AGNH AG noticemost recent · 152 NH residents+91d
  16. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 1, 2020 – Mar 8, 2021
WA AG
Discovered
Mar 10, 2021WA AG + OR AG + MT AG +3Jun 18, 2021MT AG + CA AG + ME AGfilings disagree on discovery
Data types
Financial account · Financial credentials · Identity (basic) · PCI · PII
WA AG + MT AG + CA AG +3
Attack vector
Third-Party / Supply Chain
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)

46,958

Sum of filed state slices

4,087· 8.7% of stated

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

US46,958
MA1,614
WA1,137
IN809
NH229
ME185
MT113

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

91 days

Cadence

~1 / 6.5d

vs. multi-state median

11.4× 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.