Cookies and trackers
Last updated: 2 September 2026
Nothing here is deposited to track you.
No measurement service is configured on this deployment: nothing is loaded and nothing is asked. Everything else is kept in your browser’s local storage, and the player stores nothing anywhere but on your own machine.
1. What cannot be refused
These entries are strictly necessary to the service you asked for: without them you could not stay signed in, the banner would come back on every page, and the usage figures would count one visitor as a hundred. Article 82 of the French Data Protection Act exempts this category from consent, and this category alone.
| Entry | What it is for | How long |
|---|---|---|
Your sign-insurroundify_sessioncookie | Proves it is you, so the account page opens without asking for your password every time. It is set only when you sign in, holds nothing but a signed reference to the account, and cannot be read by any script on the page. | 14 days, or until you sign out |
Your tracker choicesurroundify:consentlocalStorage | What you accepted or refused at the banner, and on what date. Keeping it avoids asking again on every page — and proves, if it ever comes to that, what was consented to. | 6 months, then the question is asked again |
Measurement identifiersurroundify:visitorlocalStorage | A number drawn at random, particular to this browser, used so the same person is not counted twice in the usage figures. It is tied to no account, no IP address and no device fingerprint, and never leaves this site. | 13 months, then renewed |
The sign-in cookie is only there once you sign in. Reading this site without an account deposits no cookie at all. It carries a signed reference to the account and nothing else — no email address, no name — and it is marked HttpOnly, so no script on the page can read it, and SameSite=Lax, so another site cannot make your browser send it. Signing out destroys it here and invalidates it on the server, which also ends every other session you have open.
The two local-storage entries are not sent to the server — unlike a cookie, which accompanies every request. Those stay on your device.
2. Our own usage counting
We also count, on our own server, a handful of gestures: the site being opened, which sections are read, which buttons are clicked, which platform tab is chosen, which install command is copied, and whether the room diagram gets dragged. This counting uses no cookie and no third-party service, retains no IP address, follows nobody from one site to another, and relies on a randomly drawn identifier renewed every thirteen months — the conditions on which the CNIL exempts audience measurement from consent.
What we get from it: totals and trends, so we can tell which part of the install loses people. Never anything about what you play or what your room looks like — the player does not report that, to us or to anyone.
3. Erasing this
From privacy settings you can see what is stored on this device and erase all of it. The same result can be had from your browser, by clearing site data for Surroundify.
Privacy settings4. And the player itself?
Nothing on this page applies to the software. Surroundify holds your rooms, layouts, mix profiles and audio in a folder on the machine you installed it on. It has no sign-in of its own — an account here is an account on this website, and having one gives this website no way into your player. The player sends no telemetry, and the only thing it ever asks of the internet is optional: ordering a certificate if you choose to claim a name under apps.surroundify.co.