AI Engine is a serverless plugin. No data is transmitted elsewhere other than your database and the used API (OpenAI / Azure / Pinecone / …). Therefore, if you are storing any data through the queries made to your chatbot, you are the only responsible person for their security and for complying with your region’s cybersecurity laws.
The only thing that reaches Meow Apps is the license and update check made by AI Engine Pro, like any premium plugin. Besides your license and site address, it includes two counters: whether MCP was used in the last 30 days (yes or no), and how many phones are paired with the Workspace app. Nothing about your content, your conversations or your users.
AI Engine uses AI models through third-party services’ APIs, so if you use an OpenAI model, you consent to OpenAI’s data usage and confidentiality practices, as you would when using their services outside of AI Engine.
AI Engine is compatible with self-hosted solutions, so you can run everything locally, from AI models to vectorized databases, and avoid using third-party services all together.
Is AI Engine GDPR compliant?
By default, AI Engine itself (as a plugin) does not infringe any GDPR rules. Depending on the options you enable, like Discussions or Insights, which save chat logs (locally in your database), it may cause you to violate GDPR rules, so make sure you enable these options with your users’ consent.
You can go to AI Engine settings to enable a GDPR consent message that locks the chatbot until the conditions are accepted.
You can also enable Privacy First in Settings > Others > Security. With it, AI Engine identifies visitors with a hash that is specific to your site instead of their real IP address, wherever it can. It does not cover everything: the conversation history (Discussions), uploaded files, debug logs and how long your AI provider keeps the data each have their own settings.
Protect sensitive data before it reaches the AI
If your visitors might type card numbers, Social Security numbers or account numbers into a chatbot or a form, you can stop them on your server before anything is sent to the AI. The Sensitive Data Guard snippet either blocks the message with a friendly notice or replaces the sensitive parts with [REDACTED].
Where are the chat logs saved?
All the data saved by AI Engine is stored in your WordPress database, and all AI Engine tables are prefixed with “mwai.” You can access them just like you would normally access your database for any other table.
You can find all of the chat logs inside the ‘wp_mwai_logs‘ table.
You can find all of the discussions inside the ‘wp_mwai_chats’ table.
You can view all conversation threads in the Discussions tab, provided that the Discussions feature is enabled in the AI Engine settings.
You can also inspect detailed logs for every request in the Insights tab, as long as the Insights feature is enabled in the AI Engine settings. Each log includes the full request data for easier debugging and analysis.
Where are images stored?
If you use Vision-capable models, your users might upload images. To be processed, these images first need to be stored, and this will be done directly on your local install. You have the choice between using the “filesystem” or “Media Library”. In both cases, images will be uploaded to your “uploads” folder.
- With the “filesystem,” the image will be renamed to have a random anonymized name and will exist as a single file.
- With the Media Library, it will use the WordPress upload function and create all the different thumbnails of the image with the original name.
No data is stored by MeowApps anywhere online. The image is then sent to OpenAI either by using BASE64 encoding or by sending the public URL of the image, depending on the setting you chose.
To change this behavior, you can go to Settings > Files & Media and change both Local Upload and Local Download to choose how the media are handled. You can also set the Expiration: expired files stop being used right away, and a daily cleanup then removes them from your server.
