Cookie and local storage policy
Use of cookies, identifiers, and similar technologies
This document explains which cookies and storage technologies Flecsa uses, for what purpose, for how long, and how you can manage them in accordance with applicable ePrivacy rules, the GDPR, and guidance from supervisory authorities.
1. What are cookies?
Definition and scope
Cookies are small text files that a website or application stores on your browser or device when you visit or use Flecsa. They help remember preferences, maintain active sessions, measure usage, or improve security.
We also use similar technologies such as local storage (localStorage), sessionStorage, in-memory session identifiers, and technical pixels when needed for equivalent functions.
2. Types of cookies
Classification under applicable rules
Cookies may be classified according to various legal and technical criteria:
- By ownership: first-party cookies (managed by Flecsa) and third-party cookies (managed by integrated providers, e.g. OAuth authentication).
- By duration: session cookies (deleted when you close the browser) and persistent cookies (remain for a defined period).
- By purpose: strictly necessary or technical cookies, preference or functionality cookies, analytics cookies, and advertising or marketing cookies.
3. Strictly necessary cookies
Legal basis: legitimate interest / service performance
These cookies are essential for Flecsa to work properly. They enable authentication, load balancing, CSRF security, session continuity after page reload, and content delivery from distributed infrastructure.
They do not require prior consent under common EU cookie guidance, although we must inform you of their use. If you block them in your browser, you may not be able to sign in or use essential features.
- Authentication session cookies: keep your sign-in verified securely.
- Security cookies: help detect abuse patterns and protect against unauthorized access.
- Infrastructure cookies: associated with CDN or hosting providers to route requests efficiently.
4. Preference and functionality cookies
Personalizing the experience
These remember choices such as interface language, sidebar state, client notification preferences, or accessibility settings. The usual legal basis is your consent or, in some cases, legitimate interest where the preference is strictly necessary to provide a requested feature.
Typical duration ranges from 30 days to 12 months, depending on the nature of the stored preference.
5. Local storage (localStorage)
Data on the user device
Flecsa uses localStorage to remember settings that improve the experience without requiring a server request on every visit. Examples during private beta:
- Language preference (`i18nextLng` or equivalent keys).
- Onboarding state (`flecsa-onboarding-v1-completed`) to avoid repeating the initial tour.
- Non-sensitive UI preferences, such as collapsed panels or recent filters when stored locally.
This data remains on your device until you delete it manually or reset site settings in your browser.
6. Analytics cookies
Aggregated usage measurement
During private beta, Flecsa may not use third-party analytics cookies. If we enable them in the future, they will allow us to understand in an aggregated, pseudonymized way how the platform is used (pages visited, errors, performance).
In that case, we will request your prior consent via a banner or preference center, in line with applicable ePrivacy rules. You may reject them without affecting access to essential features.
7. Third-party cookies
Integrated providers
When using Sign in with Google or other OAuth providers, those third parties may set their own cookies under their policies. Flecsa does not directly control those cookies. We recommend reviewing the relevant provider’s privacy and cookie policies.
Infrastructure providers (hosting, CDN) may use strictly necessary technical cookies for service delivery.
8. Retention periods
Duration of each category
Session cookies expire when you close the browser. Persistent cookies are kept for the period defined in their technical configuration, typically between 24 hours and 12 months, except security cookies that may renew on each visit.
We periodically review cookie duration to comply with the data minimization principle.
9. How to manage or withdraw consent
User control
You can manage cookies in several ways:
- Browser settings: most browsers let you block, delete, or limit cookies. See help for Chrome, Firefox, Safari, or Edge.
- Privacy extensions: third-party tools that block trackers (may affect Flecsa functionality).
- Direct contact: email privacy@flecsa.com if you need help exercising your preferences.
- Future preference center: if we enable non-essential cookies, we will provide a dedicated in-app panel to accept or reject specific categories.
10. Updates to this policy
Changes in technologies used
We will update this Cookie Policy when we incorporate new technologies, providers, or purposes. The “Last updated” date reflects the current version. We will notify you via in-app notice if changes require renewed consent.