Short answers. Longer explanations live in the docs.
The WordPress plugin is free and GPL-licensed, published in the official plugin directory. The plugin is a front end, so it needs a chat endpoint to produce answers: either the hosted Kivunly service, which is in beta and currently free, or a backend you run yourself.
Not if you use the hosted service — model costs are covered there during beta. If you run your own backend you pay your AI provider directly, which for a few hundred questions a month is typically single-digit dollars.
Yes. The plugin talks to whatever HTTPS endpoint you configure. It sends the visitor message, recent session history, the page URL and your site key, and expects a reply back. The full contract is in the docs.
It is specifically built not to. The backend fetches your real published pages and gives the model only those titles and URLs, and it is allowed to say it could not find a matching page rather than inventing one. That last permission is the part most chat widgets lack — see why AI chat widgets invent links.
It is one small CSS file and one small JavaScript file loaded in the footer, with no external dependencies. Nothing loads at all until you enable the widget and configure an endpoint.
No cookies, no analytics, no tracking pixels. The conversation stays in the visitor's own browser tab and disappears when the tab session ends. Details in the privacy policy.
Yes. All visitor-facing text comes from your own settings, the layout supports right-to-left sites, and the widget can sit bottom-left, which usually reads better on RTL sites.
Yes, for guiding visitors to products and content that are publicly published. It is a navigation and recommendation assistant, not a checkout or order-status system.
The backend re-reads your published content on a schedule through the public WordPress REST API, so posts published after setup are picked up without any action from you.
No. A hosted-service key is issued for one site and is refused on any other domain, so a copied key does not work elsewhere.
The widget shows a short error message inside the chat panel; the rest of the page is unaffected. The widget loads in the footer and only calls the endpoint when a visitor sends a message, so it never blocks your page from rendering.
Write to hello@kivunly.com, or use the support forum on the WordPress.org plugin page.