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

Bt&Co., P.A. — November 2024 breach

Clustered 3 filings across 3 jurisdictions · filing window Oct 6, 2025 → Nov 12, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

3 filings

States

3

Affected · reported

789

First → last filing

Oct 6, 2025 → Nov 12, 2025

Merge confidence

100%

incident inc_c2e230190de34c04 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 3 regulatory filings. Intrusion Nov 6, 2024–Nov 14, 2024, discovered Nov 13, 2024 — the first regulatory filing landed 327 days later (flagged late). 789 individuals reported across the linked filings. Data reported: Government ID, PII, and Identity (basic). Notifications rolled out on a 37-day schedule across 3 filings beginning Oct 6, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
327days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
37days

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 clocksMaine✗ ME AG >90d · 364dVermont✗ VT AG >45 bdayFull clock table in Litigation Timeline

Incident timeline

Nov 6, 2024breach begins
Nov 13, 2024discovered
notification delay · 327 days
Oct 6, 2025first filing
Nov 12, 2025most 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. OCT 6IN AGIN AG noticefirst filing · states nationwide total 789day 0
  2. NOV 12ME AGME AG notice1 ME residents+37d
  3. NOV 12VT AGVT AG noticemost recent · no count stated+37d
  4. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 6, 2024
IN AG
Discovered
Nov 13, 2024· 7d undetected
ME AG + VT AG
Data types
Identity (basic) · PII
ME AG + VT AG
Attack vector
Phishing
ME 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)

789

Sum of filed state slices

2· 0.3% of stated

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

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

37 days

Cadence

~1 / 18.5d

vs. multi-state median

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