PULAU Corporation reported a data breach to the Montana Attorney General. The breach was reported on 2020-08-28. The breach occurred from 6/11/2020 to 6/29/2020. 4 Montana residents were affected.
Affected (this filing): 4
Clustered 2 filings across 2 jurisdictions · filed Aug 28, 2020. View entity profile → Other incidents for this victim →
incident inc_f29958bd6a7e4c3e · merge_method deterministic · confidence 100%
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
CA MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jun 11, 2020
When the intrusion reportedly occurred, per the linked filings
PULAU Corporation reported a data breach to the Montana Attorney General. The breach was reported on 2020-08-28. The breach occurred from 6/11/2020 to 6/29/2020. 4 Montana residents were affected.
Affected (this filing): 4
PULAU Corporation notified individuals of unauthorized access to its network between June 11 and June 29, 2020. An external party acquired employment-related records containing personal information including names, contact info, dates of birth, government-issued IDs (SSN, passport, driver's license), financial account info, online credentials, and health-related information. The company engaged security experts, coordinated with law enforcement, and secured systems. Affected individuals were offered two years of identity restoration and credit monitoring.
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.