The service needs your catalogue and your pages to answer correctly. It doesn't need your customers. Here we write exactly what is sent, when, and what never leaves the shop.
To answer “where is my order”, the assistant needs the order's status, not the person behind it. That's why the plugin sends the number, the status and the shipment, and leaves the personal details where they are.
Every shop has its own key, and behind it only its own data. The key is accepted only when the request comes from the domain it was issued for, so a copy of the plugin on another site gets nothing.
Nothing leaves before you connect the shop. After that, only the following.
Name, descriptions, address, image, prices, stock, categories, brand, attributes, variations, average rating and the text of the three newest reviews, never who wrote them.
The text of your published pages and articles. Not the cart, the checkout or the account page.
Number, status, date, total, products, shipping method and tracking number. Without names and without addresses.
Whatever the visitor writes, together with a random identifier, the page they're on, where they came from and the pages they saw. Only if they write a message.
The site address, the versions of the plugin, WordPress, WooCommerce and PHP, the language and the currency.
The product's details and your notes, or the topic and keywords of an article.
Six things that apply to every plan.
The key, the domain, the plan and the tokens are checked on the server every time, not inside the plugin.
The service keeps only a hash of the site key. If you lose it, you issue a new one.
The chat has a message limit per visitor and per shop, so no one can spend your tokens.
Conversations and messages are deleted automatically after 90 days.
Products, pages, orders and the chat itself turn off separately from the plugin settings.
Disconnecting stops every sending. Deleting the site from the dashboard erases what the service keeps.
It asks for the email or phone the order was placed with and compares it with the hash the shop has sent. The email and phone themselves never reach the service.
You, from your dashboard. To produce an answer, the message and the relevant parts of your catalogue go through an AI model provider acting on behalf of the service.
On Supabase and Netlify infrastructure. The details are in the Privacy Policy and the Data Processing Agreement (DPA).
Only what loading a file reveals: the chat loads from our server, like an image or a font. The visitor's path stays in their browser and is sent only together with a message they write themselves.
It's a good idea. The plugin adds suggested text about the chat to WordPress's privacy policy guide (Settings → Privacy), and you decide whether to use it.
The free plan includes one shop.
Start for free