Set up your bannerConfigure Your ToolsAudio and Video Content

JW Player

How to configure JW Player at different risk levels and map it in the Consenter Manager.

This work is licensed under CC BY-SA 4.0

Typical processing purposes: Unlock additional website features, Customise online ads

Overview

This guide explains how to implement different privacy configurations for JW Player and how to reflect them in the Consenter Manager.

  1. Configure the third-party service.
  2. Map the selected configuration in the Consenter Manager.
  3. Update your privacy policy to reflect the actual implementation.

The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.

At a glance

Scope. The JW Player web player with optional advertising (JWP, Inc., New York, United States).

What the service does in this scope. The doNotSaveCookies setup property permits or prohibits the player from storing user IDs; by default (false) user cookies are stored, and JW Player suggests true when a user has opted out via a CMP. JW Player supports IAB TCF v2 in VAST and Google IMA advertising.

Note on consent signals. Advertising in the player expects a TCF consent string. Consenter does not currently support TCF communication, so this guide does not cover configuring the signal; load the player only after consent in Consenter.

Configurations included.

ConfigurationSummary
Configuration A — Medium riskPlayer without ads; doNotSaveCookies: true; player after consent.
Configuration B — Higher risk (default configuration)Player with user cookies and VAST / Google IMA ads; after consent.

No configuration without prior consent. Even with doNotSaveCookies: true, the player loads from JW Player's CDN and sends analytics; the sources do not establish that this is free of device access.

Step 1 — Configure JW Player

#Configuration areaWhere to configure itConfiguration A — Medium riskConfiguration B — Higher risk (default configuration)
1Processing purposesOperator decisionUnlock additional website featuresUnlock additional website features; Customise online ads
2doNotSaveCookiesjwplayer.setuptruefalse (default)
3AdvertisingVAST / Google IMAOffOn
4LoadingConsenter script blockingAfter consentAfter consent

Step 2 — Map the configuration in the Consenter Manager

Processing location. JWP is a US enterprise subject to the US CLOUD Act; list the United States. Ad partners (e.g. Google) need their own entries as independent controllers.

Consenter Manager fieldConfiguration A — Medium riskConfiguration B — Higher risk (default configuration)
Processing purposesUnlock additional website featuresUnlock additional website features, Customise online ads
Tracking methodThird party tracking (single session, cross-website)Third party tracking (crosssession, cross-website)
IdentifierNo identifierDevice identifiers
Data categoriesBrowsing and interaction data, Device characteristics, IP addressBrowsing and interaction data, Device characteristics, Device identifiers, IP address, Users' profiles
Legal role of data recipientProcessorProcessor (JW Player); ad partners as Individual Controller
Personalisation modelNo personalisationProfile based
Maximum storage durationSessionPer cookie inspection
Processing locationUnited StatesUnited States

How is this guide?

Shape Consenter Together

Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.

Need Help?

Last updated on

On this page