How This Briefing Works
This report opens with key findings, then maps the gaps between what Branch 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
“Requires claims extraction via CDT”
Live website analysis pending
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
Recommended Actions for Branch
- →- Audit Branch SDK privacy controls and ensure Do-Not-Track flags are properly configured for users who have not consented to tracking. - Evaluate NativeLink pasteboard access against your consent framework and consider whether clipboard-based attribution aligns with your privacy posture. - Review all active third-party integrations and verify that data processing agreements cover each partner receiving user data through Branch. - Implement independent attribution validation to cross-reference Branch's credit assignments against server-side conversion data. - Assess concentration risk from unified linking and attribution, and document contingency procedures for Branch service disruptions.
Negotiation Leverage
- →Leverage: Branch competes directly with Adjust, AppsFlyer, Singular, and Kochava for attribution, and with Firebase Dynamic Links and URL shorteners for deep linking. The unified linking-plus-attribution value proposition creates switching costs, but individual capabilities can be replaced. Use the competitive landscape to negotiate data minimization and retention terms.
- →Key questions for Branch: (1) What specific data elements does NativeLink read from the pasteboard beyond the deep link URL? (2) Which third-party integrations require PII in plaintext, and what contractual protections exist for that data downstream? (3) Can we obtain audit logs showing which partners received our users' data through Branch integrations? (4) What is Branch's data retention period for device-level attribution data?
- →Contractual protections to seek: Explicit limitations on pasteboard data access scope; contractual requirement that Branch enforce data minimization with downstream integration partners; right to audit data flows to third-party partners; SLA guarantees covering both linking uptime and attribution data integrity; notification requirements for changes to NativeLink methodology or partner data sharing terms.
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
129 detection signatures across scripts, domains, cookies, and network endpoints