How This Briefing Works
This report opens with key findings, then maps the gaps between what Tidio 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
Analysis pending. Findings will appear here once intelligence collection is complete.
Claims vs. Observed Behavior
pending
“Awaiting scanner verification”
Scanner validation needed to confirm the full scope of runtime behavior including localStorage usage patterns, network requests to Tidio servers, behavioral trigger execution timing relative to consent, and any cookie deployment despite claims of localStorage-only storage
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
Recommended Actions for Tidio
- →- Audit Tidio widget runtime behavior: catalog all network requests, localStorage entries, and DOM interactions triggered by the Tidio JavaScript on your site using browser developer tools. - Review Visitors List data exposure: assess who within the organization can access real-time visitor IP addresses, geolocation, and device data through the Tidio dashboard. - Configure GDPR compliance features: ensure pre-chat consent fields and privacy policy display are active if operating in jurisdictions requiring consent for visitor tracking. - Evaluate behavioral trigger scope: review all active automation triggers and assess whether they require more behavioral data collection than necessary for chat functionality. - Assess localStorage persistence: understand what visitor data Tidio stores in localStorage, how long it persists, and whether it effectively circumvents cookie consent requirements in your jurisdiction.
Negotiation Leverage
- →Tidio's pricing is competitive in the live chat market, but the total cost assessment should include the privacy exposure created by the real-time visitor monitoring system. Push for contractual language limiting the use of visitor behavioral data to chat functionality only -- specifically, ensure that Visitors List data (IP, geolocation, device fingerprinting) is not retained beyond the chat session or used for profiling. If using Lyro AI, demand transparency on whether chat transcripts and visitor behavior data are used for model training across customers. The localStorage-based storage approach should be scrutinized -- while Tidio claims cookies are not used under normal conditions, localStorage persistence may actually create greater tracking exposure since it is not subject to cookie consent mechanisms in most implementations. Competitive alternatives (Intercom, Freshchat, Drift/Salesloft, Zendesk Chat, Crisp) provide negotiation leverage on both pricing and data handling terms.
IOC Manifest
Indicators of compromise across 4 categories. Use for detection rules, CSP policies, or Pi-hole blocklists.
Ecosystem & Supply Chain
Evidence Artifacts
Artifacts collected during analysis, available with evidence-tier access.
Complete network capture with all requests and responses
259 detection signatures across scripts, domains, cookies, and network endpoints