DisclosureLens
UnknownInformationHigh

Jambav

bd_99023fc861bdb767 · schema v1 · pii pii-v1

Severity

High

Discovered

Nov 11, 2019

Filed

Dec 17, 2019

To disclose

5 weeks

Affected

6,100,000

Linked

9 filings

Confidence

95%
Full breach record for Jambav →2 incidents on file

Jambav Inc reported a data breach to the Oregon Attorney General. The breach was reported on 2019-12-17. The breach occurred during 11/11/2019. The breach was discovered on 11/11/2019. 6,100,000 individuals were affected. Notice was sent on 12/16/2019.

Oregon clock✓ OR AG ≤45d5 weeks discovery → filing
⚠ occurrence dateThe stored discovery date equals the breach OCCURRENCE date. Detection is normally later, so this OVERSTATES the delay — a 'late' verdict here may not be real.

Incident timeline

discovery → filing · 5 weeks / 36 days

Nov 11, 2019

Begins

Nov 11, 2019

Discovered

Dec 17, 2019

Filed

This filing is one of 9 about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (8) · sorted by filing gap

Show 4 more filings ↓up to 24d gap

Filing propagation · 9 filings · 8 states

View merged incident ↗
Washington State AGDec 13 · first
Oregon State AG+4d · this page
California State AG+6d
Hawaii State AG+7d
Montana State AG+9d
South Carolina State AG+10d
Massachusetts State AG+10d
Delaware State AG+20d
California State AG+28d

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

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.