Cookie policy
Last updated: 28 September 2026
We only use what is strictly necessary for the website and dashboard to work. We use no analytics, advertising or social media trackers, so we do not need to ask for your consent.
1. Public website
The home page and legal pages set no cookies and load no third-party scripts. Fonts are served from our own server, so your browser does not contact Google or any other font provider.
If you use the theme switch (light, dark, system), your choice is saved in your browser's local storage under the key fa-theme. It never leaves your device and is only written when you use the switch.
2. Sign-in and dashboard
When you sign in, our authentication provider Clerk sets cookies that keep you signed in and protect your account. Without them, the dashboard cannot work.
| Name | Provider | Purpose | Duration |
|---|---|---|---|
__session (and suffixed variants) | Clerk, on our domain | Short-lived token proving you are signed in | About 1 minute, renewed while you are active |
__client_uat (and suffixed variants) | Clerk, on our domain | Date of your last sign-in state change, to detect sign-out | Up to 1 year |
__client | Clerk, on Clerk's authentication domain | Keeps your sign-in session | Session lifetime configured for the application |
clerk-* (local storage) | Clerk | Caches your session token in the browser | Until sign-out |
fa-theme (local storage) | FiveM Analytics | Remembers the theme you chose | Until you clear your browser data |
3. Why there is no consent banner
Under article 82 of the French Data Protection Act and the ePrivacy Directive, consent is not required for cookies that are strictly necessary for a service you explicitly request, such as staying signed in, or that remember a display preference you chose. These are the only ones we use. If we ever add an optional tool, such as audience measurement, we will update this page first and ask for your consent where the law requires it.
4. Managing cookies
You can delete or block cookies in your browser settings. Blocking the authentication cookies will prevent you from signing in to the dashboard; the public website will keep working.