Skip to content
Mikabot

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 and the AI model used
  • Technical request data: IP address, user agent, response time, and token counts
  • The status of the request, plus an error message when it failed

Failed requests are recorded separately, with the reason and the request that caused them.

What the widget stores in the browser

The widget uses localStorage and sets no cookies. It keeps the session ID, the visible conversation, and the last used language. The conversation copy is cleared after 24 hours, and starting a new conversation clears all three.

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 your AI configuration 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 logs support deleting one conversation or a selection at once.

Who can see conversations

  • The users invited to that chatbot, according to their role.
  • Nobody working on another chatbot in your account. Conversations belong to one chatbot.

Transcript emails

If you set transcript recipients under Chatbot settings, conversations are also emailed to those addresses. That copy lives in your mailbox and is outside Mikabot, so include it 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 your chat logs 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.