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

TIAA and TIAA Life

Clustered 2 filings across 2 jurisdictions · filing window Apr 2, 2018 → Apr 17, 2018. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge49%

Determination

Confirmed

Members

2 filings

States

2

Affected · reported

3

First → last filing

Apr 2, 2018 → Apr 17, 2018

Merge confidence

49%

incident inc_86f2005122994412 · merged by llm · confidence 49%

Confirmed breach. Merged as one breach: 2 regulatory filings. The filing describes unauthorized access. 3 individuals reported across the linked filings. Data reported: Government ID, Financial account, and Identity (basic). Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Filing span
15days

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.

Sensitive data

identity_government

Incident timeline

? — ?breach window unknown
Apr 2, 2018first filing
Apr 17, 2018most 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 about this breach

  1. APR 2MA AGMA AG noticefirst filing · 2 MA residentsday 0
  2. APR 17MT AGMT AG noticemost recent · 1 MT residents+15d
  3. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
—
Discovered
—
Data types
Financial account · Identity (basic) · Government ID
MA AG + MT AG
Attack vector
Unauthorized Access
MT 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 filing2 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
llm
Confidence
0.49 · below the 0.85 auto-merge floor
Audit
Every link edge records its method, confidence and model + prompt versions (49% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

15 days

vs. multi-state median

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