Cookie Policy
The information stored on your device when you visit officina-digitale.net, listed one by one.
In short: this site sets no cookies. It stores a small amount of technical information in your browser's local storage, all of it needed to make the site work and none of it used to recognise you, follow you across sites or build profiles. We use no analytics, advertising or social network tools. That is why you are not asked for consent: the notice shown on your first visit is informational.
1. Cookies and similar technologies
Cookies are small text files that a site stores in a visitor's browser and that the browser automatically sends back to the server with every subsequent request. Alongside cookies there are other technologies for keeping information on a device — in particular local storage and session storage — which, unlike cookies, are not sent automatically to the server: they stay in the browser and can only be read by pages from the same site.
The law treats all of these technologies the same way, because what matters is not the technical mechanism but the fact that information is kept on the user's device. That is why we list them all, stating the type of each.
2. How this site approaches them
This site sets no cookies at all, neither its own nor third-party ones. The only information kept on your device is listed in section 3 and stored in the browser's local storage.
In particular, the site does not use:
- analytics or traffic measurement tools, from any provider;
- profiling, advertising or retargeting cookies or identifiers;
- social network buttons or widgets;
- fonts loaded from external providers: our typefaces are hosted on our own servers.
3. Full list of information stored
3.1 Set directly by us
| Name | Type | Purpose | Duration |
|---|---|---|---|
od_avviso_privacy |
Local storage | Records that you have seen the notice, so it is not shown again on every visit. It contains only the version date of the notice, no identifier. | Permanent, until you clear your browser data |
3.2 Set by the chat component (3CX)
The following information is written by the chat component built into the site. The first two are stored when the page loads, because they remember the state of the chat window; the others only if you actually start a conversation.
| Name | Type | Purpose | Duration |
|---|---|---|---|
callus.greeting_activated |
Local storage | Remembers whether the chat greeting has already been shown or dismissed | Permanent, until you clear your browser data |
callus.collapsed |
Session storage | Remembers whether the chat window is open or minimised | Until you close the browser tab |
chatInfoGuid and related session keys |
Local storage | Identify the ongoing conversation and keep it going if you reload the page. Written only if you start a chat | For the duration of the conversation |
| Technical information from Cloudflare Turnstile | Cookies and local storage used by Turnstile | The site's forms are protected by an anti-bot check. To tell a person from an automated program, Turnstile stores technical information on the device. The provider states that it is not used for advertising profiling. It is created only on pages that contain a form, and serves solely to prevent automated submissions | As set by the provider |
wplc-ga-initiatedwplc-ga-interacted |
Local e session storage | These belong to an analytics function of the chat component that is not operational on this site, because it requires an analytics tool we have not installed. They are still written when you interact with the chat, which is why we declare them. No data is sent to third parties. | For the duration of the conversation or session |
4. External services contacted by the site
Storing information on your device is one thing; contacting an external server is another, because it means your IP address is transmitted. For completeness we list those contacts too.
| Service | When it is contacted | Why |
|---|---|---|
| 3CX | On every page load | To download the chat component and check operator availability. The chat has to be ready before you need it, which is why it loads immediately |
| Formspree | Only when you submit a form | To deliver the form content to us |
| Cloudflare Turnstile | On pages that contain a form | For the anti-bot check on the contact and emergency forms. On the emergency form, if the check does not complete, the page immediately shows the phone number to call |
| Netlify | Always | The provider hosting the site: every page you read is served from its infrastructure |
The role of these providers and the safeguards for data transfers are described in our privacy notice.
5. How to delete this information
You can delete the information listed in section 3 at any time from your browser settings, under the option for clearing browsing data or site data. The exact steps vary slightly between browsers and are documented in each browser's help pages.
You lose nothing meaningful by deleting them: the notice will be shown once more and the chat window will return to its initial state. No site function stops working.
You can also prevent storage entirely by blocking site data in your browser settings. The site will still work, but the notice will appear on every visit, because we will have no way of remembering that you had already read it.
6. Why we do not ask for consent
The law requires prior consent for information kept on a device that is not strictly necessary to provide the service the user has requested. Typically this means analytics, profiling or advertising tools.
As the list in section 3 shows, there are none on this site: everything stored is there to make what you are using work. That is why the notice shown on your first visit has a single button and exists to inform you, not to collect a consent that would have no object.
If we ever introduce tools that require consent, we will not simply change the buttons on the notice: we will implement a mechanism that actually blocks those tools until consent is given, and we will update this document before switching them on.
7. Changes to this document
The list in section 3 is verified against the site's code. It is reviewed whenever the integrated services or their versions change. The date at the top of this document indicates the version in force; when changes are substantial, the notice is shown again even to people who had already dismissed it.