Clustered 2 filings across 2 jurisdictions · filing window Mar 24, 2021 → May 7, 2021. View entity profile → Other incidents for this victim →
incident inc_4aa2806bdf3e4c9b · merge_method deterministic · confidence 95%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Identity (basic) · Government ID
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.
CA ME
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Dec 27, 2020
When the intrusion reportedly occurred, per the linked filings
Dec 27, 2020
Reported by MAINE AG, CALIFORNIA AG filings
TradeSource, Inc. reported an external system breach that occurred and was discovered on December 27, 2020. The incident compromised the names and Social Security numbers of 35,070 individuals, including 396 residents of Maine. The company sent written notifications to those affected on March 22, 2021, and offered identity theft protection services.
Affected (this filing): 396
TradeSource, Inc., a staffing firm for the construction industry, experienced a data security incident on December 27, 2020. The breach potentially exposed full names, mailing addresses, birthdates, and Social Security numbers of individuals. The company engaged third-party forensic specialists, notified law enforcement, and enhanced network security. Credit monitoring and identity theft protection services were offered to affected individuals through IDX.
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.