FMSCookie Notice
This site sets only what it needs to function. There is no advertising or cross-site tracking cookie here.
Last updated: August 8, 2026 · Version 1.0
Draft — company details not yet filled in
This document is not in force. It is published for review only: the operating entity’s details are still missing, and a contract without an identified counterparty binds nobody. Fill in the company environment variables to publish it.
Missing: legalName, entityForm, registrationNumber, registeredAddress, governingLawCountry, disputeForum
1. What this site stores
| Name | Purpose | Lifetime | Category |
|---|---|---|---|
| fms_locale | Remembers the language you chose, so the site does not go back to guessing from your operating system on the next visit | 12 months | Strictly necessary |
| Session and authentication cookies | Keep you signed in on the pages that require an account, and protect form submissions | Session, or as stated at sign-in | Strictly necessary |
Strictly necessary cookies do not require consent under the ePrivacy Directive, because the site cannot deliver what you asked for without them. We do not use them for anything beyond the purpose stated.
2. What this site does not set
- No advertising or retargeting cookies.
- No cross-site tracking, no advertising pixels, no social media tracking widgets.
- No third-party analytics that profiles you across sites.
- No fingerprinting.
If we ever add an optional cookie — for example product analytics — we will ask for your consent first through a banner that makes refusing as easy as accepting, and we will update this notice before it goes live.
3. How to control cookies
You can delete cookies and block them in your browser settings. If you block the language cookie, the site will simply detect your language from your operating system every time, which is the same behaviour as a first visit. If you block authentication cookies, the pages that need an account will not work.
4. The mobile and desktop apps
The FMS apps do not use cookies. They store an authentication token and your settings in the platform’s secure storage on the device. What they collect is described in the Privacy Policy.