Clustered 4 filings across 4 jurisdictions · filing window Jan 5, 2024 → Mar 13, 2024. View entity profile → Other incidents for this victim →
incident inc_073ed0fc9612471d · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Identity (basic) · Government ID
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.
IN ME MT NH
all State AG
per-filing reported counts
State AGs report only their own residents; bars show per-filing counts.
Earliest sighting first · deep chronology in Litigation Timeline
Nov 25, 2023
When the intrusion reportedly occurred, per the linked filings
Nov 25, 2023
Reported by MAINE AG, NEW HAMPSHIRE AG filings
Quaker Window Products Co. experienced an external system breach on November 25, 2023, which was also the date of discovery. The breach compromised the names and Social Security numbers of 3 Maine residents. The company provided written notification to affected consumers on December 29, 2023, and offered 12 months of credit monitoring services through IDX.
Affected (this filing): 3
Quaker Window Products, Co reported a data breach to the Indiana Attorney General. The breach occurred on 2023-11-25 and was reported on 2024-01-17. 3 Indiana residents were affected. 1,408 individuals affected in total.
Affected (this filing): 1,408
Quaker Window Products, Co. reported a data breach to the Montana Attorney General. The breach was reported on 2024-03-12. The breach occurred on 11/25/2023. 1 Montana residents were affected.
Affected (this filing): 1
Quaker Window Products, Co. notified the NH AG of a data security incident on March 12, 2024. Unauthorized access occurred on Nov 25, 2023, affecting 1 NH resident's PII. The company engaged cybersecurity experts, reported to federal law enforcement, and offered identity protection services.
Affected (this filing): 1
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.