Cookies and consent

Essential cookies support the service. Optional analytics stays off until consent is given.

The public site is designed so non-essential analytics does not load unless it has first been configured and the visitor has actively chosen to allow it.

Last updated 22 April 2026

Use the contact page for legal, privacy, or procurement follow-up.

Important

These pages explain the current operating model of the product. Where a signed commercial agreement, proposal, order form, renewal, or DPA contains more specific terms, that signed agreement takes precedence.

Essential cookies and storage

Essential session and security storage may be used for secure form submission, sign-in, session continuity, MFA, and storing a cookie-consent preference.

Essential storage is used only where it is required to deliver the requested service or a security control.
Authenticated product pages also use secure session behavior needed to keep signed-in users authenticated safely.

Optional analytics

Optional analytics is separate from essential storage. If analytics is enabled later, it remains off until the visitor actively accepts it.

Rejecting optional analytics does not block access to the public site.
The consent control is designed so rejecting optional analytics is as easy as accepting it.

Managing consent

Visitors can revisit cookie preferences from the footer control at any time.

If analytics is not configured, no optional analytics script is loaded.
If analytics is configured, the public shell still waits for an explicit consent decision before loading it.

Need clarification?

Route legal, privacy, or procurement questions through the same product host.

The public contact route is the intake path for rollout, compliance, data-rights, and commercial follow-up.