Cookies and Browser Storage
How DriverWell uses sign-in storage, feature preferences and public offline reading
Last updated: 1 September 2026
1. What This Policy Covers
Cookies are small files stored by a website through your browser. DriverWell also uses local storage, session storage and IndexedDB for selected features. Those technologies are listed separately because they are not all HTTP cookies.
DriverWell uses an essential sign-in cookie and browser storage needed for features you choose to use. The anonymous public support core does not load advertising cookies, social-media tracking pixels or public route-measurement storage.
2. Essential Sign-In Cookie
This cookie is created after a user chooses to sign in. It supports the requested authenticated service and cannot be switched off while that session is active. The relevant UK cookie rule is Regulation 6 of the Privacy and Electronic Communications Regulations 2003. UK GDPR also applies where an identifier is personal data.
| Cookie | Purpose | Duration | Control |
|---|---|---|---|
| app_session_id | Maintains the authenticated Manus OAuth session | Up to one year unless you sign out or it is cleared earlier | Essential after sign-in |
3. Browser Storage for Requested Features
A feature may write browser storage when you deliberately save a preference, create an offline entry, dismiss a notice, begin a campaign journey or sign in to a fleet account. The technical inventory remains under review, so these are current examples rather than an exhaustive list.
| Storage key or category | Purpose | Duration | Storage type |
|---|---|---|---|
| dw_cookie_consent_v2 | Records that you have made a browser-storage preference and the selection time | Until changed or browser storage is cleared | Local storage |
| sensory-settings | Remembers accessibility and sensory choices you save | Until changed or browser storage is cleared | Local storage |
| driverwell-offline#entries | Stores entries you create for offline-first functionality | Until synchronised or cleared, subject to the feature behaviour | IndexedDB |
| driverwell_fleet_token and company preference | Maintains a fleet dashboard session after the operator signs in | Until sign-out or browser storage is cleared | Local or session storage |
4. Anonymous Public Support Core
The Everyday Support hub, emergency information, public resource directory, Toolbox Talks, condition information and public search are designed to work without an account. Public search happens in the browser and does not send your search words to DriverWell. The public application shell does not load a platform analytics script or create a page-view session identifier for these routes.
Some separate campaign and signed-in features retain their own disclosed data and consent controls while DriverWell reviews them. They are not part of the anonymous public support core.
5. Manage Browser Storage
You can revisit the browser-storage notice using the button above. You can also clear cookies and browser storage through your browser settings. Blocking the essential session cookie prevents signed-in features from working, but public content remains available.
Clearing browser storage can reset local preferences and remove offline copies held by your browser. It does not automatically erase information already stored through a signed-in feature. You can submit a data-rights request through the Privacy Policy or account data page.
6. Service Worker and Push Notifications
DriverWell uses a service worker to cache selected application assets. Push notifications are separate and optional. They are enabled only after you grant browser permission and can be disabled through browser or DriverWell notification settings.
7. Contact
For questions about cookies or browser storage, contact peter@www.driverwell.co.uk. The ICO also provides a public guide at ico.org.uk.