Legal
Cookies
Updated 23 September 2026
Core Fleet Control does not use profiling, advertising or analytics cookies. This page lists everything the browser keeps for this site, and everything it does not.
What we keep
corefleetcontrol_session
Technical cookie
- When
- Only after you sign in. If you have not logged in, this cookie is not there.
- Purpose
- It keeps you signed in and opens the right area: fleet, courier or platform.
- Duration
- 12 hours. Sign out deletes it at once.
- Contents
- A signed token with the account id, the role and the organisation id. No password, email, name, CNP, IBAN or documents.
- Limits
- HttpOnly: page script cannot read it. SameSite=Lax, path /. In production it is sent only over HTTPS.
corefleetcontrol_cookie_ok
Technical cookie
- When
- When you close the cookie notice.
- Purpose
- It remembers that you have seen the notice, so it does not appear again.
- Duration
- 6 months.
- Contents
- Only the value 1. No personal data.
corefleetcontrol_privacy_read
Browser local storage
- When
- After you confirm that you have read the privacy notice, during registration.
- Duration
- It stays until you clear this site’s data in the browser.
- Contents
- Only the value 1. No personal data.
corefleetcontrol_a11y
Browser local storage
- When
- When you change text size, contrast or link underlines from the Accessibility panel.
- Duration
- It stays until you press Reset or clear this site’s data in the browser.
- Contents
- Text size, high contrast on or off, link underlines on or off. No personal data. It is not a cookie and it is not sent to the server.
corefleetcontrol_home_visit
Technical cookie
- When
- The first time you open the homepage, if this browser has not opened it in the last 12 hours.
- Purpose
- The counter at the bottom of the homepage does not count the same browser twice.
- Duration
- 12 hours.
- Contents
- Only a technical mark, with no personal data. The server keeps a single total, not a list of who came by.
uni-open-chrome
Session storage
- When
- Only in the courier app, if you open the link from an Android in-app browser, for example WhatsApp.
- Duration
- It is deleted when you close the tab.
- Contents
- Only the value 1, so Chrome is not opened again. No personal data.
Courier app cache
Browser cache
- When
- In the courier area, after the app has been opened.
- Duration
- Until the browser drops the cache, or until a new version of the app is published.
- Contents
- Icons, manifest, and images and fonts already downloaded for that area. Not login pages, not payout files, not documents.
- Public site
- The public site service worker does not store pages. It only allows the program to be installed on a computer.
What we do not keep
- Analytics cookies, such as Google Analytics.
- Advertising cookies or pixels, such as Meta or TikTok.
- Cookies from other sites.
- A language cookie. Language follows the country of the IP address or, on a local network, the browser language. We do not write it in the browser.
- A country cookie. If the IP is public, the server reads its country to choose the language and keeps that in memory for about 10 minutes. It does not write it in the browser and it does not build a profile.
- A list of pages visited for marketing.
Passwords, documents, IBAN, CNP and calculations are not in the browser. They are in the database on the dedicated server.