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

TRINITY UNIVERSAL INSURANCE COMPANY — July 2023 breach

Clustered 8 filings across 8 jurisdictions · filing window Feb 1, 2024 → Feb 12, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

8

Affected · reported

76,470

First → last filing

Feb 1, 2024 → Feb 12, 2024

Merge confidence

100%

incident inc_973e539df7264883 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings. The filings describe a physical incident. Intrusion Jul 7, 2023–Jul 10, 2023, discovered Jul 11, 2023 — the first regulatory filing landed 205 days later (flagged late). 76,470 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 3 more. Notifications rolled out on a 11-day schedule across 8 filings beginning Feb 1, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
205days

Discovered → first regulatory filing

Discovery variance
183days

Range of discovered_at dates across filings

Filing span
11days

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 clocksWashington✗ WA AG >90dOregon✓ OR AG ≤45dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jul 7, 2023breach begins
Jul 11, 2023discovered · members disagree
notification delay · 205 days
Feb 1, 2024first filing
Feb 12, 2024most 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. FEB 1IL AGIL AG noticefirst filing · no count statedday 0
  2. FEB 9DE AGDE AG noticeno count stated+8d
  3. FEB 9OR AGOR AG noticestates nationwide total 76,470+8d
  4. FEB 9CA AGCA AG noticeno count stated+8d
  5. FEB 9IN AGIN AG noticestates nationwide total 76,470+8d
  6. FEB 9WA AGWA AG noticestates nationwide total 31,701+8d
  7. FEB 10MA AGMA AG notice48 MA residents+9d
  8. FEB 12SC AGSC AG noticemost recent · 197 SC residents+11d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jul 7, 2023 – Jul 10, 2023
DE AG
Discovered
Jul 11, 2023IL AG + WA AGJan 10, 2024OR AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
DE AG + CA AG + WA AG +2

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)

76,470

Sum of filed state slices

10,772· 14.1% of stated

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

US76,470
IN6,248
WA4,279
SC197
MA48

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

11 days

Cadence

~1 / 1.6d

vs. multi-state median

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