All Vendors
personalization

Tofu

Personalization platform with cross-domain sync and pre-consent activation.

5 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 Tofu 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

Tofu 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

HIGH
They Claim

“Pending claims extraction”

Observed Behavior

Runtime detection shows C08 (cross-domain sync) and C09 (consent bypass)

Customer Impact

What This Means For You

Revenue teams using Tofu face consent liability when personalization tracking begins before user authorization. Cross-domain sync creates visitor journey correlation that persists beyond opt-out requests. Personalization targeting data may expose competitive intelligence.
Recommended Actions

What To Do About It

Role-specific actions based on observed behavior

If You Use Tofu

  • →Audit Tofu initialization timing relative to consent collection
  • →Implement consent-gated personalization engine activation
  • →Review cross-domain sync scope and data retention policies

If You're Evaluating Tofu

  • →Document pre-consent tracking activation and data capture scope
  • →Request technical controls to disable cross-domain sync until consent obtained
  • →Obtain written confirmation of data deletion procedures for personalization profiles

Negotiation Leverage

  • →Pre-consent tracking: Personalization engine activates before consent — require technical mechanism to defer initialization.
  • →Cross-domain correlation: Visitor state synchronized across properties — negotiate opt-out from identity linkage and demand data deletion rights.
  • →Personalization data retention: Targeting profiles persist beyond opt-out — demand specific deletion timelines and third-party sharing restrictions.
Runtime Detections

Runtime Detections

2 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-C08Cross-Domain Sync

Identity stitching

BTI-C09Consent Bypass

Ignoring CMP signals

IOC Manifest

IOC Manifest

3 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

Tofu appears alongside other personalization platforms (Mutiny, Optimizely, Dynamic Yield), analytics tools (Google Analytics, Mixpanel), and ABM platforms. Personalization decisions often based on data from multiple sources.
Loads (1)
Amplitude
Evidence

Evidence Artifacts

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

HAR Capture

Complete network capture with all requests and responses

IOC Manifest

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

Vendor Details