All incidents View linkage analytics →Get the evidence package — $79

Confirmed3 filings · 2 statesUnverified claimConfirmedEnforcedhigh sensitivity

Merged incident · 3 filings

90 Degree Benefits Wisconsin — January 2022 breach

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

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

3 filings

States

Affected · reported

—

First → last filing

Apr 21, 2022 → Jun 10, 2022

Merge confidence

100%

incident inc_f31ad9ea29274d70 · merged by deterministic · confidence 100%

Confirmed breach. One breach, 3 legal records. Intrusion Jan 28, 2022–Feb 27, 2022, discovered Feb 27, 2022 — the first regulatory filing landed 53 days later. Notifications rolled out on a 50-day schedule across 3 filings beginning Apr 21, 2022. This page is the deduped roll-up; each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

53days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Filing span

50days

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.

Sensitive data

identity_government

Incident timeline

Jan 28, 2022breach begins

Feb 27, 2022discovered

notification delay · 53 days

Apr 21, 2022first filing

Jun 10, 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

APR 21DE AGDE AG noticefirst filing · no count statedday 0
JUN 9DE AGDE AG noticeno count stated+49d
JUN 10CA AGCA AG noticemost recent · no count statedauto-linked+50d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Feb 27, 2022
Discovered: Feb 27, 2022
Data types: PII · Identity (basic) · Government ID
Attack vector: Unauthorized Access
Response: Launched an investigation with the assistance of a leading independent digital forensics firm · Took steps to secure our environment, including by implementing enhanced security measures · Notified the Federal Bureau of Investigation and are fully cooperating with their investigation

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

50 days

Cadence

~1 / 25d

vs. multi-state median

10.0× 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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.