Clustered 2 filings across 2 jurisdictions · filing window Oct 12, 2023 → Oct 18, 2023. View entity profile → Other incidents for this victim →
incident inc_ce6ba060f1584f81 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Identity (basic) · Government ID · Financial account
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.
NH VT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 22, 2023
When the intrusion reportedly occurred, per the linked filings
Jan 22, 2023
Reported by VERMONT AG, NEW HAMPSHIRE AG filings
Clean Rentals Inc. notified consumers of a data security incident discovered on January 22, 2023, where an unauthorized third party accessed computer systems. Impacted data included names, addresses, SSNs, DOBs, driver's licenses, bank account/routing numbers, credit card info, and medical/health insurance information. The company engaged forensic experts and offered one year of identity monitoring services.
Clean Rentals Inc. notified the New Hampshire Attorney General on October 18, 2023, of a cybersecurity incident occurring on or around January 22, 2023. An unauthorized third party gained access to computer systems, potentially impacting the personal information of approximately 45 New Hampshire residents. The company engaged an incident response team and forensic experts, and is offering complimentary identity monitoring services to affected individuals. The investigation is ongoing.
Affected (this filing): 45
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.