Cookies are part of the infrastructure, not the furniture.
We use a minimal set of technical cookies to ensure the site functions reliably—like a well-built wall holds a picture frame. Marketing and analytics scripts are opt‑in only.
Our Evaluation Method
Every cookie on nodexo.world is logged and justified against a single criterion: does it serve a technical function required for the site to work, or does it merely serve an external service's needs? We apply a three‑point test.
Decision Criteria
- Essential: Required for navigation, form submission, or basic security. No opt-out.
- Functional: Enhances UX (e.g., remembered color mode). Optional, with clear user control.
- External: Third‑party scripts (e.g., embedded maps). Explicit consent required.
This framework allows us to maintain clarity. A site that trusts its own design shouldn't need to rely on opaque trackers to understand its audience.
Cookie Categories
Technical details for transparency. Hover or tap cards for more context.
Essential
Required for core functionality. Disabling these will break the site.
Functional
Optional enhancements. Can be disabled via the consent banner.
External / Analytics
Third‑party services. Strictly blocked until explicit consent is given.
Transparency in Practice
Console Reality
A screenshot of our live staging environment. We log every cookie activation in plain English to the console for developer clarity, not stealth.
"Our clients don't need more data. They need a site that loads instantly, works flawlessly, and respects their users' attention. Every cookie must earn its place."
Process Vignette: The Decision
During a recent accessibility audit for a client in the healthcare sector, we identified a legacy marketing script firing on every page load. The script was generating session tokens without consent. We removed it. The site remained functional, and the legal risk evaporated.
The Trade-Off Map
A design decision is a series of choices. Here’s ours on cookie policy.
Option A: The "Standard" Approach
- • Use a popular consent management platform (CMP) with 20+ default templates.
- • Block nothing until user interacts (showing a banner).
- • Enable analytics, social trackers, and A/B testing by default (user must opt-out).
Trade-off: Max data, min user trust, more complexity.
Option B: The nodexo Approach
- • Use a lightweight, custom consent wrapper (under 5kb).
- • Block all non‑essential scripts at the root; site remains fully usable.
- • Only enable external services after explicit, granular consent.
Trade-off: Minimal data, high trust, lean performance.
Have a question about cookies or privacy?
We're happy to explain our process. This page is part of a transparent practice.