How This Briefing Works
This report opens with key findings, then maps the gaps between what Bloomreach discloses and what BLACKOUT observed at runtime. From there: what it means for your organization, what to do about it, and the detection data and evidence underneath.
Key Findings
Analysis pending. Findings will appear here once intelligence collection is complete.
Claims vs. Observed Behavior
pending
“Awaiting scanner verification”
Runtime behavior not yet observed
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
Recommended Actions for Bloomreach
- →• Map all data flows between your commerce platform and Bloomreach — understand exactly what historical data was imported and what syncs in real-time • Audit Bloomreach cookie configuration to determine if third-party or first-party mode is active, and whether server-side cookie extensions are circumventing browser privacy protections • Request documentation of Loomi AI decision logic for your account to understand how personalization decisions are made and attributed • Review server-to-server advertising integrations to determine what customer data is being shared with ad platforms • Establish data portability plan — ensure you can export all customer profiles and behavioral data if switching vendors
Negotiation Leverage
- →Key leverage: Bloomreach's value increases with data volume, meaning they are incentivized to retain customers — use this during renewal negotiations. Request contractual guarantees on data portability including full behavioral data export in standard formats. Ask for transparency on Loomi AI decision-making: what data inputs drive personalization, how attribution is calculated, and whether Bloomreach uses aggregated customer data to improve models that benefit competitors. Key questions: (1) What happens to ingested customer data after contract termination — deletion timeline and verification? (2) Does Loomi AI use anonymized/aggregated data from your account to train models for other customers? (3) Can server-side cookie tracking be disabled without degrading core functionality? Protections to negotiate: data deletion SLA post-termination, restriction on cross-customer model training with your data, right to audit AI decision logic, contractual commitment to respect browser privacy signals.
Runtime Detections
BLACKOUT observed this vendor's JavaScript executing in a live browser and classified each hostile behavior using our BTI-C (Behavioral Threat Intelligence — Capability) taxonomy. These are not theoretical risks — each code below was triggered by something we watched this vendor's code actually do.
Evasion infrastructure, auditor bypass
Keystroke/mouse tracking
Impact: CDP unifies behavioral data from website, email, SMS, mobile app, and advertising channels into a single customer profile. Commerce platform integrations download complete historical customer data and maintain real-time sync via webhooks.
Full session replay
Identity stitching
Ignoring CMP signals
Impact: Server-side cookie solutions are specifically designed to circumvent browser privacy protections (Safari ITP, Mozilla ETP), extending tracking persistence beyond browser-intended limits. Cross-channel automated responses may fire before channel-specific consent is validated.
Device identification
IOC Manifest
Indicators of compromise across 4 categories. Use for detection rules, CSP policies, or Pi-hole blocklists.
Ecosystem & Supply Chain
Evidence Artifacts
Artifacts collected during analysis, available with evidence-tier access.
Complete network capture with all requests and responses
155 detection signatures across scripts, domains, cookies, and network endpoints