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

DialAmerica Marketing, Inc. — February 2021 breach

Clustered 10 filings across 10 jurisdictions · filing window Jan 1, 2022 → Apr 21, 2022. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

10

Affected · reported

192,930

First → last filing

Jan 1, 2022 → Apr 21, 2022

Merge confidence

100%

incident inc_8a3cd0efc5634426 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. Intrusion Feb 2, 2021–Feb 2, 2022, discovered Jul 4, 2021 — the first regulatory filing landed 181 days later (flagged late). 192,930 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 4 more. Notifications rolled out on a 110-day schedule across 10 filings beginning Jan 1, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
181days

Discovered → first regulatory filing

Discovery variance
215days

Range of discovered_at dates across filings

Filing span
110days

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 >90dMaine⏱ ME AG >30d · 61dSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Feb 2, 2021breach begins
Jul 4, 2021discovered · members disagree
notification delay · 181 days
Jan 1, 2022first filing
Apr 21, 2022most 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. JAN 1IL AGIL AG noticefirst filing · no count statedday 0
  2. APR 6OR AGOR AG noticestates nationwide total 192,930+95d
  3. APR 6MT AGMT AG notice67 MT residents+95d
  4. APR 6ME AGME AG noticestates nationwide total 192,930+95d
  5. APR 6SC AGSC AG notice13,178 SC residents+95d
  6. APR 6MA AGMA AG notice452 MA residents+95d
  7. APR 6WA AGWA AG notice621 WA residents+95d
  8. APR 6IN AGIN AG noticestates nationwide total 192,930+95d
  9. APR 11NH AGNH AG notice122 NH residents+100d
  10. APR 21CA AGCA AG noticemost recent · no count stated+110d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 2, 2021 – Jul 9, 2021
MT AG
Discovered
Jul 4, 2021IL AG + MT AG + SC AG +2Feb 4, 2022ME AGfilings disagree on discovery
Data types
Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PHI · PII
MT AG + ME AG + SC AG +3
Attack vector
Unauthorized Access
MT 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)

192,930

Sum of filed state slices

19,513· 10.1% of stated

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

US192,930
SC13,178
IN4,914
WA621
MA452
ME159
NH122
MT67

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

110 days

Cadence

~1 / 12.2d

vs. multi-state median

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