DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed8 filings · 2 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmoderate sensitivity
Merged incident · 8 filings

SAFETYCALL INTERNATIONAL — November 2020 breach

Clustered 8 filings across 2 jurisdictions · filing window Jul 16, 2021 → Oct 11, 2021. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

8 filings

States

2

Affected · reported

not comparable

First → last filing

Jul 16, 2021 → Oct 11, 2021

Merge confidence

100%

incident inc_c873b76de9244149 · merged by deterministic · confidence 100%

Part of the Netgain Networks supply-chain incident (2021) — at least 15 organizations filed notifications naming this third party.
Confirmed breach. Merged as one breach: 8 regulatory filings. The filings describe malware. Intrusion Nov 24, 2020–Dec 3, 2020, discovered Nov 24, 2020 — the first regulatory filing landed 234 days later. Data reported: Identity (basic), PII, and Health (basic). Notifications rolled out on a 87-day schedule across 8 filings beginning Jul 16, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
234days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
87days

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.

Incident timeline

Nov 24, 2020breach begins
Nov 24, 2020discovered
notification delay · 234 days
Jul 16, 2021first filing
Oct 11, 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. JUL 16MT AGMT AG noticefirst filing · 85 MT residentsday 0
  2. JUL 19CA AGCA AG noticeno count stated+3d
  3. AUG 6MT AGMT AG notice14 MT residents+21d
  4. AUG 6CA AGCA AG noticeno count stated+21d
  5. AUG 6MT AGMT AG notice45 MT residents+21d
  6. AUG 24CA AGCA AG noticeno count stated+39d
  7. OCT 11MT AGMT AG notice29 MT residents+87d
  8. OCT 11MT AGMT AG noticemost recent · 2 MT residents+87d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 24, 2020 – Dec 3, 2020
MT AG
Discovered
Nov 24, 2020
MT AG + CA AG
Data types
Health (basic) · Identity (basic) · PII
MT AG + CA AG
Attack vector
Third-Party / Supply Chain
MT AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

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 filing8 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 Jun 12, 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

87 days

Cadence

~1 / 12.4d

vs. multi-state median

10.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.