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

Garden of Life, LLC — July 2024 breach

Clustered 11 filings across 11 jurisdictions · filing window Jan 1, 2025 → Nov 13, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

11 filings

States

11

Affected · reported

43,219

First → last filing

Jan 1, 2025 → Nov 13, 2025

Merge confidence

100%

incident inc_db9428de5fb44051 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. The filings describe hacking. Intrusion Jul 1, 2024–Dec 18, 2024, discovered Dec 18, 2024 — the first regulatory filing landed 14 days later. 43,219 individuals reported across the linked filings. Data reported: PCI, Financial account, Identity (basic), and 2 more. Notifications rolled out on a 316-day schedule across 11 filings beginning Jan 1, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
14days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
316days

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 ≤30d · 30dCalifornia✓ CA 60-day OK · 30dWashington✓ WA AG ≤30dFull clock table in Litigation Timeline

Sensitive data

financial_credentials

Incident timeline

Jul 1, 2024breach begins
Dec 18, 2024discovered
notification delay · 14 days
Jan 1, 2025first filing
Nov 13, 2025most 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. JAN 1IL AGIL AG noticefirst filing · no count statedday 0
  2. JAN 17MA AGMA AG notice1,295 MA residents+16d
  3. JAN 17NE AGNE AG noticeno count stated+16d
  4. JAN 17ME AGME AG noticestates nationwide total 43,219+16d
  5. JAN 17CA AGCA AG noticeno count stated+16d
  6. JAN 17WA AGWA AG notice1,082 WA residents+16d
  7. JAN 17NH AGNH AG notice354 NH residents+16d
  8. JAN 17MT AGMT AG notice173 MT residents+16d
  9. JAN 17IN AGIN AG noticestates nationwide total 43,219+16d
  10. JAN 31OR AGOR AG noticestates nationwide total 43,219+30d
  11. NOV 13MD AGMD AG noticemost recent · 788 MD residents+316d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jul 8, 2024
NE AG
Discovered
Dec 18, 2024· 163d undetected
IL AG + NE AG + ME AG +6
Data types
Financial account · Financial credentials · Identity (basic) · PCI · PII
MA AG + NH AG + ME AG +4
Attack vector
Unauthorized Access
ME 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)

43,219

Sum of filed state slices

4,572· 10.6% of stated

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

US43,219
MA1,295
WA1,082
MD788
IN626
NH354
ME254
MT173

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

316 days

Cadence

~1 / 31.6d

vs. multi-state median

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