Clustered 2 filings across 2 jurisdictions · filed Aug 26, 2022. View entity profile → Other incidents for this victim →
incident inc_887a2971418f4fd3 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Identity (basic)
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
Apr 29, 2022 → May 11, 2022
When the intrusion reportedly occurred, per the linked filings
May 11, 2022
Reported by CALIFORNIA AG filing
Jul 27, 2022
Reported by MAINE AG filing
Truly Nolen of America, Inc. reported a data breach affecting California residents. Unauthorized access occurred between April 29, 2022, and May 11, 2022, resulting in the exfiltration of personal information, including names. The company engaged forensic specialists, secured the network, notified federal law enforcement, and offered 12 months of credit monitoring via Experian.
Truly Nolen of America, Inc. experienced an external system breach (hacking) that occurred from April 29, 2022, to May 11, 2022, and was discovered on July 27, 2022. The breach affected 2 Maine residents, part of a larger group of 5,756 individuals. The compromised information included names and Social Security numbers. In response, the company provided written notification to the affected individuals on August 26, 2022, and offered 12 months of credit monitoring services through Experian.
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.