When you have a chat on your website, your privacy policy must say what it keeps, for how long, and what it stores in the browser. Muzau provides this text, in French or English, and its chat follows it. A conversation that stays anonymous is deleted 30 days after its last message, the fingerprint of the IP address within 48 hours, and the browser identifier is used only to find the conversation again. It is up to you to add it, with your contact address.
A form collects what the visitor chooses to send, field by field. A chat receives sentences typed as the exchange goes on, often by someone who leaves no name or address and will never come back to claim anything. Yet those messages are kept, read by a provider that writes the reply, and a small identifier stays in the browser to find the conversation again.
Your policy must say so in plain words: what is kept, for how long, who processes it, who to write to. This text binds your company, not your tool: it must only promise what the chat really does. This is the part Muzau gives you ready; reviewing and publishing it remain yours.
On your chat agent's page, Muzau shows the text to add to your privacy policy, in French or English depending on your account's language. It speaks to your visitors, in your company's name, and presents Muzau as the provider that supplies the chat on your behalf. The ready-to-send message for the person who manages your website contains it too, with the line of code to paste: see putting a chatbot on your company's website. All that is left is to write your contact address into it.
A conversation where the visitor left no address, name or number is deleted 30 days after its last message, with nothing for you to do. One where they left their email or phone, or whose request was passed on to you, is not deleted at 30 days: it joins your customer exchanges and follows their retention period. Until then, you read the 20 most recent conversations on the agent's page, each in full.
The chat limits the number of conversations opened from the same connection, to slow down automated sending. For this it relies on a technical fingerprint derived from the IP address, deleted from all conversations after 48 hours at most, including those that remain. The address itself is never stored.
The chat stores an identifier in the browser that is used only to find the conversation again. A visitor who closes the tab and comes back the next day finds it again, from the same browser, and a button lets them start a new one. It is not an advertising cookie: it does not follow the visitor to other sites. In private browsing, or if the browser blocks storage, the chat works but does not keep the conversation from one visit to the next.
Whatever the tool, a visitor should be able to read in a minute what happens to what they type. Six points are enough:
Three mistakes come up again and again. Writing "no data is kept" when the conversation is. Copying another site's policy, which describes another tool. Changing tool or setting without rereading the text. The "Artificial intelligence" notice shown in the chat is a different question: see should you tell a customer they are talking to an AI. For the GDPR principles applied to AI, the AI glossary sums them up; it is not a substitute for legal advice.
Autonomous does not mean unchecked. You set the level of autonomy of every agent, its limits cannot be crossed, everything it does is recorded in a plain-language log, and one gesture stops it all.
For the tasks you don't have time for. You give the address of your website, then describe the work in your own words. Nothing to install.