Confirmed breach. Intrusion Sep 1, 2020–Dec 3, 2020, discovered Jan 15, 2021 — the first regulatory filing landed 150 days later (flagged late). 10 individuals reported across the linked filings.
incident inc_b36fb2be8c2a4615 · merge_method human · confidence 100%
Litigation Timing
Notification delay
150days
Discovered → first regulatory filing
Filing span
0days
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.
Regulatory clocksMaine✗ ME AG >90d · 150dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
10
Data types
2
Identity (basic) · Government ID
Jurisdictions
2
ME MT
Linked filings
2
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Sep 1, 2020 → Dec 3, 2020
When the intrusion reportedly occurred, per the linked filings
Tax Sheltered Compensation, Inc. experienced an external system breach (hacking) that occurred from September 1, 2020, to December 3, 2020. The breach was discovered on January 15, 2021. The compromised information includes names and Social Security numbers. Affected individuals were offered 12 months of identity monitoring services through Kroll.
Affected (this filing): 1
ME AG >90d · 150d
🦬Montana State AGMost recentlinked via operator-confirmed · 100%
Tax Sheltered Compensation, Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2021-06-14. The breach occurred from 9/1/2020 to 12/3/2020. 9 Montana residents were affected.
Affected (this filing): 9
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.