Does embedding Mux on my site require visitor consent?

Conditional. Mux Player delivering video is functional and needs no consent. Mux Data analytics sets a persistent mux_viewer_id cookie and tracks detailed engagement metrics, which requires consent under GDPR and ePrivacy.

What cookies does Mux set?

Mux sets mux_viewer_id, a 1-year persistent cookie identifying unique viewers across sessions for engagement analytics. Session cookies maintain playback state. Analytics beacons transmit playback data to litix.io, Mux's analytics ingestion domain.

How does ConsentStack handle Mux?

ConsentStack splits Mux into two tiers: the video player is classified as functional and loads freely, while Mux Data analytics is classified as analytics and blocked until consent is granted. This lets video play while protecting viewer privacy.

What tracker domains does Mux use?

ConsentStack has catalogued tracker domains for Mux including mux.com and stream.mux.com. These are the network destinations Mux's scripts contact, which a consent platform blocks until a visitor agrees.

Mux - Video Streaming Privacy Controls

Back to Vendor Library

Overview

Mux is a developer-focused video infrastructure platform that handles video encoding, delivery, and analytics. Unlike consumer-facing video platforms, Mux operates as backend infrastructure — websites use Mux's APIs and player SDK to deliver video content while collecting detailed playback quality metrics. Mux Data (the analytics product) is widely used by streaming services, media companies, and SaaS platforms to monitor video performance at scale. The platform sits at the intersection of functional video delivery and analytics data collection.

What This Script Does

Mux's presence on websites comes through two components: Mux Player (video playback) and Mux Data (video analytics).

Mux Player:

Loads the mux-player web component or HLS.js-based player from cdn.mux.com
Delivers adaptive bitrate (ABR) video streams via Mux's global CDN
Handles quality level switching based on network conditions
Supports DRM-protected content delivery

Mux Data (analytics):

Collects granular playback metrics: play rate, startup time, rebuffering ratio, seek events, and error rates
Tracks viewer engagement: watch time, percentage viewed, and drop-off points
Records quality of experience (QoE) metrics: video resolution, bitrate, and frame drops
Transmits beacon data to litix.io (Mux's analytics ingestion domain)

Cookies set:

mux_viewer_id — persistent cookie (1 year) identifying unique viewers across sessions for engagement analytics
Session cookies for maintaining playback state during the current visit
No third-party advertising cookies are set

Data collected per view:

Viewer ID (cookie-based), IP-derived geography, browser, OS, and device type
Full playback timeline with second-level granularity
Network conditions and bandwidth estimates
Custom metadata passed by the host application (e.g., content title, user tier)

Consent & Compliance

Mux spans both functional and analytics consent categories. The video playback functionality (Mux Player) is functional — it delivers the content the user requested. Mux Data's analytics collection goes beyond functional necessity by tracking detailed engagement metrics and setting persistent viewer identification cookies.

Under GDPR, the mux_viewer_id persistent cookie requires consent as it is not strictly necessary for video playback. The analytics beacons to litix.io constitute processing of personal data (IP address, viewer ID) for analytics purposes.

Under CCPA/CPRA, the viewer-level engagement data and geographic information should be disclosed in the privacy policy. If Mux aggregates viewer data across multiple customer sites, this may have data sharing implications.

Should You Block This Without Consent?

Conditional. Mux Player (video delivery) is functional and can load without consent — visitors explicitly requested the video content. However, Mux Data (analytics) sets persistent viewer identification cookies and collects detailed engagement metrics that go beyond functional video delivery. If your Mux implementation includes Mux Data, the analytics component should require consent. If you use Mux Player without Mux Data, consent is not required.

Is Mux GDPR compliant?

Mux typically loads functional and analytics trackers, which are not strictly necessary for your site to work. Under the GDPR and the ePrivacy Directive, non-essential cookies and trackers must stay blocked until a visitor gives clear opt-in consent. So Mux can be fully GDPR compliant, but only if your site holds its scripts until consent is granted and lets visitors decline just as easily. Compliance depends on how your site loads Mux, not on Mux itself.

Visit website