Cookies

Last updated: 7 September 2026. This site uses three cookies and none of them profiles you or sells you advertising. That is why you see no consent banner: technical cookies, the ones the site cannot work without, do not require it. What a cookie is A small text file the site stores in your browser to remember something from one page to the next — for instance that you have signed in. The cookies we use — nfw-site — keeps the session open for whoever signs in to the reserved area. It is created only after sign-in, lasts at most 8 hours and cannot be read by page scripts. Technical. — nfw-esterno — accompanies the round trip to Google, Facebook or LinkedIn when you choose to identify yourself with one of them. It lasts 10 minutes and then disappears. Technical. — Anti-forgery cookie (its name starts with .AspNetCore.Antiforgery) — protects the forms from submissions crafted by other sites. It lasts as long as the browser session. Technical. If you do not sign in and do not send forms, the site writes nothing in your browser. How we count visits without cookies To know which pages are read we record on our own server the page, the language, the referring site, the campaign parameters, the device type, the country and your IP address with the last part zeroed. No identifier follows you from one visit to the next. If your browser sends Do Not Track or Global Privacy Control we record nothing, and search engine robots are not counted. Third-party cookies We use neither Google Analytics nor advertising pixels, and no public page loads resources that set third-party cookies. If you choose to identify yourself with an external provider, during that step the provider may set its own cookies on its own domain: its notices apply. How to see and delete them Every browser lets you view and delete cookies from its settings, usually under "Privacy and security". Deleting nfw-site signs you out of the reserved area; the public pages keep working as before.

How we handle the data collected through the forms is explained in the privacy policy.