Does your website use third-party services? Get GDPR compliant in minutes.
Try FlowConsentFree plan · 10-min setup
How DPlayer handles cookies and personal data, and what European websites must do to use it in a GDPR and ePrivacy compliant way.
DPlayer is a embeddable video player. It is an open source HTML5 video player that site owners embed to play video content directly on their pages. When it runs on a website it operates as a third party processor whose scripts, cookies and network requests are loaded into the browsers of your European visitors.
In a typical deployment DPlayer processes playback preferences, session identifiers and, when streaming from third party providers, device and connection data. Most of this information qualifies as personal data under the GDPR because it can be linked to an identifiable person, directly or through online identifiers stored on the device.
Any storage of or access to information on a visitor device is governed by Article 5(3) of the ePrivacy Directive, transposed into national law across the EU. The GDPR then governs the subsequent processing, so DPlayer must have a valid legal basis, a clear retention period and transparent information for the data subject.
Get GDPR compliant in 10 minutes
Free plan available · No credit card required
The strictly necessary functions of DPlayer can rely on contract or legitimate interest, but any analytics, marketing or personalisation cookies layered on top still require prior consent. Keep the essential and the optional layers clearly separated so the legal basis matches each purpose.
DPlayer reports hosting in merchant defined servers (self hosted), which keeps the core processing inside the European Economic Area. You should still confirm the location of any subprocessors and content delivery nodes, because a single non European endpoint can still trigger a transfer.
List DPlayer in your records of processing and your cookie policy, load it only through a consent management platform, document the consent you collect and review the vendor data processing agreement at least once a year. Test the site with consent refused to make sure no identifier is set before a choice is made.
Websites using DPlayer must obtain user consent under GDPR regulations.
DPIA considerations
Assess the volume and sensitivity of data processed through DPlayer, whether visitors are profiled or tracked across sites, and any transfer outside the EEA. A formal DPIA is advisable where DPlayer enables large scale monitoring or combines data from several sources.
Sample consent text
This site uses DPlayer to deliver core functionality. Optional analytics and marketing features of DPlayer are activated only with your consent, which you can change at any time in the cookie settings.
Third-party domains contacted
cdn.jsdelivr.netCookies placed
| Name | Type | Duration | Purpose |
|---|---|---|---|
| dplayer-volume | preferences | Persistent (local storage) | Remembers the chosen playback volume |
| dplayer-danmaku | preferences | Persistent (local storage) | Remembers comment overlay settings |
DPlayer uses cookies for user preferences — inform visitors with a consent banner.
DPlayer typically stores session identifiers and, depending on configuration, analytics or marketing cookies. The exact names and lifetimes appear in the cookie table on this page, and you should scan your own site because deployments differ.
For its strictly necessary functions DPlayer can rely on contract or legitimate interest, but any analytics or marketing cookies it adds still require prior consent.
The non essential cookies rely on consent under Article 6(1)(a) GDPR combined with Article 5(3) ePrivacy. Strictly necessary processing can rely on contract under Article 6(1)(b) or legitimate interest under Article 6(1)(f).
DPlayer reports hosting in merchant defined servers (self hosted), so by default data stays in the EEA. Verify subprocessors and CDN nodes, since one non European endpoint can still create a transfer to a third country.
A DPIA is required when processing is likely to result in a high risk, for example large scale tracking or profiling. Where DPlayer monitors behaviour at scale or combines data sources, run a DPIA before going live.
Load DPlayer only after consent through a consent management platform, keep it blocked by default, document each consent, list it in your records and cookie policy, and sign a data processing agreement with the vendor.
Yes. Depending on your goal you can choose privacy first or cookieless tools, or self hosted options that keep data in the EEA. Whichever you pick, the same consent and transparency duties apply.
Add DPlayer to the cookie policy with its purpose, the cookies it sets, their duration and the recipient, note any third country transfer and the safeguard used, and refresh the entry whenever you change configuration or after a new cookie scan.