Does your website use third-party services? Get GDPR compliant in minutes.
Try FlowConsentFree plan · 10-min setup
Modernizr is an open source JavaScript feature detection library that runs entirely in the browser, sets no cookies and collects no personal data, so it needs no consent.
Modernizr is an open source JavaScript library released under the MIT license that detects which HTML, CSS and JavaScript features the visitor browser supports. Developers use it to adapt a page to the available capabilities, for example by loading a fallback when a modern feature is missing. It is a developer tool, not an analytics or advertising product.
Modernizr runs entirely on the client side, inside the visitor browser. It makes no network requests of its own, sets no cookies, and collects no personal data. It simply tests the browser and adds the results as classes on the page or as a JavaScript object. By itself it never sends anything back to any server, so there is no tracking and no profiling.
Because Modernizr stores nothing on the device and reads no identifiers, the ePrivacy consent rule does not apply to the library itself, and there is no personal data processing by the library. The only privacy consideration arises from how the file is delivered, not from what the library does. If self hosted, there is no third party contact at all.
Get GDPR compliant in 10 minutes
Free plan available · No credit card required
The single privacy consideration is the delivery method. If you load Modernizr from a third party content delivery network such as cdnjs, the visitor browser contacts that CDN, which receives the visitor IP, exactly as in the German Google Fonts cases. If you self host the file from your own server, no third party receives anything and the question disappears.
No consent is required for Modernizr, because it sets no cookies and processes no personal data. There are no data transfers caused by the library itself. A transfer can only occur if you load it from a CDN located outside the EEA, in which case the visitor IP reaches that CDN and the usual transfer rules apply to the CDN, not to Modernizr.
The clearest compliant setup is to self host Modernizr, which removes any third party contact and any transfer question. If you prefer a CDN, disclose that CDN as a recipient and confirm its safeguards. Either way, you do not need a cookie entry or a consent prompt for Modernizr, since the library itself is privacy neutral.
Websites using Modernizr must obtain user consent under GDPR regulations.
DPIA considerations
No data protection impact assessment is required for Modernizr itself because the library sets no cookies, makes no network requests and processes no personal data. The only assessment relates to delivery: if you load it from a third party CDN, evaluate the visitor IP transfer to that CDN. Self hosting removes even that consideration.
Sample consent text
No consent is needed for Modernizr because it sets no cookies and processes no personal data. It runs entirely in your browser to detect supported features and never sends anything to a server.
Third-party domains contacted
cdnjs.cloudflare.comCookies placed
| Name | Type | Duration | Purpose |
|---|---|---|---|
| None | Not applicable | Not applicable | Modernizr sets no cookies and stores nothing on the visitor device. It is a client side feature detection library that runs in the browser, makes no network requests of its own and collects no personal data, so there are no cookies to record. |
This service may collect user data. Ensure GDPR compliance with FlowConsent.
No. Modernizr is a client side feature detection library that sets no cookies and stores nothing on the visitor device. It only reads which browser features are available and records the result on the page, so there is nothing to list in a cookie table.
No. Because Modernizr sets no cookies and processes no personal data, neither the ePrivacy consent rule nor a GDPR consent applies to the library itself. You do not need a consent prompt for it.
No legal basis is needed for the library itself because it processes no personal data. Where you self host the file, serving it relies on legitimate interest under Article 6(1)(f) GDPR as strictly necessary delivery, the same as any of your own static assets.
Not by itself. Modernizr makes no network requests and therefore causes no transfers. A transfer can only happen if you choose to load the file from a CDN outside the EEA, in which case the visitor IP reaches that CDN. Self hosting removes any transfer entirely.
No. The library sets no cookies, makes no requests and processes no personal data, so it presents no risk requiring a data protection impact assessment. The only thing worth a brief note is your chosen delivery method, self host or CDN.
Self host the Modernizr file from your own server, which keeps everything within your own infrastructure and avoids any third party contact. Build only the feature tests you need. You do not need a cookie entry or consent banner for it.
You can often replace Modernizr with native feature checks in JavaScript or CSS, such as the supports query, which detects features without any library. Where you still want a library, any client side feature detection tool can be self hosted to keep the same privacy neutral profile.
You do not need to add Modernizr to a cookie policy, since it sets no cookies. If you load it from a third party CDN, mention that CDN as a recipient in your privacy policy and explain the visitor IP contact. If you self host, no entry is needed at all.