Cookie Policy

Cookies and preferences

Technical update: 28 October 2026.

Necessary functions

The website uses browser storage for the cart and display preferences. Private areas use technical cookies for authentication and security. These functions are separate from optional statistics.

Optional Google Analytics 4 statistics

When configured, Google Analytics 4 is enabled only after “Accept statistics” is selected. Before a choice and after rejection, the website does not load the Analytics tag or send it events. “Reject statistics” and “Accept statistics” are available in the same panel.

With consent, public page views and actions involving public products may be measured: product views, cart changes and checkout starts. An order awaiting bank transfer is not a paid purchase. Purchases are measured on the server only after payment verification and where consented attribution is available; a refund verified for the entire paid amount may correct a previously measured purchase.

Analytics parameters include pseudonymous browser and session identifiers, public product codes, quantities and euro amounts. The website excludes emails, names, phone numbers, addresses, licence keys, private pages, order confirmation pages, URL query strings and fragments. Advertising identities, Google Signals and advertising personalisation are not enabled by this integration.

Duration and changing your choice

The statistics choice is stored in the browser for 180 days, after which it is requested again. Analytics cookies _ga and _ga_* are configured for a maximum of 180 days without automatic renewal. Use “Cookie preferences” in the footer to change your choice.

Withdrawal immediately stops new events in this browser and removes analytics cookies accessible to the website. The browser sends a random withdrawal code to the server. If offline, it retains the request and retries when the website reconnects. Server dispatch is blocked once the server receives the withdrawal; a request already sent cannot be recalled. Actions before consent are not replayed.

The server does not use attribution older than 180 days for new dispatches. The technical ledger retains pseudonymous identifiers, logical event receipts and hashes of withdrawal codes to prevent duplicate events and honour subsequent withdrawals. This operational duration does not automatically delete existing ledger records. For other processing information and contacts see the privacy policy.