How This Briefing Works
This report opens with key findings, then maps the gaps between what Instapage 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 cookie behavior, heatmap data collection, and advertising pixel execution not yet observed by BLACKOUT scanner
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
Recommended Actions for Instapage
- →- Audit all advertising pixels deployed on Instapage landing pages and verify each is gated behind proper consent management. - Review the built-in heatmap data collection scope and determine whether mouse movement, scroll depth, and click tracking require separate consent under your applicable privacy regulations. - Assess third-party heatmap integrations (Crazy Egg, Mouseflow) for redundant data collection and ensure each tool is disclosed in your privacy policy. - Verify that approximate location data collection is disclosed and has a documented legal basis, particularly for EU visitors. - Map the complete data flow from landing page to CRM to ensure no unauthorized data sharing occurs through automated integrations.
Negotiation Leverage
- →When negotiating with Instapage, request documentation of all data collected by the platform's JavaScript tag versus data collected by third-party pixels deployed on pages. Ask for clarity on data retention periods for heatmap recordings, visitor behavioral data, and form submission records. Key contractual protections should include restrictions on Instapage's use of aggregated heatmap and behavioral data for product development or benchmarking, data portability guarantees for all lead and analytics data, and clear data deletion timelines upon account termination. Press for details on how approximate location data is derived, stored, and whether it is shared with any third parties. Negotiate for the ability to disable built-in heatmaps independently of other analytics features if consent requirements dictate it.
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
15 detection signatures across scripts, domains, cookies, and network endpoints