Functionality vendor · Vimeo.com, Inc.
Vimeo Cookies: List With Purpose and Retention
Last verified 2026-10-17 · Updated 2026-10-17
On this page
Cookies Vimeo Sets on Your Site
The Vimeo player sets the vuid cookie on vimeo.com by default, and Vimeo lists 9 more player cookies, such as player and player_clearance.
| Name | Type | Category | Party | Retention | What it does |
|---|---|---|---|---|---|
<clip-id>_password | Cookie | Functionality | Third-party | Session | The <clip-id>_password cookie on vimeo.com keeps the encoded password of a password-protected video for the browser session. |
<webinar-uuid>_webinar_registrant | Cookie | Functionality | Third-party | 7 days | The <webinar-uuid>_webinar_registrant cookie on vimeo.com stores the ID of a webinar registrant for 7 days. |
__cf_bm | Cookie | Essential | Third-party | 30 minutes (1800 seconds) | The __cf_bm cookie on vimeo.com is the Cloudflare bot management cookie of Vimeo, which Vimeo sets even with dnt=1. |
_cfuvid | Cookie | Essential | Third-party | Session | The _cfuvid cookie on vimeo.com supports the Cloudflare rate limiting rules of Vimeo for the browser session, even with dnt=1. |
cf_clearance | Cookie | Essential | Third-party | 1 year (365 days) | The cf_clearance cookie on vimeo.com remembers for 1 year that the browser passed a Cloudflare challenge, even with dnt=1. |
flags | Cookie | Functionality | Third-party | 1 year (365 days) | The flags cookie on vimeo.com stores the player features the video owner turned on, for 1 year. |
lc_<hash> | Cookie | Functionality | Third-party | 7 days | The lc_<hash> cookie on vimeo.com stores the ID of a viewer who filled in a video registration form, for 7 days. |
player | Cookie | Functionality | Third-party | 1 year (365 days) | The player cookie on vimeo.com keeps the volume, quality, and caption choices of a viewer in the Vimeo player for 1 year. |
player_clearance | Cookie | Essential | Third-party | 7 days | The player_clearance cookie on vimeo.com protects the Vimeo player from bots for 7 days, and Vimeo sets it even with dnt=1. |
vuid | Cookie | Analytics | Third-party | 2 years (730 days) | The vuid cookie is a Vimeo analytics cookie that identifies a viewer of embedded videos for 2 years and needs consent under the ePrivacy Directive. |
Scripts, Pixels, and Endpoints Vimeo Loads
Vimeo loads 1 known script, pixel, or data endpoint. Each row gives the host to look for in the Network tab of Chrome DevTools or in a cookie scanner report.
| Type | Resource | Host | What it does |
|---|---|---|---|
| Iframe | Vimeo embed (player.vimeo.com) | player.vimeo.com | The Vimeo player loads the video from player.vimeo.com and writes the vuid cookie unless the URL carries dnt=1. |
Does Vimeo Need Consent?
Yes, the Vimeo cookies need consent in the EU and the UK, and need no prior opt-in in California. The table gives the rule for each law, taken from the page of the <clip-id>_password cookie.
| Law | Consent before the cookies are set | Opt-out right | Source |
|---|---|---|---|
| EU ePrivacy Directive + GDPR | Required | Withdraw at any time | Article 5(3), ePrivacy Directive |
| UK PECR | Required | Withdraw at any time | Regulation 6 and Schedule A1, PECR |
| California CCPA | No general opt-in | None while the vendor acts as a service provider | Cal. Civ. Code 1798.120 |
The consent table describes what each law requires and is not legal advice. Whether a law applies to your site depends on where your visitors are, where your business is based, and how you set up Vimeo, such as the dnt parameter of the player URL.
Vimeo sets 4 strictly necessary cookies as well, such as __cf_bm, and those cookies follow the rule for strictly necessary cookies.
Read the reason for each answer in the consent rules for the <clip-id>_password cookie.
How to Add Vimeo to a Consent Banner
Add Vimeo to a consent banner by holding back the script that inserts the Vimeo player until the visitor accepts functionality cookies. Both TermsFeed products block Vimeo in the Functionality category.
Add Vimeo to TermsFeed Free Cookie Consent
TermsFeed Free Cookie Consent runs a tagged script only after the visitor accepts its category. Change type="text/javascript" to type="text/plain" and add data-cookie-consent="functionality".
<div id="vimeo-1"></div>
<script type="text/plain" data-cookie-consent="functionality">
document.getElementById('vimeo-1').innerHTML =
'<iframe width="640" height="360" src="https://player.vimeo.com/video/VIDEO_ID" ' +
'title="Vimeo video player" allow="fullscreen; picture-in-picture"></iframe>';
</script>Cookie Consent is free and needs no account. Build your free consent banner with TermsFeed Free Cookie Consent.
Add Vimeo to TermsFeed Privacy Consent
Add Vimeo from its template in TermsFeed Privacy Consent, and each video shows a consent placeholder until the visitor accepts Vimeo. Replace each Vimeo <iframe> with the replaceable tag of the template, and remove the padding <div> that Vimeo puts around the player.
The Vimeo template asks for no ID and fills every field of the vendor. Pick the "Vimeo" card under Functionality and click "Add Vimeo". The illustration shows the template form in the TermsFeed app.
Privacy Consent detects the location of each visitor and records every answer in a consent log. Set up Vimeo from its template with TermsFeed Privacy Consent.
Follow every step, the vendor settings, and the check in Chrome DevTools in how to block the <clip-id>_password cookie.
Who Runs Vimeo
Vimeo.com, Inc. runs Vimeo from the United States. The Vimeo player loads from player.vimeo.com, so every Vimeo cookie on your pages belongs to the domain of Vimeo and not to your own domain.
Read how Vimeo.com, Inc. handles the data in the Vimeo privacy policy. Both documents appear in the sources at the end of this page.
Vimeo Cookie FAQs
Does Vimeo need consent?
Yes, the Vimeo cookies need consent in the EU and the UK, and need no prior opt-in in California. Firstly, the ePrivacy Directive requires consent before a site sets the functionality cookies of Vimeo. Secondly, the UK PECR requires consent before a site sets the functionality cookies of Vimeo. Thirdly, the CCPA sets no general opt-in requirement for the functionality cookies of Vimeo, and the table gives the opt-out right of visitors. The consent section of this page gives the table for each law.
How long do Vimeo cookies last?
The cookies of Vimeo last up to 2 years (730 days), and 2 cookies last for the browser session. A session cookie such as <clip-id>_password has no expiry date, and the vuid cookie lasts longest. The retention column of the cookie list gives the lifetime of each cookie.
How do I block Vimeo cookies?
Block the Vimeo cookies by holding back the script that inserts the Vimeo player until the visitor accepts functionality cookies. Tag the script that inserts the Vimeo player with data-cookie-consent="functionality" in TermsFeed Free Cookie Consent, or add Vimeo as a vendor in TermsFeed Privacy Consent. The page of the <clip-id>_password cookie gives the full steps and the settings of Vimeo.
Sources for the Vimeo Cookies
The facts on this page come from the documentation Vimeo publishes, checked on 2026-10-17. The list gives every source, so you check each fact yourself.
- Vimeo Help Center, Vimeo player cookies
- Vimeo Help Center, About player parameters
- TermsFeed check of the Vimeo player with and without dnt=1 in Chrome, 17 October 2026 (internal)
- Vimeo privacy policy