Confirmed breach. Intrusion Sep 4, 2020, discovered Oct 28, 2020 — the first regulatory filing landed 15 days later. 1 individuals reported across the linked filings.
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.
Regulatory clocksMaine✓ ME AG ≤30d · 15dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
1
Data types
2
Identity (basic) · Financial credentials
Jurisdictions
1
ME
Linked filings
1
all State AG
Sensitive data
financial_credentials
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Sep 4, 2020
When the intrusion reportedly occurred, per the linked filings
T3 Micro, Inc. experienced an external system breach on September 4, 2020, which was discovered on October 28, 2020. The breach affected one Maine resident. The information compromised included names combined with financial account numbers or credit/debit card numbers and their associated access codes.
Affected (this filing): 1
ME AG ≤30d · 15d
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.