A short cookie policy,
because we use few of them.

A cookie is a small text file that a website asks your browser to store on your device. When you come back, your browser sends the cookie with the request, which lets the site recognize your session and remember a simple setting. Some values are stored the same way in your browser's local storage rather than in a cookie.

FleetPath keeps this to the minimum. We use only the cookies needed to sign you in and to remember your display preference. We do not use cookies to advertise to you, to profile you, or to follow you across other websites.

Below are the cookies FleetPath relies on to keep you signed in and to remember your theme, what each one is for, and how long it lasts.

sb-<project-ref>-auth-token

Purpose: keeps you signed in by holding your authenticated session, so you do not have to log in again on every page. Set by our authentication provider, Supabase. Type: strictly necessary (authentication). Duration: lasts for your signed-in session and is refreshed while you stay active; cleared when you sign out.

fp_theme

Purpose:remembers whether you chose the light or dark appearance, so the correct theme is shown the moment a page loads. The same preference is mirrored in your browser's local storage. Type: functional (preference). Duration: up to 400 days; you can clear it at any time from your browser.

The authentication cookie is set by Supabase and may be split into a few numbered parts (for example, names ending in .0 and .1) when the stored session is large. Those parts together represent a single session.

While the public site is gated ahead of general availability, opening our private unlock link sets one additional strictly-necessary cookie that unlocks the sign-in and sign-up pages. It stores only a one-way hash of an access key, never the key itself, is marked HttpOnly and Secure, lasts about thirty days, and does no tracking of any kind. It is removed once the public site opens.

FleetPath does not set any of the following:

• Third-party advertising cookies.
• Cross-site or cross-context tracking cookies.
• Behavioral-advertising cookies or advertising identifiers.
• Third-party or product-analytics tracking cookies.

We do not sell or share personal information for cross-context behavioral advertising, and we do not build advertising profiles about you. The cookies described above stay within FleetPath and are used only to run the product.

Consent banners exist so a site can ask permission before it sets advertising, analytics, or other non-essential cookies. FleetPath sets none of those. Because we use only strictly-necessary and preference cookies, there is nothing to ask consent for, so we do not present a cookie-consent banner and we do not run consent-management tooling.

You are always in control of the cookies stored on your device. Every major browser lets you view, block, or delete cookies from its privacy or site-data settings, and most let you do so per site.

If you clear or block the theme cookie

Clearing fp_theme simply resets FleetPath to its default appearance; your browser or system light or dark preference is used until you choose a theme again. Nothing else is affected.

If you block the authentication cookies

Blocking the session cookies described in section 2 will break sign-in. These cookies are how FleetPath keeps you authenticated, so if your browser refuses them you will not be able to log in or stay logged in. There is no way around this, because the cookies are essential to the service rather than optional.

Cookies are one small part of how FleetPath handles data. This policy covers what we store in your browser; our Privacy Policy covers the broader picture: what we collect, why, who processes it, how long we keep it, and the rights you have over it. Your use of FleetPath is also governed by our Terms of Service.

If our cookie practices change, we will update this page to match. If we ever introduced a category of cookie that required your consent, we would ask for it first. Given how the product is built today, we do not expect that to happen.