What is the player cookie?
„player” is an HTTP cookie placed by Vimeo, the video hosting platform owned by Vimeo, Inc. It appears on websites that embed a Vimeo video (for example via an iframe or embed code), when the visitor loads that page or interacts with the video player.
Because it is set on the vimeo.com domain rather than the host site's domain, it is considered a third-party cookie from the perspective of the site displaying the embed.
What data it stores
The cookie stores information related to the user's video playback preferences within the Vimeo player interface, such as viewing settings for Vimeo embeds. The exact value format is not publicly documented by Vimeo, and its content may vary.
The data is sent to Vimeo's servers (Vimeo, Inc., whose infrastructure may involve data transfers outside the European Economic Area), not to the site hosting the embed.
What it is used for
The stated purpose is functional: the Vimeo player uses this cookie to keep the viewing experience consistent when the user returns to a video or navigates between multiple pages containing Vimeo embeds, whether on the same site or across different sites.
For the website operator, this cookie does not generate any first-party data — it is simply part of the normal operation of the embedded video player.
Does it require consent?
In CookieFix's classification, „player” falls under the preferences (functional) category. While it relates to how a video player works, it is not strictly necessary for basic page display, which means it requires the visitor's prior consent under Article 4^1 of Law 506/2004 (Romania's transposition of the ePrivacy Directive) and GDPR principles.
The website operator should declare this cookie in the cookie policy, place it under the corresponding consent banner category, and prevent the Vimeo embed (and the resulting cookie) from loading before consent is obtained.
How to block or delete player
A visitor can delete or block this cookie from browser settings (for example the „Cookies and site data” section in Chrome, Firefox, or Safari), by searching for entries associated with the vimeo.com domain. Blocking it may prevent playback preferences from being remembered on future visits.
For website operators, the recommended approach is using a consent management platform such as CookieFix, which automatically blocks the Vimeo script/embed from loading until the visitor gives consent for the preferences category.
Frequently asked questions
It's an HTTP cookie set by Vimeo on vimeo.com when a Vimeo video is embedded and played on a website, used to remember the user's playback preferences.
Yes, since it's classified as preferences (functional), it is not strictly necessary and should only be set after the visitor gives consent, in line with GDPR and Law 506/2004.
The typical duration is 1 year from the last time the cookie was set or updated.
You can use a consent management platform that blocks the Vimeo embed from loading until consent is given for the preferences category, or a visitor can delete it manually from their browser settings.