All Vendors
revenue_intelligence

Justcall

Justcall revenue intelligence platform begins browser-side execution before consent capture completes.

6 IOCs9 detections100% pre-consent9 sites
70
Vendor Risk Score

How This Briefing Works

This report opens with key findings, then maps the gaps between what Justcall 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

Key Findings

9 detections across 9 sites100% pre-consent activity
CRITICAL

Pre-Consent Activity

Justcall was observed loading and executing before user consent was obtained on 100% of sites where it was detected.

GDPRePrivacy
Disclosure Gaps

Claims vs. Observed Behavior

1 gaps
Customer Impact

What This Means For You

Revenue teams using Justcall inherit pre-consent tracking liability. Privacy audits detecting consent bypass create compliance exposure. Sales intelligence derived from non-consented data produces legally questionable insights.
Recommended Actions

What To Do About It

Role-specific actions based on observed behavior

If You Use Justcall

  • →Implement consent gate before Justcall initialization
  • →Verify call tracking functionality with post-consent loading
  • →Maintain consent timestamp records vs Justcall execution timing

If You're Evaluating Justcall

  • →Request Justcall consent integration technical documentation
  • →Evaluate revenue intelligence platforms with consent-first architecture
  • →Consider server-side call tracking to avoid browser consent requirements

Negotiation Leverage

  • →Justcall deploys pre-consent - require consent-aware initialization capabilities
  • →Demand technical documentation of consent management integration
  • →Negotiate consent bridge implementation as contract term
  • →Establish liability allocation for pre-consent data collection violations
Runtime Detections

Runtime Detections

1 BTI-C CODES

BLACKOUT observed this vendor's JavaScript executing in a live browser and classified each hostile behavior using our BTI-C (Behavioral Threat Intelligence — Capability) taxonomy. These are not theoretical risks — each code below was triggered by something we watched this vendor's code actually do.

BTI-C09Consent Bypass

Ignoring CMP signals

IOC Manifest

IOC Manifest

4 INDICATORS

Indicators of compromise across 3 categories. Use for detection rules, CSP policies, or Pi-hole blocklists.

No indicators in this category

Ecosystem

Ecosystem & Supply Chain

Operates within sales/revenue operations technology stack. Pre-consent pattern suggests integration with call tracking or visitor identification requiring immediate initialization.
Evidence

Evidence Artifacts

Artifacts collected during analysis, available with evidence-tier access.

HAR Capture

Complete network capture with all requests and responses

IOC Manifest

6 detection signatures across scripts, domains, cookies, and network endpoints

Vendor Details