Clustered 2 filings across 2 jurisdictions · filed Sep 15, 2017. View entity profile → Other incidents for this victim →
incident inc_c43f2eb81c744729 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Identity (basic) · Financial account
CA OR
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 26, 2016 → Sep 5, 2017
When the intrusion reportedly occurred, per the linked filings
Aug 1, 2017
Reported by CALIFORNIA AG filing
Bulletproof 360, Inc. disclosed a data breach affecting payment card information (name, card number, expiration, CVV) for customers who made online transactions between October 26, 2016, and September 5, 2017. An unknown third party compromised the e-commerce system by inserting unauthorized code. The company engaged a security firm, notified law enforcement, and removed the malicious code.
Bulletproof 360, Inc reported a data breach to the Oregon Attorney General. The breach was reported on 2017-09-15. The breach occurred during 10/26/2016 - 5/30/2017, 8/28/2017 - 9/5/2017. The breach was discovered on 2/23/20178/1/20179/5/2017. 35,716 individuals were affected. Notice was sent on 3/21/20179/15/2017.
Affected (this filing): 35,716
About this clustering
DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.