QA mode · Tier:PUBLIC(override via ?tier=paid | premium)
← All Vendors
data_enrichment

Limadata

Limadata data enrichment platform initiates execution before consent capture, creating consent-sequence violations.

84 IOCs observed2 detections1 sites
80
Vendor Risk Score
Tier: HOSTILE
Observation Coverage

BLACKOUT observes runtime behavior in the browser. This dossier reflects browser-side execution, which is one of five vendor data-egress classes. Server-to-server transfers, backend integrations, and offline data flows are outside this observation boundary.

BLACKOUT observes runtime behavior and cites the regulations that address that behavior pattern. Legal determinations are the customer's counsel's call.

How This Briefing Works

This dossier opens with key findings, then maps the gap between what Limadata discloses and what BLACKOUT observed at runtime. From there: what it means for your organization, what to do about it, and the detection evidence underneath. BLACKOUT observes runtime browser behavior and cites the regulations that address each pattern — legal determinations are your counsel's call.

Key Findings

At a Glance

Detections
2

across 1 sites

Pre-Consent Rate
0%

vendor fires before consent

Disclosure Gaps
1

Summary

Briefing

Data enrichment technology deploying pre-consent tracking. Consent bypass (C09) creates regulatory violations under privacy frameworks requiring explicit opt-in before data processing begins.

Customer Impact

What This Means For You

Organizations using Limadata inherit consent-timing liability for data enrichment. Privacy audits revealing pre-consent data processing create compliance findings. Enriched data built on non-consented foundation produces legally questionable intelligence.

Collapse Engine

Risk Channel Breakdown

Oracle
Truth Collapse
25

Distorts attribution data

Broker
Control Collapse
90

Feeds competitor intelligence

Reaper
Safety Collapse
0

Expands attack surface

Counselor
Legitimacy Collapse
100

C09 consent bypass - data enrichment processes execute before consent mechanism completion

BTI Codes

Threat Indicators

Runtime-observed (BTI-C)

BTI-C01
Defeat Device

Evasion infrastructure, auditor bypass

BTI-C06
Behavioral Biometrics

Keystroke/mouse tracking

BTI-C07
Session Recording

Full session replay

BTI-C09
Consent Bypass

Ignoring CMP signals

BTI-C10
Fingerprinting

Device identification

1
BTI Consequences Identified

Per-code narrative explanations of what each detected behavior means for your organization

Available in VIDB Subscription

Per-code evidence with full attribution chain, severity rankings, and consequence narratives See pricing →

Disclosure Gaps

Claims vs. Reality

1
Gaps Observed

BLACKOUT analyzed Limadata's public claims against observed runtime behavior and identified 1 contradiction.

Available in VIDB Subscription

Full claim-vs-reality gap analysis with claim text, observed behavior, severity, regulatory citations (GDPR, CCPA, ePrivacy), and evidence pointers per gap See pricing →

Recommended Actions

What To Do

Recommended Actions
7

3 for current users · 4 for evaluators

Negotiation Leverage
4

contractual leverage points

Available in VIDB Subscription

Role-specific actions (security / legal / marketing / procurement), full negotiation brief with contractual language, and BTI-code-specific consequences See pricing →

Ecosystem

Supply Chain & Pairings

Available in VIDB Subscription

Full supply-chain mapping (loads / loaded-by lists with vendor identities) and the undisclosed-subprocessor list with observation evidence See pricing →

Profile: limadataFirst Seen: 2026-01-22Last Updated: 2026-02-25