Legal
Cookie Policy
Last updated: 18 July 2026
This Cookie Policy explains how DREVORA uses cookies and similar browser storage or access technologies on the public website at drevora.app and the fleet and workforce management platform at app.drevora.app.
1. About this policy
This page covers browser cookies and similar technologies such as local storage and session storage that DREVORA’s code actually uses, based on a review of the current public website and web application. It does not describe ordinary server-side database records stored in DREVORA’s backend systems.
For wider information about personal data, see our Privacy Policy. Related product terms are in our Terms of Service.
2. What cookies and similar technologies are
Cookies are small text files that a website may store in your browser. Similar technologies include local storage and session storage, which let a web application keep small pieces of information on your device so features can work as expected.
Some storage lasts only while the browser tab or window is open (session storage). Other storage can remain until it is cleared, replaced, or expires according to the relevant provider or browser settings (local storage or cookies).
3. Technologies DREVORA actually uses
The public marketing website at drevora.app does not set first-party cookies for
advertising or analytics. Apart from the first-visit necessary-storage notice
acknowledgement described below (drevora.cookie_notice.v1), the landing
page does not write other local storage or session storage through DREVORA’s
marketing-site code. It is a static product site with a demo request form.
The authenticated web application at app.drevora.app uses browser storage for login session persistence, a small number of interface preferences, and short-lived functional caches. Those technologies are listed in the table below.
DREVORA currently does not use advertising cookies, behavioural tracking pixels, or marketing analytics scripts such as Google Analytics, Microsoft Clarity, Meta Pixel, or Vercel Analytics in the reviewed landing or application code.
4. Strictly necessary technologies
The platform uses Supabase authentication with browser session persistence so that authorised users can stay signed in and tokens can refresh while using the product. Without this storage, login and secure access to company workspaces would not work reliably.
The application may also keep short-lived session storage entries that reduce unnecessary repeat background work during an Admin session (for example, limiting how often an expiry-notification scan runs) and a short weather display cache for the dashboard. These are functional storage items, not advertising tools.
5. Preference technologies
Where you or your organisation use product features that remember a choice in the browser, DREVORA may store that preference locally. Verified examples include:
- remembering whether the Admin sidebar is collapsed;
- a Worker appearance preference (light, dark, or system) for that browser account;
- a remembered vehicle selection for Vehicle Checks;
- a same-day “warning already seen” marker for Vehicle Checks;
- a temporary login-portal presentation preference (Admin or Worker) for the current browser session.
These preferences are first-party browser storage used to make the product easier to use. They are not used for advertising or cross-site tracking.
6. Analytics technologies
Based on the current repository review, DREVORA does not load third-party analytics or measurement cookies for advertising or behavioural profiling on the marketing website or in the web application client code.
7. Advertising or tracking
DREVORA currently does not use advertising, retargeting, or behavioural tracking technologies in the reviewed code. No cookie consent banner is shown because the verified browser storage described here is limited to necessary authentication, security/session operation, functional caches, and user-requested product preferences.
8. Technology table
The following list reflects verified browser storage technologies. Durations are described honestly: where an exact cookie max-age is not set by DREVORA code, the duration is session-based, browser-controlled, or dependent on the authentication provider’s session configuration.
Supabase authentication session
- Provider
- Supabase (first-party app use)
- Purpose
- Keep authorised users signed in and refresh session tokens
- Category
- Strictly necessary
- Storage type
- Local storage (Supabase client session persistence)
- Duration
- Dependent on Supabase session configuration and sign-out; cleared when the session ends or storage is removed
- Consent required
- No (strictly necessary for the logged-in product)
- Surface
- app.drevora.app
Login portal preference
- Name / key
drevora.auth.portal- Provider
- DREVORA
- Purpose
- Remember Admin vs Worker login presentation for the current browser session
- Category
- Preference / functional
- Storage type
- Session storage
- Duration
- Session-based (ends when the browser tab/session ends)
- Consent required
- No
- Surface
- app.drevora.app
Admin sidebar layout
- Name / key
drevora-sidebar-collapsed- Provider
- DREVORA
- Purpose
- Remember whether the Admin sidebar is collapsed
- Category
- Preference
- Storage type
- Local storage
- Duration
- Browser-controlled until cleared or changed
- Consent required
- No
- Surface
- app.drevora.app (Admin)
Worker appearance preference
- Name / key
drevora.worker.appearance:followed by the user id- Provider
- DREVORA
- Purpose
- Remember a Worker’s light, dark, or system appearance choice
- Category
- Preference (user-requested)
- Storage type
- Local storage
- Duration
- Browser-controlled until cleared or changed
- Consent required
- No
- Surface
- app.drevora.app (Worker)
Remembered vehicle for Vehicle Checks
- Name / key
drevora_vehicle_check_remembered_vehicle_id- Provider
- DREVORA
- Purpose
- Remember the last selected vehicle for Vehicle Checks convenience
- Category
- Preference / functional
- Storage type
- Local storage
- Duration
- Browser-controlled until cleared or changed
- Consent required
- No
- Surface
- app.drevora.app
Vehicle Check warning seen marker
- Name / key
drevora_vehicle_check_warning_seen_…(includes company, user, and date)- Provider
- DREVORA
- Purpose
- Avoid repeatedly showing the same daily Vehicle Check warning
- Category
- Preference / functional
- Storage type
- Local storage
- Duration
- Browser-controlled; keyed to the calendar day in the storage key
- Consent required
- No
- Surface
- app.drevora.app
Admin expiry-notification scan marker
- Name / key
drevora.admin.expiryNotificationScanAt:followed by company id- Provider
- DREVORA
- Purpose
- Limit how often the Admin client requests an expiry-notification scan during a session
- Category
- Strictly necessary / functional
- Storage type
- Session storage
- Duration
- Session-based; application logic also treats a scan as fresh for about 30 minutes within the session
- Consent required
- No
- Surface
- app.drevora.app (Admin)
Weather display cache
- Name / key
drevora-weather:followed by location- Provider
- DREVORA
- Purpose
- Temporarily cache weather display data for the dashboard
- Category
- Functional
- Storage type
- Session storage
- Duration
- Session-based; application logic refreshes after about 30 minutes
- Consent required
- No
- Surface
- app.drevora.app
Landing cookie-notice acknowledgement
- Name / key
drevora.cookie_notice.v1- Provider
- DREVORA
- Purpose
- Remember that the visitor acknowledged the necessary-storage notice on the public website
- Category
- Preference / functional (acknowledgement)
- Storage type
- Local storage
- Duration
- Browser-controlled until cleared, or until a future notice version (for example
v2) replaces it - Consent required
- No (records acknowledgement of necessary technologies; not used for advertising or behavioural tracking)
- Surface
- drevora.app (landing and legal pages)
The public website displays a first-visit notice about necessary cookies and similar
browser storage. When a visitor selects “Accept necessary cookies”, the acknowledgement
value accepted is saved under drevora.cookie_notice.v1 in
localStorage so the notice does not reappear until browser storage is cleared or a
newer notice version is introduced. That key is not used for advertising or behavioural
tracking.
The marketing website may load icon fonts from Google Fonts (fonts.googleapis.com / fonts.gstatic.com). DREVORA does not use that request for advertising analytics. Any cookies set by those third-party font hosts, if any, are controlled by Google’s own systems rather than by DREVORA application storage keys listed above.
9. Managing browser storage
DREVORA does not currently provide a separate in-product “Cookie Settings” control
because the verified technologies above are limited to necessary authentication,
functional operation, and user-requested preferences. On the public website, visitors
acknowledge the necessary-storage notice; that acknowledgement is stored only as
described for drevora.cookie_notice.v1.
Appearance and similar product preferences can usually be changed inside the relevant Admin or Worker settings screens where those controls exist.
Most browsers let you block or delete cookies and clear local or session storage through their settings or privacy controls. The exact steps depend on your browser. If you block or remove strictly necessary authentication storage, you may be unable to sign in or stay signed in to the DREVORA platform. Some remembered preferences and convenience features will also stop working until they are set again.
10. Changes to this policy
We may update this Cookie Policy when our technologies or legal requirements change. The “Last updated” date at the top of this page will change when updates are published.
11. Contact
Questions about this Cookie Policy: admin@drevora.uk.
For broader personal-data information, see our Privacy Policy. Product terms are in our Terms of Service.