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

Professional Business Systems, Inc. — December 2020 breach

Clustered 7 filings across 7 jurisdictions · filing window Jan 1, 2021 → Jul 6, 2021. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

7 filings

States

7

Affected · reported

1,210,688

First → last filing

Jan 1, 2021 → Jul 6, 2021

Merge confidence

100%

incident inc_e39ea4885ade4496 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings. Intrusion Dec 25, 2020, discovered Dec 30, 2020 — the first regulatory filing landed 2 days later (flagged late). 1,210,688 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 7 more. Notifications rolled out on a 186-day schedule across 7 filings beginning Jan 1, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
2days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
186days

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 · 183dMassachusetts✓ MA credit monitoring dueHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

authenticationidentity_government

Incident timeline

Dec 25, 2020breach begins
Dec 30, 2020discovered
notification delay · 2 days
Jan 1, 2021first filing
Jul 6, 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. JUL 1MT AGMT AG noticeno count stated+181d
  3. JUL 1ME AGME AG noticestates nationwide total 1,210,688+181d
  4. JUL 1CA AGCA AG noticeno count stated+181d
  5. JUL 1MA AGMA AG notice1,318 MA residents+181d
  6. JUL 1HHS OCRHHS OCR noticestates nationwide total 1,210,688+181d
  7. JUL 6NH AGNH AG noticemost recent · states nationwide total 1,210,688+186d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 25, 2020
ME AG
Discovered
Dec 30, 2020· 5d undetected
IL AG + MT AG + ME AG +1
Data types
Authentication · Credentials · Employment · Financial · Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PHI
MT AG + ME AG + CA AG +3
Attack vector
Ransomware
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)

1,210,688

Sum of filed state slices

1,776· 0.1% of stated

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

US1,210,688
MA1,318
NH284
ME174

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

186 days

Cadence

~1 / 31d

vs. multi-state median

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