Cookie policy
You can choose statistics and marketing separately. Declining them doesn't stop you browsing, watching the demo video or contacting us.
Last updated 20 October 2026. Controller and contact details in the privacy policy. This is a translation: the Italian version prevails.
1. What is switched on and when
Technical tools. The vilmor_consent cookie stores your preferences. The hosting provider handles the technical data needed to deliver and protect the site. Google Tag Manager is loaded to manage tags and choices: this involves a request to Google's servers even before you accept. The demo video is loaded from Cloudflare (media.vilmor.it) without cookies.
Anonymous statistics. PostHog is active from the moment the site opens, in cookieless mode: it counts page views and events without writing cookies or identifiers on the device. To distinguish visits on the same day, it calculates on its own servers an anonymous identifier from the date, browser, IP address and site, which changes every day and doesn't allow you to be recognized on later visits; browser and IP address are used only for that calculation and are not stored. The only thing left on the device is the technical entry that remembers this mode (see table). PostHog also records technical page errors, so that we can fix them. The data are processed on servers in the European Union.
Statistics. After consent, PostHog saves a cookie and a localStorage entry to recognize the browser on later visits, records click and scroll positions for heatmaps and clicks on elements that don't respond, and Google Analytics 4 (for visits and events) and Microsoft Clarity (for interactions, heatmaps and session replays, with forms marked for masking) are switched on. PostHog measures page performance (Web Vitals) and, after a choice on the updated banner, records browsing sessions. Form fields and the number shown after submission are masked; hidden fields are excluded and console recording is disabled. Web Vitals, heatmaps and recordings don't start without consent to statistics.
Marketing. After consent, Meta Pixel is switched on. From 12 November 2026 the pixel may also measure conversions on the device: according to Meta, it uses on the device the data you entered in forms, such as your email, and temporary device data, and sends Meta only the fact that a conversion took place and the campaign to attribute it to. If you successfully submit the form on the Italian Contact page (not the English one) or click a button that opens the WhatsApp chat, the server may also send the event to Meta's Conversions API, with the data described in the privacy policy. With the consent given on the updated banner, the server also tells Meta whether you then write to us on WhatsApp from the site's button and whether you book a call, as described in the privacy policy. To recognize the message, with marketing consent the button adds to the pre-filled text a few invisible characters with a random code for the browser, which stays in localStorage until marketing consent is withdrawn. We don't add a second Lead event through the Meta pixel. The same consent switches on the OpenAI pixel, which records page views and form submissions for campaigns on ChatGPT, as described in the privacy policy.
On your first visit, optional consents are denied. The banner is shown again to people who had already chosen, before the new PostHog recordings are switched on. You can accept all, decline, or save a separate choice. Consent to statistics doesn't automatically enable marketing.
2. Cookies used
The cookies depend on your preferences, your browser and where the visit comes from. The durations below refer to how long they stay on the device; they don't coincide with how long the data are kept in the providers' systems.
| Name | Category and provider | Purpose | Duration |
|---|---|---|---|
| vilmor_consent | Technical · Vilmor | Stores your choice on statistics and marketing. | 180 days |
| vilmor_attribution (sessionStorage) | Marketing · Vilmor | Keeps the campaign source in the browser tab and attaches it to the request forwarded to HighLevel. Only with marketing consent; removed on withdrawal. | Browser tab session |
| vilmor_wa_marcatore (localStorage) | Marketing · Vilmor | Keeps the browser's random code that the WhatsApp button adds, in invisible characters, to the pre-filled message, so that the first message is linked to the visit (see the privacy policy). It is shared across tabs, so a withdrawal from another tab stops the sending. Only with marketing consent; removed on withdrawal. | Until marketing consent is withdrawn |
| __ph_opt_in_out_phc_* (localStorage) | Technical · PostHog | Remembers whether PostHog may use a persistent identifier (statistics accepted) or must stay in the anonymous mode without cookies. It contains only this choice, no identifier. | Until deleted from the browser |
| ph_phc_*_posthog (cookie, localStorage and sessionStorage) | Statistics · PostHog | Recognizes the same browser on later visits and across vilmor.it and websites.vilmor.it; in sessionStorage it keeps the current session and window. Present only with consent to statistics. | 180 days; sessionStorage until the tab is closed |
| _ga, _ga_* | Statistics · Google | Distinguish visitors and keep session information for Analytics 4. | Up to 24 months, depending on configuration |
| _clck | Statistics · Microsoft | Keeps the browser's Clarity identifier for this site. | Up to 1 year |
| _clsk | Statistics · Microsoft | Links page views into one Clarity session. | Up to 1 day |
| _fbp, _fbc | Marketing · Meta | Support campaign measurement; _fbc may be present when the visit comes from a Meta ad. | Up to 3 months |
| __oppref | Marketing · OpenAI | Keeps the campaign identifier when the visit comes from an ad on ChatGPT. | 30 days |
| __obref | Marketing · OpenAI | Random browser identifier used to measure campaigns on ChatGPT. | 365 days |
Providers may use further cookies on their own domains depending on the browser and the features in use. Up-to-date references are in the documentation of PostHog, Google Analytics, Microsoft Clarity, Meta and OpenAI.
3. Changing or withdrawing consent
Open from the footer or from this page. The new choice applies to later processing and doesn't make processing already carried out under the previous consent unlawful.
The withdrawal is passed to the loaded tags and to PostHog, which stops recordings and the sending of new Web Vitals, returns to cookieless mode and deletes its own cookie, the localStorage entry and the tab's session data; it also prevents new CAPI sending without marketing consent. It doesn't automatically remove scripts already loaded by the page. Microsoft states that Clarity, after a refusal, may continue in a limited mode without cookies. To apply the loading block to the new choice you can reload the page; you can also delete existing cookies from your browser settings.
You can consult your browser's instructions to view, block or delete cookies. Blocking technical cookies may prevent your preferences from being remembered.
4. Providers, transfers and rights
The tools involve PostHog (data in the European Union), Google, Microsoft, Meta and OpenAI, as well as Cloudflare for the demo video; the latter may involve processing outside the European Economic Area. For the controller, purposes, legal bases, transfer safeguards, retention and how to exercise your rights, see the privacy policy.