SafetyFirst
bd_d59ad81fdec3e96e · schema v1 · pii pii-v1
Full breach record for SafetyFirst →2 incidents on fileSafetyfirst Systems, LLC experienced unauthorized access to a limited portion of its environment between January 16 and January 19, 2026. The incident was discovered on January 19, 2026, via log review. The company secured the compromise, engaged third-party forensic experts, and notified law enforcement. Personal information, including names, may have been accessed. 196 Rhode Island residents were affected. The company is offering complimentary credit monitoring and fraud assistance services.
J jump to incidentP pin to compareR raw source
Incident timeline
Jan 16, 2026
Begins
Jan 19, 2026
Discovered
Jul 23, 2026
Filed
Linked disclosures
Why this link?Regulatory filings (8) · sorted by filing gap
- South Carolina State AGbd_040d0e18b0e6fc0b2026-07-23Verified
- New Hampshire State AGbd_440e40e75b8e3bab2026-07-23Verified
- Nebraska State AGbd_50b680190ffb752e2026-07-23Verified
- Oregon State AGbd_52833391eb61f3fd2026-07-23Verified
Show 4 more filings ↓Show fewer ↑up to 22d gap
- Massachusetts State AGbd_60c66a4e1edccb922026-07-23Candidate
- Washington State AGbd_bc745a0679daa31f2026-07-23Verified
- Texas State AGbd_dff0e099643dee8d2026-07-23Verified
- Illinois State AGbd_03fb70879d50edd32026-07-01 · +22dVerified
Filing propagation · 9 filings · 9 states
View merged incident ↗Pattern: first filing Jul 1 (IL), last Jul 23 (CA) — a 22-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.