Does your website use third-party services? Get GDPR compliant in minutes.
Try FlowConsentFree plan · 10-min setup
Glide.js is a lightweight, dependency-free JavaScript ES6 slider and carousel library (~8kb gzipped). It provides responsive, touch-enabled sliders with CSS3 transitions. Glide.js does not set any cookies, does not collect personal data, and does not perform any tracking. When loaded from a public CDN such as jsdelivr or cdnjs, visitors' IP addresses may be transmitted to CDN providers. Self-hosting the library eliminates any privacy concern. No consent banner is required for Glide.js itself.
Glide.js is a lightweight, dependency-free JavaScript ES6 slider and carousel library created by Jędrzej Chałubek. Weighing only ~8kb gzipped, it delivers responsive, touch-enabled sliders with smooth CSS3 transitions. The library is open source under the MIT licence and can be installed via npm or loaded from public CDNs such as jsdelivr and cdnjs. Glide.js is designed purely for UI presentation: it slides content panels, images, or cards across the screen. It does not collect analytics, does not fingerprint visitors, and does not communicate with any remote server on its own.
Glide.js does not set any cookies. It does not use localStorage, sessionStorage, or any other browser storage mechanism. The library operates entirely in memory during page rendering and leaves no persistent trace on the visitor's device. No personal data such as IP addresses, device identifiers, or behavioural information is collected or processed by Glide.js code. This makes it one of the most privacy-friendly front-end libraries available.
Since Glide.js does not set cookies or collect personal data, it falls outside the scope of the ePrivacy Directive's consent requirement (Art. 5(3)). Under GDPR, no lawful basis for data processing needs to be established for the library itself, because no personal data processing occurs. However, when Glide.js is loaded from an external CDN, the browser sends a network request that includes the visitor's IP address to the CDN provider. This CDN request is subject to the CDN provider's own privacy policy and may involve data processing under GDPR.
Get GDPR compliant in 10 minutes
Free plan available · No credit card required
When served from cdn.jsdelivr.net or cdnjs.cloudflare.com, the visitor's IP address is transmitted to Cloudflare or Fastly infrastructure, which operates globally including in the United States. Under GDPR Chapter V, this constitutes an international data transfer. Cloudflare participates in the EU-US Data Privacy Framework, providing an adequacy basis for the transfer. To eliminate any third-country transfer concern entirely, site operators can self-host Glide.js by bundling the library file directly into their build process or serving it from their own European server.
No consent banner or cookie notice is required for Glide.js. The library qualifies as a strictly necessary technical component for website presentation. European data protection authorities, including the CNIL, have consistently held that front-end UI libraries that do not set cookies or collect data do not require user consent. If you load Glide.js from an external CDN, you should mention the CDN provider in your privacy policy under the list of third-party services, but this does not trigger a consent requirement.
For maximum GDPR compliance, self-host Glide.js by installing it via npm and bundling it with your application. This eliminates all third-party requests. If using a CDN, mention the CDN provider (Cloudflare or Fastly) in your privacy policy and note the legal basis for the transfer (EU-US Data Privacy Framework or legitimate interest). No changes to your cookie banner configuration are needed. Glide.js should not appear in your cookie policy because it does not set any cookies.
Websites using Glide.js must obtain user consent under GDPR regulations.
DPIA considerations
A DPIA is not required for Glide.js. The library is a purely client-side UI component that does not process personal data, set cookies, or perform tracking. CDN loading transmits IP addresses but this is standard web functionality and does not trigger DPIA requirements.
Sample consent text
Glide.js does not require a consent notice. It is a front-end slider library that does not set cookies or collect personal data. If loaded from a CDN, you may mention CDN usage in your general privacy policy.
Third-party domains contacted
cdn.jsdelivr.netcdnjs.cloudflare.comglidejs.comThis service may collect user data. Ensure GDPR compliance with FlowConsent.
No. Glide.js does not set any cookies, use localStorage, sessionStorage, or any other browser storage. It is a purely client-side slider library that operates entirely in memory.
No consent is required. Glide.js does not set cookies or collect personal data. It qualifies as a strictly necessary UI component for website presentation and is exempt from ePrivacy consent requirements.
Legitimate interest (Art. 6(1)(f) GDPR) applies for loading a front-end UI library essential to website functionality. Since no personal data is processed by Glide.js itself, no specific lawful basis is required for the library.
Not directly. Glide.js itself does not transmit any data. However, if loaded from a CDN like jsdelivr or cdnjs, the visitor's IP address is sent to CDN infrastructure which may include US servers. Self-hosting the library eliminates this transfer entirely.
No. A DPIA is not required because Glide.js does not process personal data, does not perform profiling, and does not engage in systematic monitoring. It is a display-only UI component with no data processing activity.
For maximum compliance, install Glide.js via npm and bundle it locally in your build process. This eliminates all third-party CDN requests. If you prefer CDN loading, mention the CDN provider in your privacy policy. No cookie banner configuration changes are needed.
Glide.js is already one of the most privacy-friendly slider libraries available. Similar cookie-free alternatives include Swiper.js, Splide, and Keen-Slider. All operate as client-side UI components without cookies or data collection when self-hosted.
No. Since Glide.js does not set any cookies, it should not be listed in your cookie policy. If loaded from a CDN, you may mention the CDN provider in your general privacy policy under third-party service providers, but this is separate from cookie declarations.