Confirmed breach. Intrusion Feb 2, 2025, discovered Mar 13, 2025 — the first regulatory filing landed 27 days later. 780 individuals reported across the linked filings.
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 clocksLeak gap⏱ Leak >30dMaine✓ ME AG ≤30d · 27dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
780
Data types
—
Jurisdictions
2
IN ME
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Feb 2, 2025
When the intrusion reportedly occurred, per the linked filings
Plasser American Corporation experienced an external system breach (hacking) that occurred on February 2, 2025, and was discovered on March 13, 2025. The breach affected one Maine resident who was notified on April 9, 2025. The company offered 12 months of identity theft protection services through Experian IdentityWorks.
Affected (this filing): 1
ME AG ≤30d · 27d
🏎️Indiana State AGMost recentlinked via multistate filing link · 100%
Plasser American Corporation reported a data breach to the Indiana Attorney General. The breach occurred on 2025-02-02 and was reported on 2025-04-09. 3 Indiana residents were affected. 780 individuals affected in total.
Affected (this filing): 780
Leak >30d
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.