Ruvalin

Trackers

Cookies

This site sets none. No measurement cookie, no advertising cookie, no preference cookie. That is why there was no banner to dismiss when you arrived.

Last updated

01

What is stored on your device

Nothing. The site sets no cookie, writes nothing to your browser's local storage, and places no identifier of its own or anyone else's. Even the phishing test, which could reasonably want to remember your answers, keeps them nowhere: they live in the page and go with it.

02

Audience measurement, without cookies

Page traffic is measured by Vercel Web Analytics. The service sets no cookie and creates no lasting identifier: it computes a hash from the incoming request, uses it to avoid counting the same visit twice, and discards it after twenty-four hours.

What it keeps is the timestamp, the page viewed, the referrer, an approximate city-level location, the operating system and the browser. None of it identifies you, none of it follows you from one site to another, and none of it is passed to third parties. The service's documentation sets out what it collects

An arrangement of this kind counts as audience measurement strictly necessary to the service, which the French regulator exempts from consent so long as it stays within that purpose, does not correlate data across sites and feeds no profiling. That is the case here. The CNIL's guidance

If you would rather not appear in it even so, any common content blocker will stop the script loading: the site behaves exactly the same without it.

03

Google's calendar, and only if you ask for it

One third-party element could set cookies: the booking calendar provided by Google, offered at the end of the domain checker and the phishing test.

It is not loaded with the page. Instead, an empty frame offers to display it. Until you click, nothing goes to Google: no cookie, no IP address, no page viewed. If you do click, you load Google's service, and its own trackers then apply. Google's privacy policy

You can always book without loading anything at all: the button that opens the calendar in a new tab, the telephone, or an email to contact@ruvalin.com will do just as well.

04

Why there is no banner

Because there is nothing to consent to. Article 82 of the French Data Protection Act requires consent before reading from or writing to a visitor's device, and before loading a third party that would do so. Here nothing is written, and the one third party that might be is waiting for your click.

A banner on a site that stores nothing adds no protection whatsoever. All it does is train the visitor to click “I accept” without reading — which is precisely the habit phishing exists to exploit.

05

How to check for yourself

Do not take our word for it. Open your browser's developer tools, go to the Application or Storage tab, and look at the cookie list for ruvalin.com. It is empty. The Network tab will likewise show you outgoing requests, and Google will appear there only after you have clicked to display the calendar.

06

Contact and changes

This page is updated should the site ever include a service that sets trackers, in which case a compliant consent mechanism would be put in place first. Any question: contact@ruvalin.com.

Personal data processing is set out in full in the privacy policy

CallBook