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

Taylor Ganson & Perrin — December 2021 breach

Clustered 8 filings across 5 jurisdictions · filing window Feb 22, 2022 → May 3, 2022. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

5

Affected · reported

10,840

First → last filing

Feb 22, 2022 → May 3, 2022

Merge confidence

100%

incident inc_2975db2db00e4bbf · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings. The filings describe unauthorized access. Intrusion Dec 14, 2021, discovered Jan 23, 2022 — the first regulatory filing landed 30 days later. 10,840 individuals reported across the linked filings. Data reported: Government ID, Financial account, PCI, and 5 more. Notifications rolled out on a 70-day schedule across 8 filings beginning Feb 22, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
30days

Discovered → first regulatory filing

Discovery variance
4days

Range of discovered_at dates across filings

Filing span
70days

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 clocksMaine⏱ ME AG >30d · 60dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Dec 14, 2021breach begins
Jan 23, 2022discovered · members disagree
notification delay · 30 days
Feb 22, 2022first filing
May 3, 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. FEB 22MA AGMA AG noticefirst filing · 8,767 MA residentsday 0
  2. FEB 22MT AGMT AG notice15 MT residentsday 0
  3. FEB 22IN AGIN AG noticestates nationwide total 6,317day 0
  4. FEB 28NH AGNH AG noticeno count stated+6d
  5. MAR 28ME AGME AG noticestates nationwide total 6,317+34d
  6. APR 1NH AGNH AG notice167 NH residents+38d
  7. APR 25ME AGME AG noticestates nationwide total 10,840+62d
  8. MAY 3NH AGNH AG noticemost recent · 135 NH residents+70d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 14, 2021
IN AG
Discovered
Jan 23, 2022MT AG + NH AGJan 27, 2022ME AGfilings disagree on discovery
Data types
Credentials · Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PCI · PII
MA AG + MT AG + NH AG +1
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)

10,840

Sum of filed state slices

9,099· 83.9% of stated

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

US10,840
MA8,767
NH167
ME145
MT15
IN5

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 filing8 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
Reviewed
operator-reviewed Jun 12, 2026 · at least one link edge was human-adjudicated
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

70 days

Cadence

~1 / 10d

vs. multi-state median

8.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.