DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed10 filings · 10 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 10 filings

SafetyFirst — January 2026 breach

Clustered 10 filings across 10 jurisdictions · filed Jul 23, 2026 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

10

Affected · reported

141,230

First → last dated filing

Jul 23, 2026

Merge confidence

100%

incident inc_4c9414671aa34560 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. Intrusion Jan 16, 2026–Jan 19, 2026, discovered Jan 19, 2026. 141,230 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
65days

Range of discovered_at dates across filings

Filing span
0days

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 >90dCalifornia✗ CA 30-day late · 185dTexas✗ TX AG >30dSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jan 16, 2026breach begins
Jan 19, 2026discovered · members disagree
Jul 23, 2026first dated filing
—watching for filings

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing about this breach

  1. JUL 1IL AGIL AG noticefiling day not on record · no count stated—
  2. JUL 23SC AGSC AG noticefirst filing · 1,235 SC residentsday 0
  3. JUL 23NH AGNH AG notice230 NH residentsday 0
  4. JUL 23NE AGNE AG noticefiling day not on record · 195 NE residents—
  5. JUL 23OR AGOR AG noticestates nationwide total 141,230day 0
  6. JUL 23MA AGMA AG notice825 MA residentsday 0
  7. JUL 23IN AGIN AG noticestates nationwide total 141,230day 0
  8. JUL 23WA AGWA AG notice1,157 WA residentsday 0
  9. JUL 23CA AGCA AG noticeno count statedday 0
  10. JUL 23TX AGTX AG noticemost recent · states nationwide total 141,230day 0
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 16, 2026 – Jan 19, 2026
SC AG
Discovered
Jan 19, 2026SC AG + NH AG + NE AG +3Mar 25, 2026IL AG + TX AGfilings disagree on discovery
Data types
Identity (basic) · Government ID
IL AG + SC AG + NH AG +5
Attack vector
Unauthorized Access
SC 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)

141,230

Sum of filed state slices

9,983· 7.1% of stated

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

US141,230
TX4,504
IN1,837
SC1,235
WA1,157
MA825
NH230
NE195

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 filing10 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

0 days

Cadence

~1 / 0d

vs. multi-state median

20.0× faster

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.