Skip to content

Data and privacy

Mikabot processes visitor conversations on your behalf. This page lists what is recorded, so you can complete your own privacy notice and answer audit questions.

What a conversation records

Each chat turn is stored as one log entry containing:

  • The visitor’s message and the answer that was given
  • The session ID that groups the turns of one conversation
  • The page URL where the chat happened
  • The detected language
  • Technical request data: IP address, user agent, device type, viewport, and response time
  • The status of the request, plus an error message when it failed
  • Flags noting whether the message appeared to contain an email address or a phone number, which is what triggers the transcript email

Requests that are rejected before a conversation starts are not shown in Chat conversations.

What the widget stores in the browser

The widget uses localStorage and sets no cookies. It keeps:

  • the session ID
  • the visible conversation, cleared after 24 hours
  • the last used language
  • a counter that caps the attention popup at twice per 24 hours
  • a debug flag, when debug logging has been switched on

Starting a new conversation clears the session ID and the stored conversation. The other values remain.

The widget does not require a customer login and does not track visitors across other websites.

What visitors add themselves

Anything a visitor types is stored as written. That can include personal data such as an order number, an email address, or a phone number.

  • Instruct the bot in Settings → Bot personality not to ask for personal details.
  • Send people to your contact page or contact email for anything that needs an identity.
  • Delete conversations that contain data you should not keep. Chat conversations supports deleting one conversation or a selection at once, and deletion is permanent.

Deleting conversations does not reduce the message count already billed for that period.

Who can see conversations

  • The users invited to that chatbot, according to their role. Viewer is read-only and is the right role for colleagues who only report.
  • Nobody working on another chatbot in your account. Conversations belong to one chatbot.

Transcript emails

If you set Email Recipients under Settings → General settings, conversations are also emailed to those addresses whenever a visitor leaves an email address or a phone number. The optional periodic chat report sends a summary on the same basis.

Those copies live in your mailbox, outside Mikabot, so include them in your own retention rules.

Your responsibilities as the shop

  • Mention the chat assistant and its purpose in your privacy policy.
  • State that conversations are stored, and how long you keep them.
  • Handle access and erasure requests by finding the conversation in Chat conversations and deleting it.
  • If you use consent tooling, decide whether the widget loads before or after consent. It is a plain script tag, so your consent manager can gate it.