This site set none for a long time. It now sets one, to count what gets read, and only after you agree. This page says what it holds, what it does not, and how to remove it without writing to us.
Last updated :
The short answer
vuisio.com sets one audience measurement cookie, and only if you click
"Accept". Until you answer, nothing is written to your browser and nothing
is sent anywhere.
The measurement is done with our own tool, on our own servers, in France.
There is no Google Analytics, no Matomo hosted elsewhere, no third party
service of any kind. No data leaves our infrastructure, and no contract
above us would let anyone else reach it.
Cookie
Contents
Lifetime
vuisio_id
Sixteen random bytes. Not your name, not your address, nothing that came from you.
Six months
vuisio_s
A visit identifier, to tell two visits on the same day apart.
Thirty minutes of inactivity
Both are marked HttpOnly. That means this page's JavaScript
cannot read them: it can neither copy them elsewhere nor hand them to
anyone, and a compromised script would get no further. It is also why what
your browser sends us carries no identifier at all: it could not.
Six months, not thirteen
The French regulator caps an audience measurement cookie at thirteen
months. We keep six. That is shorter than the rule allows, which makes
it a decision rather than compliance.
Withdrawing your consent
One button, here, right now. It clears both cookies, records the
withdrawal, and can delete what has already been measured.
That deletion actually works, which is not a given: it is only possible
because the identifier is a cookie. So called "cookieless" measurement,
which recognises people by their browser configuration, has no key to
delete, and the person becomes identifiable again on the next page load. We
can write this sentence; most banners cannot.
What is measured
The page path, the country, a device class, and the site you came from.
Nothing more, and above all not your IP address.
Your address is read at request time to derive a two letter country, then
forgotten. It is written nowhere: the table that receives measurements has
no column to put it in, which is a firmer guarantee than a promise not to
use it. We derive no city, no region, no internet provider.
The path only, never what follows the question mark. A
URL can carry an email address or a token; those are stripped before
anything is stored.
The domain you came from, never its full address, which
often contains the search you typed.
A device class: mobile, tablet or desktop. Not the exact
resolution, which would single out one device in a hundred.
A country, computed against a database installed on our
own servers. No geolocation service is called, which would amount to
sending your address to a third party.
Detailed measurements are deleted after forty five days. Only daily
totals remain after that, in which nobody is distinguishable.
What a refusal writes
Nothing. No cookie, and no "refused" row in our records either.
This is the point we most want in writing, because it is usually false
elsewhere. Recording a refusal would require an identifier to know whose
it was: so a cookie, so precisely what you just refused. Many banners do
it anyway.
Your refusal is kept by your browser, in a key named
vuisio_consent holding the word "refused" and a date. It is
never sent to us. It exists only so the question is not asked again on
every page, and it expires after six months: the same lifetime as the
cookie, so both answers age together.
Both buttons carry the same weight
"Accept" and "Refuse" are two buttons of the same size, side by side, at
the same level. A refusal demoted to a small grey link under a green
button is a sanctioned practice, and also a way of collecting consent
everybody knows is worthless.
Check it yourself
Thirty seconds, with nothing to install, in any browser. Do it before you
answer the banner: you will see there is nothing there.
Open the developer tools with the F12 key.
Go to the Application tab in Chrome, or Storage in Firefox.
Look at Cookies for the vuisio.com domain. Until you
have clicked "Accept", the list is empty.
Switch to the Network tab and reload: everything comes
from vuisio.com, without exception. No call to /api/collect
goes out before you agree.
Accept, then look again: vuisio_id appears, and the
HttpOnly column is ticked. That is what stops the page's
code from reading it.
This check is worth more than our word, and that is exactly why we point
you to it.
No external resource
Everything your browser downloads while reading this site comes from
vuisio.com. Not one request goes elsewhere.
Typefaces are served from our domain, never from a remote font service.
Icons are inlined at build time: they are shapes in the page's code, not
files to fetch.
The trailer is hosted on our servers. It only downloads if you press
play: until you click, only the still image is loaded.
The anti-bot check on the contact form is computed by your browser, from
a challenge issued by our server. No third-party service is called, no
image has to be deciphered and nothing is written into your browser.
Audience measurement is served from vuisio.com, by our own
infrastructure. The /api/collect address is relayed
internally to our portal: your browser never talks to another domain,
and the cookie stays first party.
No map, no icon font, no third party analytics script.
What we fixed
The trailer used to go through a third-party player, French and
cookie-free, but which itself loaded a playback library from cdn.jsdelivr.net, a foreign delivery network. Your IP address was therefore exposed to
it.
It was the site's only external request, and it left precisely from the
page that sells sovereignty. We removed it by hosting the video
ourselves. This paragraph stays here because a page that recounts only
its successes teaches nobody anything.
Inside the application
The Vuisio application sets no cookie either. It does store a few
preferences in your browser's local storage, and those never leave your
device.
This information is sent to no server. It exists only to save you
reconfiguring everything at each meeting. Clearing the site's data from
your browser removes all of it.
Key
What it is for
vuisio_name
The display name, so you do not retype it at every meeting
vuisio_audio_output
The speaker you chose
vuisio_flip_camera
Whether your own image is mirrored
vuisio_bg_prefs
The blur or virtual background you selected
vuisio_custom_bg
The background image you imported, which never leaves your device
vuisio_emoji_freq
The reactions you use most, so they come up first
vuisio_session_*
Your session identifier in a room, cleared when the tab closes
vuisio_breakout_*
The breakout room you belong to, cleared when the tab closes
Keys whose name ends in a star are written once per room. Those kept in
session storage disappear when the tab closes, with no action from you.
This list is taken from the code of the web client. It is exhaustive as of
the revision date shown at the top of the page.
What changed, and when
Until September 2026 this site set no cookie at all, and this page said
so. It was rewritten the very day measurement went live, not afterwards.
The previous version promised a compliant banner would appear
before any measurement tool was switched on, and that this
page would be rewritten the same day. That is what happened: the banner,
the collector and this page shipped in one release. A cookie page a week
behind the code is a lie, even an accidental one.
Any further change will be announced here, before it takes effect. And if
you found an undeclared tracker had slipped in here, the right
response is to write to us at contact@vuisio.com. We would remove it, and this page would say what happened.
A question about this document ?
Write to us: we answer requests to exercise your rights as well as questions of substance, including when the answer is that we do not know yet.
We would like to know which pages are read, using our own tool, hosted in France. One cookie, six months, no identifier this page's code can read, nothing sent to a third party. Refusing writes nothing at all: no cookie, and no row in our records.