Does your website use third-party services? Get GDPR compliant in minutes.
Try FlowConsentFree plan · 10-min setup
Flowplayer is an online video player and hosting service that embeds video on websites and apps and can serve video advertising. The embedded player can set cookies for playback preferences and, when analytics, advertising or social features are enabled, advertising and tracking cookies. It processes the visitor IP address and viewing data. Consent is normally required once analytics or ads are active, while a no cookie privacy mode is available for playback only embeds.
Flowplayer is an online video player and hosting platform used to embed and stream video on websites and applications. It handles encoding, adaptive streaming and delivery through a content delivery network, and it offers video advertising and monetisation features. Publishers embed the Flowplayer player to show on demand or live video and, where they choose, to run advertisements before or during the content.
The player can set cookies that remember playback preferences such as volume and quality, which are broadly functional. When you enable analytics, advertising or social sharing features, it also sets analytics and advertising cookies and may load third party ad and social scripts. In all cases the delivery of video involves processing the visitor IP address, and viewing data such as plays, watch time and the content requested can be recorded.
Storing and reading cookies on the device is governed by Article 5(3) of the ePrivacy Directive. Strictly necessary playback cookies may rely on functional grounds, but analytics and advertising cookies are not exempt and require consent. The processing of IP and viewing data is personal data processing under the GDPR. Advertising features in particular can involve third party controllers and profiling, which raises the level of obligation.
Get GDPR compliant in 10 minutes
Free plan available · No credit card required
If you run analytics, advertising or social features through Flowplayer, you need prior consent before the related cookies and scripts load. Configure the embed so that these features only activate after the user accepts the relevant category. For a purely functional, playback only experience you can use the no cookie or privacy mode, which avoids non essential cookies and reduces the need for consent.
Video delivery uses a content delivery network and analytics or advertising partners that may be located in the United States, so personal data such as the IP address can be transferred outside the European Economic Area. Any such transfer must rely on an appropriate safeguard such as Standard Contractual Clauses or the EU US Data Privacy Framework where the relevant provider is certified. Map the partners involved and record the safeguards.
Decide whether you need analytics or advertising features at all. If you do, gate the embed behind consent, list the player and advertising cookies in your cookie policy, sign a data processing agreement and document any third party advertising controllers. If you only need playback, use the privacy mode embed, and in all cases inform users about viewing data collection and transfers.
Websites using Flowplayer must obtain user consent under GDPR regulations.
DPIA considerations
A DPIA may be required where Flowplayer is used with advertising or extensive analytics, since this can involve profiling and third party tracking across a large audience. For playback only embeds using the privacy mode the risk is lower and a DPIA is usually not needed. Assess the advertising partners, the viewing data collected, the United States transfer and the scale of use.
Sample consent text
We use the Flowplayer video player to show video on this site. When you accept, we also enable video analytics and advertising, which set cookies and may share viewing data with partners including in the United States. You can decline and still watch with playback only.
Third-party domains contacted
flowplayer.comflowplayer.orgcdn.flowplayer.comCookies placed
| Name | Type | Duration | Purpose |
|---|---|---|---|
| flowplayer preferences | Functional | Persistent | Stores playback preferences such as volume, quality and resume position. |
| flowplayer analytics | Analytics | Up to 1 year | Records video engagement such as plays and watch time when analytics is enabled. |
| flowplayer advertising | Advertising | Up to 1 year | Supports video advertising and measurement when ads are enabled, set only after consent. |
Flowplayer uses cookies for user preferences — inform visitors with a consent banner.
The Flowplayer player can set functional cookies for playback preferences such as volume and quality. When analytics, advertising or social features are enabled it also sets analytics and advertising cookies and may load third party scripts. It processes the visitor IP and viewing data such as plays and watch time.
It depends on configuration. Analytics and advertising cookies require prior consent. A strictly necessary, playback only embed using the no cookie privacy mode may rely on functional grounds and avoid consent for those cookies.
Necessary playback cookies may rely on functional grounds, but analytics and advertising cookies rely on consent under Article 5(3) ePrivacy and Article 6(1)(a) GDPR. Advertising features may also involve third party controllers with their own basis.
It can. Video delivery and any advertising or analytics partners may use servers in the United States, so the IP address and viewing data can be transferred there. Such transfers must rely on Standard Contractual Clauses or the EU US Data Privacy Framework.
For playback only embeds in privacy mode a DPIA is usually not needed. Where you run advertising or large scale analytics that profile viewers, a DPIA under Article 35 GDPR may be required.
Use the no cookie privacy mode if you only need playback. If you enable analytics or ads, gate them behind consent, list the cookies in your cookie policy, sign a data processing agreement and document advertising partners and transfers.
Alternatives include JW Player, Vimeo, Brightcove, Dailymotion and self hosted players such as Video.js. Some offer privacy modes that avoid cookies for playback only. Consent rules apply once analytics or ads are added.
Distinguish functional playback cookies from analytics and advertising cookies, list them by purpose and duration, name any advertising partners, explain US transfers and tell users how to withdraw consent for non essential features.