AumChat

These rules are decided inside WordPress. Nothing about them is sent anywhere; they only choose whether the loader script is printed on the page.

When a rule is not enough, one filter decides per request:

add_filter( 'aumchat_show_widget', function ( $show ) { return is_checkout() ? false : $show; } );

Source code

The released source is on GitHub at github.com/aumcreate/aumchat-wp — bug reports and pull requests are welcome there.

More from AumCreate

How to install this plugin, what it needs, and where the settings live: aumcreate.com/plugins/aumchat

Also free from AumCreate: llms.txt and schema for AI search, AI crawler control, AI translation for WordPress, and digital-goods checkout for WooCommerce: aumcreate.com/plugins

External services

This plugin connects your site to AumChat , a chat service operated by AumCreate at https://chat.aumcreate.com . The plugin is useless without it, so connecting a site is what grants consent for the exchanges below.

1. The chat widget, in your visitors’ browsers.

Once a site is connected, every public page loads https://chat.aumcreate.com/loader.js and, when a visitor opens the chat, a frame from https://chat.aumcreate.com/ . This happens in the visitor’s browser, not on your server. AumChat receives:

• the site key, and the address and title of the page the visitor is on;
• the address that referred them, their browser’s language and user agent;
• the country their connection comes from, as reported by the hosting provider (IP addresses are not stored);
• a random visitor identifier the widget stores in the browser’s local storage, so a conversation continues as the visitor moves between pages;
• anything the visitor types or attaches in the chat, and an email address if they choose to leave one.

Conversations are kept for the retention period the site owner sets in the workspace (12 months after a conversation closes by default, and they can be deleted sooner). Visitors who never open the chat still cause the loader script to be fetched.

2. A status check from your server, made in the admin.

When you press Connect, save a key by hand, or press “Check again”, this plugin calls https://chat.aumcreate.com/api/plugin/site . It sends the site key and this site’s domain, and nothing else. The answer is the site’s name, its saved domain, and when the widget was last seen. No visitor data is involved and this request never happens on a front-end page view.

3. Your product catalogue, if you turn on product sync.

Product sync is off until you paste a sync token from your AumChat dashboard. Once you do, this plugin sends your published products to https://chat.aumcreate.com/api/plugin/products — when you press “Sync products now”, and once a day from then on — so the assistant answers with current prices and stock instead of whatever it saw the day you connected. For each published product it sends the product’s post ID, name, price and currency, category, SKU, permalink, image address, short description, full description, specification list and stock status. It also sends the site key this plugin is connected to — not as a credential, but so that AumChat can refuse a catalogue pushed with a sync token belonging to a different site in your workspace, instead of quietly filing it under the wrong one — and the request identifies itself with this site’s address. Drafts, private and trashed products are not read. Nothing about your visitors, customers or orders is sent, and no order, customer or user record is read at any point. Remove the sync token and the daily job sends nothing; deactivate the plugin and the job is removed.

4. Connecting an account.

The Connect button sends you to https://chat.aumcreate.com/wp-connect with this site’s domain and the address of this settings page, so the workspace can send the site key back. You sign in on AumChat’s own pages; this plugin never sees your password.

Terms of Service: https://chat.aumcreate.com/legal#terms Privacy Policy: https://chat.aumcreate.com/legal