All Vendors
platform

Oakie

Platform vendor with pre-consent tracking activation.

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 Oakie 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

Oakie 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

disclosure

MEDIUM
They Claim

“Pending claims extraction”

Observed Behavior

Limited public information about Oakie data practices. Counselor score (40) indicates consent violations but specifics require vendor documentation review.

Customer Impact

What This Means For You

Functionality impact depends on Oakie deployment purpose - removal may affect specific platform features or integrations. Retention risk includes regulatory exposure for consent violations and potential data subject complaints if tracking scope exceeds privacy policy disclosures.
Recommended Actions

What To Do About It

Role-specific actions based on observed behavior

If You Use Oakie

  • →Implement consent gate before Oakie scripts load
  • →Audit platform configuration for data collection scope
  • →Review Data Processing Agreement for processor obligations and data sharing terms
  • →Confirm privacy policy adequately discloses Oakie data processing

If You're Evaluating Oakie

  • →Defer all Oakie scripts until post-consent confirmation
  • →Request vendor documentation on consent management integration capabilities
  • →Assess whether platform functionality can be replicated with privacy-respecting alternatives
  • →Investigate data retention and deletion capabilities

Negotiation Leverage

  • →Oakie contract terms require review - demand clarity on data sharing permissions and processor vs controller status
  • →Negotiate explicit consent management integration requirements in service terms
  • →Confirm platform honors consent withdrawal and data deletion requests with technical enforcement
  • →Request technical documentation on tag firing controls and consent signal integration
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

Oakie appears to integrate with marketing technology or analytics platforms. Limited ecosystem visibility suggests standard integration patterns. Third-party data flows likely exist but require vendor documentation review to confirm scope.
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