TrueFire
bd_837c562ff81a02ee · schema v1 · pii pii-v1
Full breach record for TrueFire →3 incidents on fileTrueFire LLC notified consumers of a data breach where unauthorized access to its website occurred between August 3, 2019, and January 14, 2020. The incident potentially exposed names, addresses, and payment card details (including security codes) entered during checkout. TrueFire discovered the breach on January 10, 2020, engaged forensic specialists, notified law enforcement, and provided credit monitoring guidance to affected individuals.
J jump to incidentP pin to compareR raw source
Incident timeline
Aug 3, 2019
Begins
Jan 10, 2020
Discovered
Mar 9, 2020
Filed
vs. sector median
3 wks faster
Linked disclosures
Why this link?Regulatory filings (3) · sorted by filing gap
- Massachusetts State AGbd_13c0c3be1552e35c2020-03-10 · +1dVerified
- California State AGbd_e89c77e7a5033b372020-03-10 · +1dVerified
- Indiana State AGbd_c92d5b8102f212162020-02-13 · +25dVerified
Filing propagation · 4 filings · 4 states
View merged incident ↗Pattern: first filing Feb 13 (IN), last Mar 10 (CA) — a 26-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.