gnuranza.it
This page describes the categories of cookies and similar technologies used by the site, their purposes, and how saved preferences can be changed.
Last updated
March 28, 2026
Technical consent record
The technical log is stored server-side for up to 180 days, unless a longer period is strictly necessary for defensive, audit, or abuse-prevention purposes.
Cookies and similar technologies include tools that can store or read information in the browser or on the device, or trigger requests toward third-party services that process technical or identifying data.
The site follows a privacy-first approach: only strictly necessary technologies are activated automatically, while non-essential services remain blocked until explicit consent.
The site distinguishes at least four categories: necessary or technical, functional, analytics, and marketing or profiling.
AnythingLLM and Elfsight are treated as functional and load only after consent. Google tag / GA4 is treated as analytics and is initialized with advanced Google Consent Mode, using denied defaults before the visitor makes a choice.
The AI chatbot is an optional service: it is not initialized until the visitor grants functional consent or has already stored a valid prior preference that enables it.
For visitors who have already granted that consent, the site may issue a lightweight technical request to the chatbot backend when the page loads in order to reduce first-response latency, without automatically opening the chat.
The site integrates Google tag with a technical setup that sets analytics_storage, ad_storage, ad_user_data, and ad_personalization to denied by default, and updates them only after preferences are saved.
This mode may still involve limited technical requests to Google before full consent, according to Google's advanced Consent Mode model. The final classification and legal suitability of this setup must be confirmed by the controller or privacy counsel.
The consent preference is stored in a first-party cookie for up to 180 days, unless the banner version changes or the user clears browser storage.
The technical consent record is retained on the server for the period described in this policy and in the operational project documentation.
Preferences can be reopened at any time through the 'Cookie preferences' command available in the footer and through the persistent dedicated button.
If you disable a category that was previously allowed, the site applies the new choice and may require a page refresh to stop integrations already initialized.
In addition to the internal preference panel, you can limit cookies or storage through browser settings, keeping in mind that blocking technical cookies may affect essential features.
For any enabled third-party services, this page lists privacy notices and opt-out links when available.
Cookie preferences
Necessary / technical
Always onRequired for security, session handling, consent preferences, and the contact form.
Functional
Enable chat, contact widgets, and other optional client-side features.
Analytics
Reserved for non-essential measurement if enabled by the controller.
Marketing / profiling
Reserved for campaigns, remarketing, or profiling only if enabled in the future.
Relevant services and technologies
Technical inventory used to align configuration, banner behavior, pre-consent blocking, and legal documentation.
Site technical cookies and form protection
Session handling, CSRF tokens, rate limiting, consent preferences, and abuse prevention.
First-party, always active on the site domain.
Not used for profiling.
No
Server-side locale and region resolution
Determine the initial language and whether the regional opt-out link should be shown.
Server-side only through reverse-proxy headers and Accept-Language.
Does not install browser cookies.
No
Google SMTP relay
Server-side forwarding of messages submitted through the contact form.
Backend only, triggered when the user submits the form.
No credentials are exposed to the browser.
AnythingLLM embed
Optional conversational assistance for property-related questions.
Third-party script loaded client-side only after functional consent.
The widget loads only after functional consent. If the visitor has already granted that consent in a previous visit, the site may send a lightweight warm-up request to the backend to reduce first-response latency without automatically opening the chat.
Yes
Elfsight WhatsApp Chat
Optional widget to open a WhatsApp contact flow through an external provider.
Third-party script loaded client-side only after functional consent.
Loading remains blocked until functional consent is granted.
Google tag / GA4
Statistical measurement of visits and page views across the site.
Google tag loads on all pages with advanced Google Consent Mode: denied by default before choice, then updated automatically after consent.
When analytics consent is denied, the tag remains in denied mode and should not use analytics_storage. Confirm the legal suitability of advanced Consent Mode with the controller or privacy counsel.
Optional marketing or profiling
Any future campaigns, remarketing, or profiling activities.
Currently inactive. Must only load after marketing consent.
Category is prepared but no marketing scripts are currently active.
Yes
Cookie preferences
We use always-on technical cookies for security, session handling, consent storage, and the contact form. Chat, external widgets, and other non-essential tools are loaded only after your choice.