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 :
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 PostHog, on its European servers, in Frankfurt. It is a third-party tool, and that is a change: until September 2026 this page announced a tool written by us and hosted by us, and it could say no data left our infrastructure. That is no longer true, and putting it any other way would be lying by omission.
What has not changed: there is no Google Analytics, no advertising network, no resale. PostHog is our processor under the GDPR, bound by contract, and works on this data for us alone. Its publisher is American, which puts the transfer under standard contractual clauses; the servers that receive our measurements are in Germany.
| Cookie | Contents | Lifetime |
|---|---|---|
ph_…_posthog | An identifier drawn at random by your browser, and the time of your current visit. Not your name, not your address, nothing that came from you. The cookie's full name contains our project's public key, which is why it is so long. | Six months |
The previous cookies were marked HttpOnly: this page's
JavaScript could not read them, so it could neither copy them elsewhere
nor hand them to anyone. PostHog's cookie cannot be, because the page's
own code sets and reads it. That is one protection fewer, and we would
rather write it here than let somebody discover it in their inspector.
In exchange, the identifier stays an ordinary cookie, one your browser can clear on its own and one the button below clears too. That is what makes withdrawal real, and it is the guarantee we chose to keep.
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.
One button, here, right now. It clears the cookie, records the withdrawal, and deletes at PostHog 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.
Since measurement moved to PostHog, the button does one more thing: your identifier travels with the request, and our servers ask PostHog to delete the person holding it, events included. Clearing our own records without that would be keeping the visible half of the promise.
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 on arrival to derive a two letter country, then set aside: PostHog is configured not to attach it to the event, so we never see it anywhere. We derive no city, no region, no coordinates, no time zone and no internet provider.
That last sentence needs a word of explanation, because it does not come free. PostHog adds the city, the region and the coordinates by default — enough to place somebody in their village. We installed a rule in their ingestion pipeline that erases all of it and lets only the country through, before anything is stored. It is a setting, not a promise: it can be inspected in our PostHog project, and it is what makes this paragraph true.
Measurements are kept at PostHog for one year, and the withdrawal button above deletes them without waiting for that.
Beyond the measurements above, your navigation on this site is recorded: mouse movement, clicks, scrolling, and what is shown on screen. It lets us see where people get stuck on a page rather than guess. We declare it in a separate box because it is not audience measurement, and filing it under that word would make it sound like less than it is.
What you type is never recorded. Every input field is masked at source: the contact form replays as empty boxes. Recordings are deleted after thirty days, and the withdrawal button above deletes them immediately along with the rest.
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", a date, and the
version of the text you answered. 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.
The version is there for a precise reason. If we change measurement tool or recipient, the text changes, so does the version, and your previous answer stops counting: you are asked again. That is what happened when we moved to PostHog, including for people who had refused — refusing a French tool is not refusing this one, it is never having been asked.
"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.
Thirty seconds, with nothing to install, in any browser. Do it before you answer the banner: you will see there is nothing there.
/ph goes out
before you agree.
ph_
appears, and calls to /ph begin. They go to vuisio.com and
are relayed by our servers to Frankfurt — your browser itself talks to
no other domain.
This check is worth more than our word, and that is exactly why we point you to it.
Everything your browser downloads while reading this site comes from vuisio.com. Not one request goes elsewhere.
/ph
address is relayed by us to Frankfurt. Your browser therefore never
talks to another domain, and the cookie stays first party.
No request from your browser goes elsewhere: that is accurate, and you can check it in the Network tab. But the relay does pass your measurements on to PostHog. The proxy protects your browser from a third-party domain and your cookie from automatic deletion; it does not keep the data with us, and we would rather write that than let the title imply it.
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.
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.
Two changes, and this page was rewritten on the day of each, not afterwards.
Until September 2026, this site set no cookie at all and this page said so.
In September 2026, audience measurement written by us and hosted by us went live, with a cookie and a banner.
Since then, measurement has been entrusted to PostHog, on its Frankfurt servers. We made that choice to have a tool we do not have to maintain ourselves, and it has a cost this page spells out rather than hides: data that leaves our walls, and a cookie the page's code can read. The consent question was put to everybody again, including those who had refused.
The rule we set ourselves still holds: the code and this page ship in the same release. A cookie page a week behind the code is a lie, even an accidental one — and that is as true of a change that flatters us as of one that does not.
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.
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.