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

AMERICOLD REALTY TRUST, INC — October 2020 breach

Clustered 11 filings across 9 jurisdictions · filing window Jan 1, 2021 → Apr 12, 2021. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

9

Affected · reported

144,216

First → last filing

Jan 1, 2021 → Apr 12, 2021

Merge confidence

100%

incident inc_b7bb35c715cf4878 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. Intrusion Oct 29, 2020–Nov 16, 2020, discovered Nov 15, 2020 — the first regulatory filing landed 47 days later (flagged late). 144,216 individuals reported across the linked filings. Data reported: Government ID, Biometric, Identity (basic), and 7 more. Notifications rolled out on a 101-day schedule across 11 filings beginning Jan 1, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
47days

Discovered → first regulatory filing

Discovery variance
1days

Range of discovered_at dates across filings

Filing span
101days

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 >90dMaine✗ ME AG >90d · 108dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

authenticationbiometricfinancial_credentialsidentity_government

Incident timeline

Oct 29, 2020breach begins
Nov 15, 2020discovered · members disagree
notification delay · 47 days
Jan 1, 2021first filing
Apr 12, 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. JAN 1IL AGIL AG noticefirst filing · no count statedday 0
  2. MAR 4MT AGMT AG notice62 MT residents+62d
  3. MAR 4OR AGOR AG noticestates nationwide total 141,351+62d
  4. MAR 4IN AGIN AG noticestates nationwide total 141,351+62d
  5. MAR 4CA AGCA AG noticeno count stated+62d
  6. MAR 4WA AGWA AG notice3,337 WA residents+62d
  7. MAR 4MA AGMA AG notice1,216 MA residents+62d
  8. MAR 4ME AGME AG noticestates nationwide total 141,351+62d
  9. MAR 5NH AGNH AG notice63 NH residents+63d
  10. MAR 30CA AGCA AG noticeno count stated+88d
  11. APR 12ME AGME AG noticemost recent · states nationwide total 144,216+101d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 29, 2020 – Nov 16, 2020
OR AG
Discovered
Nov 15, 2020ME AGNov 16, 2020IL AG + MT AG + OR AG +4filings disagree on discovery
Data types
Authentication · Biometric · Credentials · Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PCI · PHI
MT AG + CA 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)

144,216

Sum of filed state slices

13,189· 9.1% of stated

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

US144,216
IN8,364
WA3,337
MA1,216
ME147
NH63
MT62

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

101 days

Cadence

~1 / 10.1d

vs. multi-state median

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