How This Briefing Works
This report opens with key findings, then maps the gaps between what Selligent 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 Analysis
“Claims extraction pending”
Awaiting scanner verification. Runtime behavioral analysis needed to confirm: (1) exact cookie taxonomy and pre-consent deployment behavior, (2) JavaScript payload size and execution patterns, (3) third-party network calls initiated by Selligent scripts, (4) data exfiltration endpoints and payload contents, and (5) tag manager interaction patterns when loaded via GTM or Tealium.
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
Recommended Actions for Selligent
- →- Audit Selligent cookie deployment timing relative to consent management platform signals to verify no pre-consent data collection occurs - Map all active Selligent integrations and API connectors to understand the full data distribution footprint across your marketing stack - Request Selligent's complete sub-processor list and verify each entity's data handling practices align with your privacy commitments - Review Selligent Cortex AI data retention policies and confirm behavioral profiling aligns with your published privacy notice - Conduct independent HAR capture during page load to verify Selligent's actual runtime network calls match their documented behavior
Negotiation Leverage
- →Selligent's primary leverage point is the gap between its privacy-centric European branding and its actual runtime data collection capabilities. When negotiating: (1) Demand a complete data flow diagram showing every endpoint Selligent scripts contact during page load, (2) Require contractual commitments on pre-consent behavior -- specifically that no cookies are set and no behavioral data is captured before explicit visitor consent, (3) Negotiate data retention limits below the default 365-day third-party cookie window, (4) Request audit rights for the Cortex AI profiling engine to verify what inferences are being made from your visitors' behavioral data, and (5) Ensure your DPA explicitly covers all Marigold subsidiary entities that may process data flowing through Selligent integrations. The Marigold acquisition history (multiple brand consolidations) creates ambiguity about which corporate entity controls data -- use this as leverage to demand clarity.
IOC Manifest
Indicators of compromise across 3 categories. Use for detection rules, CSP policies, or Pi-hole blocklists.
No indicators in this category
Ecosystem & Supply Chain
Evidence Artifacts
Artifacts collected during analysis, available with evidence-tier access.
Complete network capture with all requests and responses
4 detection signatures across scripts, domains, cookies, and network endpoints