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

TruView BSI, LLC — July 2024 breach

Clustered 11 filings across 9 jurisdictions · filing window Apr 8, 2026 → Apr 15, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

11 filings

States

9

Affected · reported

20,318

First → last filing

Apr 8, 2026 → Apr 15, 2026

Merge confidence

100%

incident inc_708f1f963e9d433b · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. The filings describe unauthorized access. Intrusion Jul 18, 2024–Aug 15, 2024, discovered Mar 4, 2026 — the first regulatory filing landed 35 days later. 20,318 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 4 more. Notifications rolled out on a 7-day schedule across 11 filings beginning Apr 8, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
35days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
7days

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 clocksVermont⏱ VT AG >14 bdayMaine⏱ ME AG >30d · 35dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jul 18, 2024breach begins
Mar 4, 2026discovered
notification delay · 35 days
Apr 8, 2026first filing
Apr 15, 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 8VT AGVT AG noticefirst filing · 4 VT residentsday 0
  2. APR 8MA AGMA AG noticeno count statedday 0
  3. APR 8NH AGNH AG notice10 NH residentsday 0
  4. APR 8ME AGME AG notice15 ME residentsday 0
  5. APR 8IN AGIN AG noticestates nationwide total 20,318day 0
  6. APR 8MT AGMT AG notice11 MT residentsday 0
  7. APR 8IN AGIN AG noticestates nationwide total 20,318day 0
  8. APR 8CA AGCA AG noticeno count statedday 0
  9. APR 8NE AGNE AG notice14 NE residentsday 0
  10. APR 10TX AGTX AG noticestates nationwide total 20,318+2d
  11. APR 15ME AGME AG noticemost recent · 15 ME residents+7d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jul 18, 2024 – Aug 15, 2024
VT AG
Discovered
Mar 4, 2026· 594d undetected
VT AG + NH AG + ME AG +4
Data types
Financial · Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
VT AG + MA AG + NH AG +5
Attack vector
Unauthorized Access
VT 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)

20,318

Sum of filed state slices

795· 3.9% of stated

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

US20,318
TX702
IN39
ME15
NE14
MT11
NH10
VT4

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

7 days

Cadence

~1 / 0.7d

vs. multi-state median

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