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

Vanguard Associates

Clustered 3 filings across 1 jurisdiction · filing window Apr 11, 2014 → May 15, 2014. View entity profile → Other incidents for this victim →

✓ data types agreeMerge100%

Determination

Confirmed

Members

3 filings

States

1

Affected · reported

3

First → last filing

Apr 11, 2014 → May 15, 2014

Merge confidence

100%

incident inc_b1ff0e8a0b284e2a · merged by deterministic · confidence 100%

Massachusetts publishes one register entry per notified resident. The filings on this page are entries in the state's annual breach register, which records who filed and how many residents were notified — not where the breach occurred.
Filed with the Massachusetts data-breach register. 3 notifications covering 3 residents. The register records who filed and how many residents — not where the breach occurred.

Litigation Timing

Filing span
34days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.

Incident timeline

? — ?breach window unknown
Apr 11, 2014first filing
May 15, 2014most recent filing

No discovery date is recorded on any filing in this cluster, so the notification delay is not computable. Dashed segments fill in as filings merge.

Member cascade — every filing in this register batch

  1. APR 11MA AGMA AG noticefirst filing · 1 MA residentsday 0
  2. APR 30MA AGMA AG notice1 MA residents+19d
  3. MAY 15MA AGMA AG noticemost recent · 1 MA residents+34d
  4. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
—
Discovered
—
Data types
Financial account
MA AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

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

34 days

Cadence

~1 / 17d

vs. multi-state median

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