Built so that a mistake — human or AI — stays small.

The connection

• ●No WordPress passwords. Each site has its own digital identity; its secret key never leaves the site.
• ●Everything travels over HTTPS and every message is signed. Old, repeated or altered messages are rejected.
• ●Every action needs a one-time permission, valid only for that site and that step, for a few minutes.
• ●You can pause, renew or cut a connection at any time — from AICOMBase or from inside WordPress.

Limits on what can happen

• ●The site decides first: AICOM’s own settings in WordPress say what AICOMBase may do there, and AICOMBase can never go beyond that.
• ●A policy per site sets which kinds of work are allowed and how risky they may be.
• ●AI keys are limited to the sites and permissions you choose, and MCP Guard checks risky AI actions before they run.
• ●No work outside a session, and a backup before every change, so work can be undone.
• ●Roles for your team — a Viewer can’t change anything.

Security alerts

Signals from every site — failed logins, unexpected plugin or user changes and the like — become security alerts in one place. On every paid plan, Security Bot reads them across all your sites and tells you which ones matter, and a daily security check looks at your public setup.

Records you can trust

• ●An audit log of every security and settings change that can’t be edited or deleted — and never contains passwords or keys.
• ●Two-factor sign-in and a list of signed-in devices for every account.
• ●AI only ever receives the information a decision needs.

AICOMBase watches, records and coordinates — it isn’t an antivirus or a firewall. Keep your hosting’s security and backups in place.