Cookie policy
This site uses no advertising trackers and sets no analytics cookies — here is exactly what is used, and why there is no consent banner.
Last updated : 28 August 2026
This site is deliberately built to set no tracker requiring consent. That is why you do not see a cookie banner on it: there is nothing to consent to.
What this site does not do
- No advertising cookies, no social network pixels, no retargeting tools.
- No profiling, no cross-referencing of your browsing with other sites.
- No sale or sharing of browsing data.
- No analytics cookies.
Cookieless analytics
We measure site traffic with Umami, a solution we host ourselves. Umami sets no cookie and stores no identifier that would let us recognise you from one visit to the next.
Recorded in aggregate form: the page viewed, the referring page, the approximate country, the device type and the browser. The IP address is used during processing to derive the country, and is then not retained.
This measurement falls within the consent exemption for statistics strictly necessary to providing the service, as the French data protection authority accepts for analytics tools limited to that purpose.
Until this measurement is enabled on our server, no analytics script is loaded at all: the site's code only injects it if its configuration is present.
Technical storage
The site is static. It sets no session cookie, keeps nothing in your browser's local storage, and has no sign-in area.
Your browser and our host cache the site's files (pages, images, fonts) to speed up display. This technical cache identifies nobody.
The mobile application
The Peercel app does not use cookies: it keeps, on your device, a secure session token required to sign you in, and a notification token if you accepted notifications. Details are in the privacy policy.
If this were to change
If a tracker requiring consent were ever added — an advertising pixel, for example — a compliant consent banner would become mandatory and would be put in place before anything is set. This page would be updated accordingly, and the history of its versions remains available in our code repository.