One linked filing — more sources may join as they report · filed Aug 31, 2020. View entity profile → Other incidents for this victim →
incident inc_9a98a3b5725b4da1 · merge_method deterministic
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Credentials · PII
CA
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jun 25, 2020
When the intrusion reportedly occurred, per the linked filings
Havenly, Inc. reported that an outside individual gained unauthorized access to a database containing usernames and hashed passwords of users on or around June 25, 2020. The affected data included first and last names, account usernames, and hashed passwords. No credit card numbers or billing addresses were stored or affected. Havenly logged out all users, forced password resets, and engaged a forensic firm on July 29, 2020.
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.