How This Briefing Works
This report opens with key findings, then maps the gaps between what HighLevel 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
“Anonymous visitor tracking and retroactive identity linking”
Awaiting scanner verification of external-tracking.js behavior and cookie persistence mechanisms
pending
“White-label data processor transparency”
Need to confirm whether HighLevel is disclosed as sub-processor in agency privacy policies across deployments
pending
“Multi-tenant data isolation”
Cross-agency data separation within HighLevel infrastructure requires verification
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
Recommended Actions for HighLevel
- →- Check whether websites you interact with use HighLevel by inspecting for external-tracking.js scripts loaded from branded subdomains - Review privacy policies of agency-branded marketing platforms for HighLevel sub-processor disclosure - Be aware that anonymous browsing on HighLevel-powered sites is tracked and retroactively linked to your identity upon form submission - Assess multi-tenant data isolation risks given the shared infrastructure model across thousands of agencies - Monitor for Twilio/LC Phone telephony data being combined with web behavioral profiles
Negotiation Leverage
- →HighLevel's core risk is the white-label opacity model — the actual data processor is hidden behind agency branding, making informed consent structurally difficult. Key leverage points: (1) Anonymous visitor tracking with retroactive identity linking creates pre-consent behavioral dossiers. (2) White-label architecture means privacy policies often fail to disclose HighLevel as the sub-processor handling data. (3) Multi-tenant infrastructure serving thousands of agencies raises data isolation questions. (4) The platform's own CCPA-specific pixel documentation acknowledges regulatory exposure, suggesting awareness of consent gaps in the default configuration.
IOC Manifest
Indicators of compromise across 3 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
7 detection signatures across scripts, domains, cookies, and network endpoints