supportwebdigit

Hello,

The issue was that you hadn’t selected a context (meaning there was no source of responses for the chatbot). Without a context selected and created (embeddings), the chatbot won’t appear. This isn’t a bug, but rather a safety measure to prevent the chatbot from saying anything random. I think giving a one-star rating as a punishment for misusing the plugin is rather unfair, given the hundreds of hours spent on this plugin for free! A reconsideration of your rating would be appreciated.

Thank you

JC

Hello Gordon,

That’s a very important question — and I’m glad you asked it.
No, using the chatbot does not train the public ChatGPT model with your website content.
SmartSearchWP uses the OpenAI API. Data sent through the API is not used to train or improve OpenAI’s models. Since February 1, 2023, OpenAI does not use API customer data for training purposes

Here’s how it works in practice:

• The chatbot sends relevant content from your website as context to generate a response.
• The AI generates an answer.
• The data is not stored long-term for training.
• OpenAI acts only as a data processor.

If required, OpenAI also provides a Zero Data Retention (ZDR) option that can be activated in your API settings for eligible use cases, meaning no data is retained beyond what is strictly necessary for the request lifecycle

Now regarding your paywall question:

If your chatbot is placed behind a paywall, then:

• Only authenticated users can access it.
• The AI will only use the content you explicitly include in the chatbot’s knowledge base.
• The information remains restricted to your environment.
• It will not become publicly accessible through ChatGPT.

In short:
Your website content stays under your control. It is used temporarily to generate responses, not to train global AI models.

If you need stricter access control (e.g., limiting chatbot usage only to logged-in members or specific sections), that can also be configured or extended.

Hope this clarifies things — feel free to ask if you’d like more technical details.

Hello

I’m not sure it’s the plugin. You use 2 icon libraries: Font Awesome 6 Free and Font Awesome 6 Pro in your pages. I think you need to deal with this problem first, because if you deactivate Font Awesome 6 Free you won’t have any more problems.

Our css are normally all typed to be targeted solely at the chatbot.

Can you give it a try and let me know how it goes?

Thanks

JC

Hi,

The problem comes from the CSS: when I delete CSS the icon appears. Example :

.fa-classic, .fa-regular, .fa-solid, .far, .fas {/* font-family: “Font Awesome 6 Free”; */}

The CORS concern :

your site https://ballx.com.br tries to load a font which is hosted on another domain (https://dev.pixeel.net/…). As this is a cross-origin resource, the browser requires the dev.pixeel.net server to explicitly say “yes, you can read me” via a CORS HTTP header. However, the response does not contain Access-Control-Allow-Origin, so the browser blocks.

Hello,

Do you still have the problem? Can you put it into debug mode and send the results to hello@smartsearchwp.com?

Thanks

Hello,

The problem may be due to a cache issue. Try deactivating the cache to check whether the chatbot is displayed. If this is the case, you’ll need to exclude the plugin’s js from your cache.

JC

Hi Karel,

I’ve created a new account so that I can reply here, as the admin account doesn’t work for replying.

Here’s how to do it:

Is it possible to activate the plugin’s debug mode (in the general settings), initiate a discussion and then go to the error log and provide me with the logs? You can deactivate debug mode afterwards. That way I can try to understand the problem. Ideally, if you could provide me with the debug.log logs that would be even better 😉

You’ll have to tell me all this in the ticket I created when you created this topic on the forum, for confidentiality reasons.

Thank you very much

JC