Cookie policy

This website sets no cookies of any kind — not advertising, not tracking, not session, not analytics. It embeds no social widgets and no cross-site fingerprinting tools. Nothing on this site talks to an external analytics provider: both mechanisms below are ours, run on our own infrastructure, and the data never leaves it.

Page requests are counted on our server. For each request we record the date, the page, the approximate country, a coarse device category (mobile, tablet, desktop) and the referring website's domain — never the full referring address, which can carry a search query.

To avoid counting the same visit ten times, requests are grouped by a cryptographic fingerprint computed from your IP address and browser, combined with a secret key that we replace every day. Your IP address is never stored. Because the key changes daily, the fingerprint cannot be linked from one day to the next — by us or by anyone else — so it is not a persistent identifier and nothing is stored on or read from your device. This is why it is exempt from prior consent as strictly necessary audience measurement.

Understanding the journey — which pages get read, where people stop — requires recognising that two page views belong to the same visit. That needs an identifier stored on your device, so we ask first. If you decline, or simply ignore the banner, nothing in this section happens.

If you accept, two random identifiers are stored in your browser's local storage: one for the current visit and one that lets us tell a first visit from a returning one. Neither is derived from anything about you. Alongside them we record which pages you opened, which links you clicked and whether you started or completed the pilot request form. None of it leaves venkai.fr or is shared with anyone.

You can change your mind at any time by clearing this site's data in your browser, which removes both identifiers and stops the collection.

The measurements described in sections 2 and 3 are stored separately and carry no shared key, so a record from one cannot be matched to a record from the other. This is deliberate: section 3 covers only visitors who opted in, and treating that subset as if it described everyone would misstate both the data and the legal basis it rests on.

Independently of the above, our content delivery network processes requests to serve this site and keeps its own technical logs — requests, cache performance, bandwidth, protection against attacks. That processing is necessary to deliver the website and is not a form of analytics; it produces no profile and is not combined with anything described above.