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

GRAYROBINSON, P.A. — March 2025 breach

Clustered 12 filings across 9 jurisdictions · filing window Apr 24, 2026 → May 7, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

12 filings

States

9

Affected · reported

65,113

First → last filing

Apr 24, 2026 → May 7, 2026

Merge confidence

100%

incident inc_2d2574ec8409424e · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings. The filings describe unauthorized access. Intrusion Mar 5, 2025–Mar 24, 2025, discovered Mar 24, 2025 — the first regulatory filing landed 396 days later (flagged late). 65,113 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 4 more. Notifications rolled out on a 13-day schedule across 12 filings beginning Apr 24, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
396days

Discovered → first regulatory filing

Discovery variance
385days

Range of discovered_at dates across filings

Filing span
13days

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 clocksMassachusetts✗ MA AG >90dCalifornia✗ CA 60-day late · 385dHIPAA✓ HHS notifiedSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 5, 2025breach begins
Mar 24, 2025discovered · members disagree
notification delay · 396 days
Apr 24, 2026first filing
May 7, 2026most 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. APR 24IN AGIN AG noticefirst filing · states nationwide total 65,113day 0
  2. APR 24NE AGNE AG noticeno count statedday 0
  3. APR 24MT AGMT AG notice41 MT residentsday 0
  4. APR 24NE AGNE AG noticeno count statedday 0
  5. APR 24HHS OCRHHS OCR noticestates nationwide total 54,131day 0
  6. APR 24MA AGMA AG notice107 MA residentsday 0
  7. APR 24CA AGCA AG noticeno count statedday 0
  8. APR 29NH AGNH AG notice34 NH residents+5d
  9. MAY 4CA AGCA AG noticeno count stated+10d
  10. MAY 5VT AGVT AG notice26 VT residents+11d
  11. MAY 7NH AGNH AG notice41 NH residents+13d
  12. MAY 7SC AGSC AG noticemost recent · 1,093 SC residents+13d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 5, 2025
IN AG
Discovered
Mar 24, 2025NE AG + MT AG + MA AG +2Apr 13, 2026NH AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PHI · PII
NE AG + MT AG + HHS OCR +5
Attack vector
Unauthorized Access
NE 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)

65,113

Sum of filed state slices

1,529· 2.3% of stated

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

US65,113
SC1,093
IN221
MA107
MT41
NH41
VT26

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 filing12 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
Reviewed
operator-reviewed Aug 23, 2026 · at least one link edge was human-adjudicated
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

13 days

Cadence

~1 / 1.2d

vs. multi-state median

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