Confirmed breach. Intrusion Feb 21, 2020, discovered Jul 28, 2020 — the first regulatory filing landed 91 days later (flagged late). 477 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 >90d · 91dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
477
Data types
—
Jurisdictions
1
ME
Linked filings
1
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Feb 21, 2020
When the intrusion reportedly occurred, per the linked filings
TrueFire LLC reported an external system breach that occurred on February 21, 2020, and was discovered on July 28, 2020. The breach affected 477 Maine residents. In response, the company offered affected individuals 12 months of credit monitoring and identity theft protection services through TransUnion.
Affected (this filing): 477
ME AG >90d · 91dME resident >60d · 91d
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.