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

OneTouchPoint, Inc. — April 2022 breach

Clustered 12 filings across 10 jurisdictions · filing window Jun 3, 2022 → Aug 26, 2022. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

12 filings

States

10

Affected · reported

4,112,892

First → last filing

Jun 3, 2022 → Aug 26, 2022

Merge confidence

100%

incident inc_b3466f23c59947ee · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings. Intrusion Apr 27, 2022–Apr 28, 2022, discovered Apr 28, 2022 — the first regulatory filing landed 36 days later (flagged late). 4,112,892 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 2 more. Notifications rolled out on a 84-day schedule across 12 filings beginning Jun 3, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
36days

Discovered → first regulatory filing

Discovery variance
78days

Range of discovered_at dates across filings

Filing span
84days

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 >30dMaine⏱ ME AG >30d · 54dHIPAA✓ HHS notifiedSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Apr 27, 2022breach begins
Apr 28, 2022discovered · members disagree
notification delay · 36 days
Jun 3, 2022first filing
Aug 26, 2022most 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. JUN 3DE AGDE AG noticefirst filing · no count statedday 0
  2. JUL 27MT AGMT AG notice74 MT residents+54d
  3. JUL 27HHS OCRHHS OCR noticestates nationwide total 4,112,892+54d
  4. JUL 27WA AGWA AG notice1,321 WA residents+54d
  5. JUL 27MA AGMA AG notice113,811 MA residents+54d
  6. JUL 27IN AGIN AG noticestates nationwide total 1,073,316+54d
  7. JUL 27OR AGOR AG noticestates nationwide total 1,073,316+54d
  8. JUL 27ME AGME AG noticestates nationwide total 1,073,316+54d
  9. JUL 28SC AGSC AG notice86,907 SC residents+55d
  10. AUG 1MT AGMT AG notice35 MT residents+59d
  11. AUG 12CA AGCA AG noticeno count stated+70d
  12. AUG 26ME AGME AG noticemost recent · states nationwide total 2,651,396+84d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 27, 2022
DE AG
Discovered
Apr 28, 2022DE AG + MT AG + WA AG +2Jun 3, 2022OR AG + ME AGJul 15, 2022ME AGfilings disagree on discovery
Data types
Health (basic) · Identity (basic) · Government ID · PHI · PII
DE AG + MT AG + SC AG +4
Attack vector
Ransomware
DE 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)

4,112,892

Sum of filed state slices

275,588· 6.7% of stated

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

US4,112,892
MA113,811
SC86,907
IN73,466
WA1,321
MT74
ME9

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

84 days

Cadence

~1 / 7.6d

vs. multi-state median

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