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

TransGlobal Insurance Agency, Inc. — February 2026 breach

Clustered 14 filings across 10 jurisdictions · filing window Apr 16, 2026 → Jul 29, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

14 filings

States

10

Affected · reported

71,597

First → last filing

Apr 16, 2026 → Jul 29, 2026

Merge confidence

100%

incident inc_9fde31ad1f3e4064 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 14 regulatory filings. Intrusion Feb 4, 2026–Feb 24, 2026, discovered Feb 18, 2026 — the first regulatory filing landed 57 days later (flagged late). 71,597 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 2 more. Notifications rolled out on a 104-day schedule across 14 filings beginning Apr 16, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
57days

Discovered → first regulatory filing

Discovery variance
6days

Range of discovered_at dates across filings

Filing span
104days

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 >45dTexas✗ TX AG >30dMaine⏱ ME AG >30d · 69dWashington⏱ WA AG >30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 4, 2026breach begins
Feb 18, 2026discovered · members disagree
notification delay · 57 days
Apr 16, 2026first filing
Jul 29, 2026most 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. APR 16NE AGNE AG noticefirst filing · no count statedday 0
  2. APR 16IN AGIN AG noticestates nationwide total 71,597day 0
  3. APR 16IN AGIN AG noticestates nationwide total 71,597day 0
  4. APR 29CA AGCA AG noticeno count stated+13d
  5. APR 30ID AGID AG notice16 ID residents+14d
  6. MAY 4ME AGME AG noticestates nationwide total 71,597+18d
  7. MAY 5WA AGWA AG notice1,880 WA residents+19d
  8. MAY 5OR AGOR AG noticestates nationwide total 71,597+19d
  9. MAY 5NH AGNH AG notice153 NH residents+19d
  10. MAY 6TX AGTX AG noticestates nationwide total 71,597+20d
  11. JUL 20ID AGID AG noticeno count stated+95d
  12. JUL 20CA AGCA AG noticeno count stated+95d
  13. JUL 21VT AGVT AG notice28 VT residents+96d
  14. JUL 29OR AGOR AG noticemost recent · states nationwide total 71,597+104d
  15. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 18, 2026
NE AG
Discovered
Feb 18, 2026ID AGFeb 19, 2026OR AGFeb 24, 2026NE AG + CA AG + ID AG +5filings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PCI · PII
NE AG + ID AG + CA AG +5
Attack vector
Unauthorized Access
NE 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)

71,597

Sum of filed state slices

6,668· 9.3% of stated

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

US71,597
TX4,425
WA1,880
NH153
IN88
ME78
VT28
ID16

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

104 days

Cadence

~1 / 8d

vs. multi-state median

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