Does your website use third-party services? Get GDPR compliant in minutes.
Try FlowConsentFree plan · 10-min setup
Offline.js is a lightweight open-source JavaScript library that automatically detects when a user loses their internet connection and can display customisable offline notifications. It operates entirely client-side in the browser, makes no server requests, collects no data, and sets no cookies. Offline.js has no GDPR implications.
Offline.js is a lightweight open-source JavaScript library that detects whether a user''s browser has lost its internet connection and can automatically display customisable notifications or UI elements to inform the user. It works by periodically testing connectivity and triggering events when the connection status changes. Offline.js operates entirely within the user''s browser and makes no external server calls beyond the optional connectivity test request.
Offline.js has no GDPR implications. It is a client-side utility that detects connectivity state. It sets no cookies, stores no personal data, and makes no requests that transmit personal data. The optional connectivity test (a small HTTP request to check if the network is reachable) does not constitute personal data processing as it does not identify individuals.
If Offline.js is loaded from a public CDN, that CDN logs visitor IP addresses. Self-hosting Offline.js as part of your application bundle eliminates this consideration. Include Offline.js via npm and bundle it with your application code.
Get GDPR compliant in 10 minutes
Free plan available · No credit card required
No GDPR actions are required for Offline.js. Self-host the library via npm bundle rather than loading from public CDNs. No privacy policy entry, DPA, or cookie notice is needed for Offline.js itself.
Websites using Offline.js must obtain user consent under GDPR regulations.
DPIA considerations
A DPIA is not required for Offline.js. The library has no data processing capabilities.
Sample consent text
This website uses Offline.js to detect connectivity issues. Offline.js is a client-side library with no data collection. No privacy implications arise from using Offline.js.
Third-party domains contacted
github.hubspot.comnpmjs.comCookies placed
| Name | Type | Duration | Purpose |
|---|---|---|---|
| offline_none | session | Session | Offline.js sets no cookies — this entry notes its absence for completeness |
This service may collect user data. Ensure GDPR compliance with FlowConsent.
No. Offline.js is a client-side connectivity detection library. It operates entirely in the browser and does not collect, store, or transmit any personal data.
No. Offline.js does not set any cookies. It manages connectivity state entirely in browser memory.
It makes a lightweight connectivity test request to check if the network is reachable. This request does not include personal data and does not constitute personal data processing. It is functionally equivalent to a browser pinging a server.
No. Offline.js has no data processing and requires no mention in any privacy policy or cookie notice.
No. Offline.js has no data processing capabilities.
Offline.js was last significantly updated several years ago and is now mostly in maintenance mode. For modern web applications, the browser's native Network Information API and Service Workers provide more powerful offline detection and handling. Offline.js remains functional but new projects may prefer native browser APIs.
Install via npm and bundle with your application rather than loading from a CDN. This keeps all static assets on your own infrastructure and avoids third-party CDN IP logging.
Yes. The browser's native online/offline event listeners and the Network Information API provide built-in offline detection. Service Workers enable more sophisticated offline handling including cached responses. For simple offline notification needs, a few lines of native JavaScript can replace Offline.js entirely.