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

DTiQ Technologies — December 2024 breach

Clustered 7 filings across 7 jurisdictions · filing window Jul 25, 2025 → Aug 7, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

7 filings

States

7

Affected · reported

4,693

First → last filing

Jul 25, 2025 → Aug 7, 2025

Merge confidence

100%

incident inc_4df57d75c23e4a93 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings. The filings describe unauthorized access. Intrusion Dec 31, 2024–Jan 12, 2025, discovered Jan 12, 2025 — the first regulatory filing landed 194 days later (flagged late). 4,693 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 1 more. Notifications rolled out on a 13-day schedule across 7 filings beginning Jul 25, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
194days

Discovered → first regulatory filing

Discovery variance
176days

Range of discovered_at dates across filings

Filing span
13days

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 >45 bdayCalifornia✗ CA 60-day late · 206dMaine✓ ME AG ≤30d · 30dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 31, 2024breach begins
Jan 12, 2025discovered · members disagree
notification delay · 194 days
Jul 25, 2025first filing
Aug 7, 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. JUL 25VT AGVT AG noticefirst filing · no count statedday 0
  2. AUG 6CA AGCA AG noticeno count stated+12d
  3. AUG 6IN AGIN AG noticestates nationwide total 4,693+12d
  4. AUG 6NH AGNH AG notice28 NH residents+12d
  5. AUG 6NE AGNE AG noticeno count stated+12d
  6. AUG 6ME AGME AG noticestates nationwide total 4,693+12d
  7. AUG 7MA AGMA AG noticemost recent · 488 MA residents+13d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 31, 2024 – Jan 12, 2025
VT AG
Discovered
Jan 12, 2025VT AG + CA AG + NH AG +1Jul 7, 2025ME AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PCI
VT AG + CA AG + NH AG +3
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)

4,693

Sum of filed state slices

538· 11.5% of stated

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

US4,693
MA488
NH28
IN20
ME2

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

13 days

Cadence

~1 / 2.2d

vs. multi-state median

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