All Vendors
platform

Joinville

Joinville platform initiates execution before consent mechanisms complete, creating consent-sequence violations.

6 IOCs3 detections67% pre-consent2 sites
70
Vendor Risk Score

How This Briefing Works

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

3 detections across 2 sites67% pre-consent activity
CRITICAL

Pre-Consent Activity

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

GDPRePrivacy
Disclosure Gaps

Claims vs. Observed Behavior

1 gaps
Customer Impact

What This Means For You

Organizations using Joinville inherit consent-timing liability. Regulatory audits revealing pre-consent platform execution create compliance findings. Data processing built on non-consented foundation produces legally questionable operations.
Recommended Actions

What To Do About It

Role-specific actions based on observed behavior

If You Use Joinville

  • →Enforce consent gate before Joinville initialization
  • →Verify platform functionality works with delayed loading post-consent
  • →Document consent timestamp vs platform start for audit trail

If You're Evaluating Joinville

  • →Request Joinville consent-aware deployment documentation
  • →Evaluate platforms with native consent integration
  • →Consider architectural changes to enable consent-first loading

Negotiation Leverage

  • →Joinville executes pre-consent - vendor must provide consent-aware initialization capabilities
  • →Require technical documentation of consent management integration
  • →Negotiate consent bridge as deployment requirement
  • →Establish contractual liability terms for pre-consent 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

2 INDICATORS

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

No indicators in this category

Ecosystem

Ecosystem & Supply Chain

Functions as platform infrastructure layer. Pre-consent deployment pattern suggests core functionality dependencies requiring immediate browser-side execution.
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