Jambav
bd_f15eb08cda29fbb1 · schema v1 · pii pii-v1
Full breach record for Jambav →2 incidents on fileJambav, Inc. reported a data breach to the Massachusetts Office of Consumer Affairs and Business Regulation. The breach was reported on 2019-12-23. 38,147 Massachusetts residents were affected. The report records the breach type as electronic.
J jump to incidentP pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
Dec 23, 2019
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 (8) · sorted by filing gap
- South Carolina State AGbd_aea6f12827799fb72019-12-23Verified
- Montana State AGbd_d7544e14d61d83d62019-12-22 · +1dVerified
- Hawaii State AGbd_81e0f9550ab1cef82019-12-20 · +3dVerified
- California State AGbd_eb98c9ae707ab1622019-12-19 · +4dCandidate
Show 4 more filings ↓Show fewer ↑up to 18d gap
- Oregon State AGbd_99023fc861bdb7672019-12-17 · +6dCandidate
- Delaware State AGbd_959ac0a9d7c37b732020-01-02 · +10dVerified
- Washington State AGbd_84a97823c016c2932019-12-13 · +10dVerified
- California State AGbd_863c7a6b7b60266e2020-01-10 · +18dVerified
Filing propagation · 9 filings · 8 states
View merged incident ↗Pattern: first filing Dec 13 (WA), last Jan 10 (CA) — a 28-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.