Clustered 2 filings across 2 jurisdictions · filed Oct 28, 2022. View entity profile → Other incidents for this victim →
incident inc_5910ba53e18644eb · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Identity (basic) · Government ID · Financial
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 NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Aug 17, 2022 → Aug 22, 2022
When the intrusion reportedly occurred, per the linked filings
Aug 22, 2022
Reported by CALIFORNIA AG, NEW HAMPSHIRE AG filings
TaxSquad, a tax preparation service, notified California AG and affected individuals of a data breach involving unauthorized access to employee email accounts. The incident, discovered August 22, 2022, potentially exposed client names, DOBs, addresses, SSNs, and tax info. TaxSquad offered one year of Experian IdentityWorks credit monitoring.
TaxSquad reported a data security incident to the New Hampshire Attorney General on October 28, 2022. Suspicious activity was identified in its email environment on August 22, 2022. The incident involved the compromise of email accounts, potentially exposing personal information including names, dates of birth, addresses, Social Security numbers, and tax-related data of two New Hampshire residents. TaxSquad secured the accounts, engaged forensic investigators, and offered credit monitoring services.
Affected (this filing): 2
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.