OpenAI<\/strong> (api.openai.com) - used when ChatGPT is selected as the provider.\nTerms of use: https:\/\/openai.com\/policies\/terms-of-use\nPrivacy policy: https:\/\/openai.com\/policies\/privacy-policy<\/p><\/li>\nGoogle (Gemini API)<\/strong> (generativelanguage.googleapis.com) - used when Gemini is selected as the provider.\nTerms of use: https:\/\/ai.google.dev\/gemini-api\/terms\nPrivacy policy: https:\/\/policies.google.com\/privacy<\/p><\/li>\nDeepSeek<\/strong> (api.deepseek.com) - used when DeepSeek is selected as the provider.\nTerms of use: https:\/\/cdn.deepseek.com\/policies\/en-US\/deepseek-open-platform-terms-of-service.html\nPrivacy policy: https:\/\/cdn.deepseek.com\/policies\/en-US\/deepseek-privacy-policy.html<\/p><\/li>\nAnthropic<\/strong> (api.anthropic.com) - used when Claude is selected as the provider.\nTerms of use: https:\/\/www.anthropic.com\/legal\/consumer-terms\nPrivacy policy: https:\/\/www.anthropic.com\/legal\/privacy<\/p><\/li>\n<\/ul>\n\nThe API key needed to connect to the selected provider is supplied by the site administrator (by creating an account with that provider). The plugin does not send any data to any of these services without an active interaction from a visitor with the chat widget.<\/p>\n\n\n
\n- Upload the plugin folder to
\/wp-content\/plugins\/<\/code>, or install it through the \"Plugins\" screen in WordPress.<\/li>\n- Activate the plugin.<\/li>\n
- Go to AI Chat Bot<\/strong> in the admin sidebar menu.<\/li>\n
- Choose a provider (OpenAI \/ Gemini \/ DeepSeek \/ Claude) and paste the matching API key.<\/li>\n
- Save the settings - the chat widget appears on your site automatically.<\/li>\n<\/ol>\n\n\n
\nDo I need my own API key?<\/h3><\/dt>\nYes, in the free version. You get one by creating an account with the provider you choose (OpenAI, Google AI Studio, DeepSeek, or Anthropic\/Claude).<\/p><\/dd>\n
Can I choose which AI model to use?<\/h3><\/dt>\nYes. Each provider has a pre-filled default model, but the model field is a plain text input - enter any other model name the provider supports. Use \"Test connection\" to check it works before saving.<\/p><\/dd>\n
Can I customize how the bot responds?<\/h3><\/dt>\nYes, through the system prompt field. Describe what the bot should know about your site or business, how it should sound, what topics to stick to, and what to say when it doesn't know an answer.<\/p><\/dd>\n
Is this compliant with the EU AI Act?<\/h3><\/dt>\nThe widget shows visitors a disclosure that they're talking to an AI system, as required by Article 50 of the EU AI Act (in effect since August 2, 2026). It appears automatically in the chat header and as the first message; you can edit the wording but not remove it.<\/p><\/dd>\n
What happens if a settings change breaks something?<\/h3><\/dt>\nEvery saved change is added to a short history on the settings page. Restore any previous version with one click.<\/p><\/dd>\n
Does the plugin store my conversation data anywhere?<\/h3><\/dt>\nNot by default - the conversation history only exists in the visitor's browser, for the current session. The administrator can optionally enable a log of recent conversations (\"Conversation log\" section in settings, disabled by default) - when enabled, the first message and reply from each new conversation, along with the IP address, are saved to the WordPress database, visible to administrators only, capped at 50 entries with automatic cleanup after a set number of days. If you enable this, mention it in your site's privacy policy.<\/p><\/dd>\n
Can I use more than one bot on my site?<\/h3><\/dt>\nThis (free) version supports one, global bot configuration.<\/p><\/dd>\n\n<\/dl>\n\n\n
2.0.3<\/h4>\n\n\n- Security hardening: the system prompt now always includes an instruction telling the model to disregard attempts, embedded in a visitor's message, to override its instructions or reveal them.<\/li>\n
- The server now keeps its own short-lived record of each conversation (expires after 1 hour of inactivity) instead of trusting the conversation history sent by the browser, closing a prompt-injection-via-forged-history vector.<\/li>\n<\/ul>\n\n
2.0.2<\/h4>\n\n\n- Added a \"Rate this plugin\" link on the Plugins screen and in the plugin description.<\/li>\n
- Expanded the Features list and FAQ to cover model selection, system prompt customization, AI Act disclosure, and settings history\/undo.<\/li>\n<\/ul>\n\n
2.0.1<\/h4>\n\n\n- Renamed all internal function, class, option, and hook names from the
aicb<\/code>\/AICB_<\/code> prefix to zuczek<\/code>\/ZUCZEK_<\/code>, per a WordPress.org review requirement (the old prefix was flagged as too generic\/common to safely avoid collisions with other plugins).<\/li>\n- The chat widget shortcode is now
[zuczek_chat_widget]<\/code>. Removed the old, unprefixed [ai_chat_widget]<\/code> alias - also flagged as too generic.<\/li>\n- Fixed a race condition in the per-IP and daily message rate limiters: the counters now increment atomically instead of a plain read-then-write, so concurrent requests can no longer slip past the configured limits.<\/li>\n<\/ul>\n\n
2.0.0<\/h4>\n\n\n- Renamed the plugin to \"Zuczkowski AI Chat Assistant\" (slug: zuczkowski-ai-chat-assistant) to resolve a trademark conflict flagged during the WordPress.org review.<\/li>\n
- The chat widget shortcode is now
[aicb_chat_widget]<\/code> (prefixed); the old [ai_chat_widget]<\/code> still works as an alias.<\/li>\n- The \"Powered by\" footer link is now off by default and must be turned on explicitly in settings.<\/li>\n
- Moved
load_plugin_textdomain()<\/code> to the init<\/code> hook (was plugins_loaded<\/code>).<\/li>\n- Fixed outdated DeepSeek Terms of Use \/ Privacy Policy links in the External Services disclosure.<\/li>\n<\/ul>\n\n
1.0.9<\/h4>\n\n\n- The chat widget is now hidden from visitors until an API key is configured for the active provider - previously it always appeared once enabled, so visitors could open a chat that immediately replied with an error. Added an admin notice explaining this when no key is set.<\/li>\n<\/ul>\n\n
1.0.8<\/h4>\n\n\n- Added a \"Powered by\" footer toggle in settings (Widget appearance section), letting you turn off the \"Powered by Katalizator AI\" link at the bottom of the chat independently of Free\/Pro version. Enabled by default.<\/li>\n
- Added an optional email notification (Email notifications section, disabled by default) to the WordPress admin address when a visitor starts a new conversation with the bot. Includes a short preview of the first message, throttled to at most one email every 5 minutes.<\/li>\n
- Added an optional log of recent conversations (Conversation log section, disabled by default; new \"AI Chat Bot \u2192 Conversations\" screen) - first message and reply per conversation, capped at the 50 most recent entries, automatic cleanup after a set number of days (WP-Cron), a button to clear it permanently. When the log is enabled, the email notification links straight to the logged conversation instead of just the homepage.<\/li>\n
- Prepared for submission to the WordPress.org plugin repository: trimmed the short description to the 150-character limit, trimmed tags to 5, filled in
Contributors<\/code>, toned down mentions of the not-yet-built Pro version (plugin description, settings panel, FAQ) to avoid listing features that don't exist yet.<\/li>\n- Rewrote the plugin's source strings from Polish to English (the WordPress.org convention), with Polish shipped as a bundled translation (
languages\/katalizator-ai-chat-bot-pl_PL.mo<\/code>).<\/li>\n<\/ul>\n\n1.0.7-beta<\/h4>\n\n\n- Fixed a double-encryption bug in the API keys:
sanitize_settings()<\/code> was hooked as the global sanitize_option_aicb_settings<\/code> filter, which fires on EVERY update_option()<\/code> call on that option, not just when the settings form is submitted. This caused two problems - (1) the \"Delete key\" button would silently restore the old value instead of actually deleting it, and (2) every \"Delete key\" or history \"Restore\" call would re-encrypt the other, already-encrypted provider keys, corrupting them over time. handle_delete_key()<\/code> and handle_restore_settings()<\/code> now temporarily remove this filter before their own update_option()<\/code> call.<\/li>\n<\/ul>\n\n1.0.6-beta<\/h4>\n\n\n- Added the ability to permanently delete a saved API key from the database (a \"Delete key\" button next to \"Test connection\" for each provider). The action can be undone via the \"Change History\" panel.<\/li>\n
- Updated the documentation - it was missing mentions of Claude (Anthropic) support, added in the previous version.<\/li>\n<\/ul>\n\n
1.0.5-beta<\/h4>\n\n\n- Fixed a stale-security-token risk under long page-cache TTLs (e.g. LiteSpeed Cache) - the widget now fetches a fresh nonce when the chat is opened.<\/li>\n<\/ul>\n\n
1.0.4-beta<\/h4>\n\n\n- Removed the download counter (moved to a separate, non-distributed plugin \"Katalizator Site Tools\" - not a product feature, just a marketing tool for the zuczkowski.com.pl site).<\/li>\n<\/ul>\n\n
1.0.3-beta<\/h4>\n\n\n- Added a full LICENSE.txt file (GPLv2) - required before publishing to the WordPress.org repository.<\/li>\n<\/ul>\n\n
1.0.2-beta<\/h4>\n\n\n- Switched API key encryption from AES-256-CBC to AES-256-GCM (authenticated encryption), keeping backward compatibility.<\/li>\n<\/ul>\n\n
1.0.0<\/h4>\n\n\n- First release.<\/li>\n<\/ul>","raw_excerpt":"An AI chat widget for your WordPress site - ChatGPT, Gemini, DeepSeek, and Claude. Use your own API key and go live for free.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/cor.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/363471","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cor.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/cor.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/cor.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=363471"}],"author":[{"embeddable":true,"href":"https:\/\/cor.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/katalizatorai"}],"wp:attachment":[{"href":"https:\/\/cor.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=363471"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/cor.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=363471"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/cor.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=363471"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/cor.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=363471"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/cor.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=363471"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/cor.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=363471"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}