Cookies, and the two we use

Nesso sets two cookies. Both are needed to keep you signed in and to keep your record together. Neither is an advertising or analytics cookie — analytics and advertising are not live yet, and section 5 says what happens the day either is.

Last updated: 8 September 2026

1. What this covers

A cookie is a small piece of text a website asks your browser to keep and send back on the next request. Italian law — art. 122 of Legislative Decree 196/2003 — treats other ways of storing things on your device the same way, and the Garante said so expressly in its guidelines of 10 June 2021. So this page lists everything Nesso stores on your device, not only the cookies.

2. The two cookies

Name	What it does	How long	Type
nesso_session	Identifies the record you are building, so what you tap on one screen is there on the next. It holds a random identifier and a signature — no name, no address, nothing readable.	180 days, renewed while you use Nesso	First party, strictly necessary
nesso_user	Says which signed-in browser this is. It holds the identifier of one signed-in session and a signature, so that signing out of this browser — or out of all of them — actually ends it.	180 days, or until you sign out	First party, strictly necessary

Both are marked HttpOnly, so no script running on the page can read them; SameSite Lax, so another website cannot use them to act as you; and Secure, so they only travel over an encrypted connection.

3. What else is stored on your device

Offline pages (Cache Storage): A service worker keeps copies of pages you have opened, under the name nesso-offline-v1, so the viewing kit still works in a basement with no signal. It is filled by what you visit and never by anything else.
The offline map (device file storage): If you ask for the map to be available offline, the map archive is written to a folder named basemap in your browser private storage. It is written only when you press the control that offers it, and the same screen removes it.

Nesso uses no local storage and no session storage. Nothing in either of the two stores above is sent anywhere: they exist so that pages you already loaded keep working without a connection.

4. No third-party cookies today

Not live yet: an advertising network, retargeting or a conversion pixel — see section 5 for what happens before any of that ships.
No analytics provider yet. The product log we keep is our own, in our own database, and it sets nothing on your device.
No embedded video, no social buttons, no comment widget, no chat widget.
The typefaces are served from our own domain, so no font provider sees your request.
The map tiles and the map worker are served from our own domain, so no map vendor sees your request.

This is why the pages load without asking you anything: there is nothing to ask about.

6. Removing them yourself

Every browser lets you see and delete cookies and site data, usually under settings for privacy or for site permissions. Clearing site data for this domain removes both cookies, the offline pages and the offline map together.

What that costs: you will be signed out, and an anonymous record you had not attached to an account becomes unreachable, because the cookie was the only thing pointing at it. Signing in first, then clearing, keeps the record and loses only the browser session.

Blocking cookies for this domain entirely leaves the public pages readable and stops sign-in from working, because there is no other way for the site to tell one request from the next.

7. Changes

The date at the top is when this version was written. Any new cookie or store is added to the table above before it is set for the first time.

Yulia Sushkova · Borgata Levrette, 31, 10094 Valgioie TO, Italy · info@nesso.fit