Confirmed breach. Intrusion Oct 10, 2020–Mar 15, 2021, discovered Jul 23, 2021 — the first regulatory filing landed 13 days later. 11 individuals reported across the linked filings.
incident inc_0b69976b237347ac · merge_method human · confidence 100%
Litigation Timing
Notification delay
13days
Discovered → first regulatory filing
Filing span
1days
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.
Regulatory clocksMaine✓ ME AG ≤30d · 14dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
11
Data types
—
Jurisdictions
2
ME MT
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Oct 10, 2020
When the intrusion reportedly occurred, per the linked filings
Great Performances/ Artists as Waitresses, Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2021-08-05. The breach occurred from 10/10/2020 to 3/15/2021. 2 Montana residents were affected.
Affected (this filing): 2
🦞Maine State AGMost recentlinked via operator-confirmed · 100%
Great Performances/Artists as Waitresses, Inc. reported a phishing incident that occurred between October 10, 2020, and March 15, 2021. The breach was discovered on July 23, 2021. The incident affected 9 Maine residents, exposing their names and Social Security numbers. The company offered 12 months of credit monitoring and identity theft protection services through Experian.
Affected (this filing): 9
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.