DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
HHS OCRState AGConfirmed7 filings · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 7 filings

Cherry Street Services, Inc. — December 2023 breach

Clustered 7 filings across 7 jurisdictions · filing window Feb 29, 2024 → Apr 22, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

7 filings

States

7

Affected · reported

184,372

First → last filing

Feb 29, 2024 → Apr 22, 2024

Merge confidence

100%

incident inc_bf612ef2ba644044 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings. Intrusion Dec 21, 2023, discovered Dec 21, 2023 — the first regulatory filing landed 70 days later (flagged late). 184,372 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 5 more. Notifications rolled out on a 53-day schedule across 7 filings beginning Feb 29, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
70days

Discovered → first regulatory filing

Discovery variance
3days

Range of discovered_at dates across filings

Filing span
53days

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 >90d · 115dVermont✗ VT AG >45 bdayHIPAA✓ HHS notifiedMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Dec 21, 2023breach begins
Dec 21, 2023discovered · members disagree
notification delay · 70 days
Feb 29, 2024first filing
Apr 22, 2024most 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. FEB 29HHS OCRHHS OCR noticefirst filing · states nationwide total 181,820day 0
  2. APR 16IN AGIN AG noticestates nationwide total 184,372+47d
  3. APR 16MT AGMT AG notice1 MT residents+47d
  4. APR 17ME AGME AG noticestates nationwide total 184,372+48d
  5. APR 17VT AGVT AG noticeno count stated+48d
  6. APR 17MA AGMA AG notice7 MA residents+48d
  7. APR 22NH AGNH AG noticemost recent · 2 NH residents+53d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 21, 2023
IN AG
Discovered
Dec 21, 2023MT AG + VT AG + NH AGDec 24, 2023ME AGfilings disagree on discovery
Data types
Financial · Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PHI · PII
HHS OCR + MT AG + VT AG +3
Attack vector
Unauthorized Access
HHS OCR

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)

184,372

Sum of filed state slices

103· 0.1% of stated

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

US184,372
IN89
MA7
ME4
NH2
MT1

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

53 days

Cadence

~1 / 8.8d

vs. multi-state median

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