Essential layer
Delivery and security
Cookies needed for session, delivery, and security are separated from optional measurement.
Legal / Cookies
This page explains which cookies support session and security, which are optional, and how preferences can change.
Cookie boundaries
An enterprise buyer needs to read what is necessary for secure operation and what is only optional add-on functionality.
Core split
This page keeps a clear separation between essential operation, preferences, and optional measurement.
Security first
Essential cookies remain separate from those used only for optional optimization.
No hidden analytics
If analytics or performance measurement is layered on top of the essential baseline, it comes with clear disclosure and choice.
Preference control
The cookie policy explains that preferences can be managed through the browser, the consent layer, and the named contact.
Operational cookie logic
This is a readable framework for categories and boundaries, not a misleading claim that every non-essential element is permanently active.
Cookie categories
Read the categories by their role in the product and whether they are required or optional.
Helps maintain continuity between the public and authenticated layers where session handling requires it.
Support the protection of forms, sessions, and other technical boundaries of the site.
May remember language or a consent decision so the preference does not need to be repeated every visit.
If enabled, they remain separate from the essential layer and tied to clear disclosure.
Duration
Short-lived session logic, preference memory, and optional measurement do not share the same retention by default.
Disclosure
The difference between essential and non-essential cookies is not hidden in a small legal note.
Escalation
If a client needs a vendor-review answer on cookies, a visible privacy and legal contact path is available.
Contact and escalation
The legal operator and contact route remain visible for policy review, procurement, and mandate preparation.
Contact points
Sensitive mandates keep legal, privacy, and procurement follow-up on one named contact path.
Privacy policy
The matching document stays available for the same legal, privacy, and procurement review.
OpenTerms of use
The matching document stays available for the same legal, privacy, and procurement review.
OpenCookies
This document is the active reference in the current language.
Current documentDPA and privacy contact
The matching document stays available for the same legal, privacy, and procurement review.
OpenLegal documents
All legal pages remain separately accessible so legal, procurement, or security teams can open them directly from the public site.
Privacy
The matching document stays available for the same legal, privacy, and procurement review.
Open privacy policyTerms
The matching document stays available for the same legal, privacy, and procurement review.
Open terms of useCookies
This document is the active reference in the current language.
Current documentRelated review pages
Use these pages when published legal text needs to be matched against operating controls, commercial framing, or the next contact step.
Contact
The contact page keeps the operator, introduction lead, and next-step path visible when the published documents do not resolve the review.
Open contactNext step
The public web remains a briefing layer. Request access and, once approved, the detailed workflow, intake paths, and next steps become available inside the member area.
Access frame