Spiraledge, Inc.
bd_6cc466ec94653061 · schema v1 · pii pii-v1
Full breach record for Spiraledge, Inc. →Spiraledge, Inc. reported a data breach to the Oregon Attorney General. The breach was reported on 2017-01-12. 426,623 individuals were affected.
J jump to incidentP pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
Jan 12, 2017
Filed
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Linked disclosures
Why this link?Regulatory filings (5) · sorted by filing gap
- California State AGbd_3542cadf5740d1a72017-01-12Verified
- Massachusetts State AGbd_869a6fc8b3a3e5b92017-01-12Verified
- Washington State AGbd_a7ef1cdcd01a568f2017-01-12Verified
- Hawaii State AGbd_04680317a3d78f602017-01-19 · +7dVerified
Show 1 more filing ↓Show fewer ↑up to 8d gap
- New Hampshire State AGbd_8cd5f5eb95f5137d2017-01-20 · +8dVerified
Filing propagation · 6 filings · 6 states
View merged incident ↗Pattern: first filing Jan 12 (CA), last Jan 20 (NH) — a 8-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.