Privacy and GDPR

Chat conversations contain personal data, and you are responsible for it as the store owner. This page explains where that data goes and the tools the plugin gives you to handle it.

This page describes what the plugin does. It is not legal advice: your privacy policy, your legal basis and your agreements with the services you connect remain your responsibility.

Where your data is stored

  • Conversations, leads, agents and settings are stored in your own WordPress database, on your hosting. We do not receive a copy of your conversations.
  • Uploaded documents, such as knowledge base PDFs, are stored on your server.
  • API keys are encrypted before being saved to the database.
  • In the visitor’s browser, the widget keeps a session identifier and the recent chat history in local storage, so the conversation survives when the customer moves from page to page.

What is sent to the AI provider

To answer a message, the plugin sends a request from your server to the AI provider you configured, using your API key. The request contains:

  • the customer’s messages and the earlier messages of the same conversation;
  • your instructions: the system prompt, the bot’s name and tone;
  • your knowledge base content;
  • product information from your catalogue, when product sync is on;
  • the details of an order, when a customer looks one up in the chat. Guests must give the order number together with the billing e-mail or phone number before any order data is used.

Whatever a customer types is passed on, including any personal details they choose to write. How the provider stores and uses that data depends on your contract with them, so read their data processing terms and name them in your privacy policy. You choose the provider on the AI Provider screen.

Other services you may connect

Data leaves your site only for the features you turn on:

  • Escalation alerts go to the e-mail address you set and, if configured, to your Slack or WhatsApp webhook.
  • Webhooks Pro send event data, which can include a customer’s name and e-mail, to the URL you enter. See Webhooks.
  • Flow Builder API Call nodes Pro can only contact hosts you have added to the allow-list.
  • Google Docs and Sheets are read from Google when you import or refresh them. Nothing about your customers is sent.
  • Licence checks: a site with a Pro key regularly confirms it with our licensing service, sending the key, the site address and name, and the plugin version. No conversation data is included.

Set IP hashing and retention

  1. Open AI Assistant → Settings → Behavior and scroll to Privacy & Data.
  2. Keep Hash IP Addresses on. The plugin then stores a SHA-256 hash of the visitor’s IP address instead of the address itself. It is on by default.
  3. Set Data Retention (days). Conversations older than this are deleted automatically. The default is 90 days; choose the shortest period that still lets you handle complaints and returns.
  4. Set Auto-Close Inactive Conversations (days). Conversations with no activity for this long are marked as closed. Closing does not delete them.
  5. Click Save Settings.

Answer an export or erasure request

The plugin plugs into the personal data tools built into WordPress, so a chat request is handled together with the rest of the customer’s data.

Export a customer’s conversations

  1. In WordPress, go to Tools → Export Personal Data.
  2. Enter the customer’s e-mail address and send the request.
  3. Once it is confirmed, download the export. It contains a section for the chatbot with each conversation’s session ID, start date, status and messages.

Erase a customer’s conversations

  1. Go to Tools → Erase Personal Data.
  2. Enter the customer’s e-mail address and send the request.
  3. Once it is confirmed, run the erasure. The plugin deletes the conversations recorded with that e-mail address, together with their agent sessions and any pending escalation.

Two limits to know:

  • Both tools find conversations by e-mail address. A visitor who chatted without ever giving an e-mail cannot be matched; those conversations are removed by the retention period, or you can delete them by hand.
  • The erase tool covers conversations. If the customer was also captured as a lead, delete that entry under Automations → Leads & Emails.

Delete conversations by hand

Under Inbox → Conversations you can select conversations and use Delete Selected at any time.

When a customer asks for a human, the escalation form asks for their name and e-mail and includes a consent checkbox for sharing that information for the support request. Mention the chat, and the AI provider behind it, in your privacy policy so customers know before they type.

If your Pro subscription ends

Returning to the Free feature set does not delete any conversation, lead or setting. See Licence and activation.

Still stuck?

Check the troubleshooting guide, or contact support and tell us what you tried.