Documents
Cookie Notice
Which cookies and which data in the browser are used by this website, the dashboard and the chat of Chattopus. Version 1 of 19 November 2026.
In short
This website does not use cookies or analytics. The dashboard uses only technical cookies for signing in: one to keep you signed in, and two more when the sign-in code by email is switched on. The chat that our customers put on their websites does not use cookies. That is why we do not ask for your consent and there is no cookie banner.
This website
The pages of this website do not set cookies and do not load analytics, advertising, fonts or content from other websites. If one day we add tools of this kind, we will say so here first.
When the website is available in more than one language and you choose one from the language menu (or from the bar that suggests yours), the website remembers your choice in the browser's local storage, under the key site.lang (the language code, for example it), so that it no longer suggests another language. Before you make a choice it saves nothing. The choice stays until you clear the website's data from the browser.
If you find our chat at the bottom right, what is written below under “The chat on our customers' websites” applies to it.
The dashboard
When you sign in to the dashboard (the address that ends in /app), the browser receives one cookie, and two more when the sign-in code by email is switched on:
| Name | What it is for | Duration |
|---|---|---|
sid | Keeps you signed in to the dashboard after you sign in. It is HttpOnly (the page's scripts cannot read it), SameSite=Lax and, on https addresses, Secure. | 30 days from the last use, or until you sign out with “Sign out” |
ac | Only with the sign-in code by email: remembers which sign-in, sign-up or invitation is waiting for the code we sent you. HttpOnly, SameSite=Lax, Secure on https addresses, sent only to the sign-in addresses (/api/auth). | One hour from the last code sent, or until you enter the right one |
rd | Only with the sign-in code by email, if you leave “Remember this device for 30 days” ticked (it is ticked to begin with; you can untick it): a random code that lets us recognise this browser, so that we do not ask you for the code here. HttpOnly, SameSite=Lax, Secure on https addresses, sent only to the sign-in addresses (/api/auth). | 30 days from when you entered the code, or until you sign out with “Sign out”, make us forget it from the Account page or change your password from another device |
The dashboard also remembers a few things in your browser's storage, without cookies:
- some choices, for example the language and the last organisation you opened;
- the replies to visitors you are writing (for 14 days at most) and those waiting for the connection to be sent (until they are sent), so that they are not lost if the network drops or you reload the page: they are saved under your name and are also deleted when you sign out with “Sign out”;
- the dashboard's files (the program, not your data or the visitors' data), kept by the browser so that the dashboard opens at once even on a slow connection, and replaced with every new version.
The chat on our customers' websites
The chat does not set cookies. To pick up the conversation while the visitor moves from one page to another, and to let them find the team's reply when they come back to the website, it saves in the browser's local storage (localStorage) a technical code of the conversation and the most recent messages, and in the browser's session storage (sessionStorage) whether the chat window is open. This data stays on the device and expires 30 days after the chat was last used or after the last reply from the team that reached the chat, if that is more recent, and never later than the period for which the website keeps conversations (15 days on the Low plan).
After the visitor has used the chat for the first time (written a message, asked for a person or left their email address), the conversation also holds a random code of their browser, which the service gives them at that moment. It has the same expiry as the conversation, and the chat sends it when the visitor starts another conversation on the same website, so that the website's team recognises their earlier conversations. Before the visitor uses the chat, this code is neither saved nor sent. Each website has its own code, and the chat page opened from a link has a separate one.
The entries the chat saves in the browser (each name ends with the website's key, pk_ followed by 24 letters and digits):
chat-assistenza:, in local storage: the conversation, that is its technical code, the most recent messages and, after the chat's first use, the browser's code. It expires 30 days after the chat was last used or after the last reply from the team that reached the chat, never later than the website's retention period.chat-assistenza:open:, in session storage: whether the chat window is open, so that it stays open when the visitor changes page. It is deleted when the tab is closed.chat-assistenza:resumed:, in session storage: the moment the visitor opened the conversation from the link in the email with the team's reply, so that the chat does not ask again for the email address they already left. It is deleted as soon as the chat has read it, and in any case when the tab is closed.chat-assistenza:teaser:, in local storage: that the visitor has already seen the teaser bubble next to the chat button, when the website shows it only once. It stays until the website's data is cleared from the browser.chat-assistenza:teaser-x:, in session storage: that the visitor closed the teaser bubble with the ✕. It is deleted when the tab is closed.
Why consent is not needed
These are tools strictly necessary to provide the service you asked for (signing in to the dashboard, using the chat), so they do not require your consent (Article 122 of Italian Legislative Decree 196/2003 and the Guidelines on cookies and other tracking tools of 10 June 2021 of the Italian data protection authority, the Garante).
You can delete them at any time from your browser's settings, by clearing the website's data: the dashboard will ask you to sign in again and the chat will start a new conversation.
For the rest of the data we process, read the Privacy Notice.