How This Briefing Works
This report opens with key findings, then maps the gaps between what Sourcepoint 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”
No runtime behavioral analysis completed. CDT browser forensics needed to verify: (1) pre-consent network requests by Sourcepoint JavaScript, (2) consent banner rendering behavior and dark pattern indicators, (3) TCF string accuracy and completeness, (4) 'Consent or Pay' implementation — does tracking activate before payment confirmation, (5) A/B test data collection scope, (6) cross-publisher consent data aggregation practices.
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use Sourcepoint
- →Audit consent banner A/B tests for dark pattern characteristics (manipulative button placement, color, copy)
- →Review 'Consent or Pay' implementation against ICO and EDPB guidance on freely-given consent
- →Verify TCF string accuracy against actual visitor consent choices
- →Assess whether Sourcepoint's consent optimization recommendations prioritize revenue over informed choice
- →Evaluate cross-publisher consent data sharing in Sourcepoint's privacy policy
If You're Evaluating Sourcepoint
- →Independent scanner verification of pre-consent network behavior
- →Legal review of 'Consent or Pay' consent validity under GDPR 'freely given' requirement
- →Compare consent rates with and without Sourcepoint optimization to quantify manipulation effect
- →Assess alternative CMPs without revenue optimization conflicts of interest
Negotiation Leverage
- →Sourcepoint's business model creates a structural conflict: the consent tool is financially incentivized to maximize consent for ad revenue, not protect visitor choice
- →'Consent or Pay' model is under active regulatory scrutiny — if invalidated, all consent collected under this model becomes void
- →A/B testing consent banners to maximize acceptance is consent signal engineering, not compliance
- →Cross-publisher consent data gives Sourcepoint information asymmetry over its own customers
- →Request disclosure of all A/B test metrics, consent rate optimization targets, and cross-publisher data aggregation practices
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
77 detection signatures across scripts, domains, cookies, and network endpoints