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

Arbor Associates Inc — April 2025 breach

Clustered 11 filings across 9 jurisdictions · filing window Jul 1, 2025 → Aug 12, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

9

Affected · reported

52,986

First → last filing

Jul 1, 2025 → Aug 12, 2025

Merge confidence

100%

incident inc_53098eae5d95481e · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. Intrusion Apr 15, 2025–Apr 17, 2025, discovered Apr 17, 2025 — the first regulatory filing landed 75 days later (flagged late). 52,986 individuals reported across the linked filings. Data reported: Health (basic), PHI, Identity (basic), and 1 more. Notifications rolled out on a 42-day schedule across 11 filings beginning Jul 1, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
75days

Discovered → first regulatory filing

Discovery variance
35days

Range of discovered_at dates across filings

Filing span
42days

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 clocksVermont✗ VT AG >45 bdayOregon✗ OR AG >45dTexas✗ TX AG >30dWashington⏱ WA AG >30dHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Incident timeline

Apr 15, 2025breach begins
Apr 17, 2025discovered · members disagree
notification delay · 75 days
Jul 1, 2025first filing
Aug 12, 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. JUL 1IL AGIL AG noticefirst filing · no count statedday 0
  2. JUL 3HHS OCRHHS OCR noticestates nationwide total 17,040+2d
  3. JUL 3WA AGWA AG notice9,005 WA residents+2d
  4. JUL 3MA AGMA AG notice589 MA residents+2d
  5. JUL 3MT AGMT AG notice29 MT residents+2d
  6. JUL 3CA AGCA AG noticeno count stated+2d
  7. JUL 17VT AGVT AG noticeno count stated+16d
  8. JUL 17OR AGOR AG noticestates nationwide total 46,081+16d
  9. AUG 8MT AGMT AG notice1 MT residents+38d
  10. AUG 8CA AGCA AG noticeno count stated+38d
  11. AUG 12TX AGTX AG noticemost recent · states nationwide total 52,986+42d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 15, 2025 – Apr 17, 2025
WA AG
Discovered
Apr 17, 2025WA AG + MT AG + CA AG +1May 22, 2025IL AG + OR AG + TX AGfilings disagree on discovery
Data types
Health (basic) · Identity (basic) · PHI · PII
IL AG + HHS OCR + WA AG +5
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)

52,986

Sum of filed state slices

11,168· 21.1% of stated

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

US52,986
WA9,005
TX1,545
MA589
MT29

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

42 days

Cadence

~1 / 4.2d

vs. multi-state median

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