Sitecommand
Sign inStart free

Security

How Sitecommand keeps your sites safe

A tool that can change your clients' websites must be harder to misuse than the websites themselves. Here is how access works, what is stored, and what an AI may do.

Start free Read the setup guide
  1. Your AI clientSigns in with OAuth you approved. Gets tools, never a password.01
  2. Hub inspectionMalware refused, insecure code sent back, risky actions held.02
  3. Signed requestSignature over the exact content and time, the site's own secret.03
  4. Site checks againSignature, replay, age, inspection, Code Lock, then it runs.04

Is it safe to let AI manage WordPress?

As safe as the limits around it.

The AI never gets a password. It gets tools; each site has its own access level; every change is inspected by the hub and again by the site, so the rules hold even if the hub were compromised.

  • Malware and backdoors refused
  • Insecure code returned with the fix
  • Risky actions held for the owner
  • Secrets masked in anything the AI can read
  • Website text treated as untrusted, never as instructions
Every change, inspected first
write_file uploads/x.phpRefused: looks like a webshellblocked
db_query with raw $_GET inputSent back with the fix: use $wpdb->prepare()fix needed
Create an administratorWaits for the account owner's approvalheld
Edit the About pageRunsallowed

Storage

Your sites' files stay on your sites.

Restore points and quarantined files live in protected folders on each site. The hub keeps account details, site addresses, encrypted secrets, status history and the activity log. Nothing is sold.

What is stored where

ON EACH SITE

Its secret, sealed

Restore points

Quarantined files

IN THE HUB

Site secrets, encrypted

Status and history

Activity log

Your sites' files

Account and connector

Locked down at every door.

Two-factor sign-in

With an authenticator app.

Roles

Read or edit members; clients see only their sites.

Activity log

Every action, by person or AI client.

Signed releases

The plugin installs only updates signed with our key.

Its own user

Acts as a user that cannot sign in. Remove it to cut access.

Code Lock

No installs or new admins until you unlock.

FAQ

Questions

How does the hub prove a request is really from you?+

Every request to a site is signed with that site's own secret and a timestamp; the site refuses unsigned, old or replayed requests.

What happens if a site's secret leaks?+

It only works for that one site. Reconnecting the site replaces it.

Can Sitecommand staff see my sites' content?+

The hub does not keep site content. Operators see account and status information, and every operator view is logged.

Is Sitecommand GDPR or SOC 2 certified?+

No certification today. You can export your data or delete your account at any time from Settings, and the hub never stores your sites' files.

Can I cut off Sitecommand from the site itself?+

Yes. Delete or demote the sitecommand user, or deactivate the plugin, and every request is refused.

Keep reading

Related

Code LockCode Lock blocks plugin installs, code snippets, code changes and new administrators on a site until you unlock it. Posts, pages and orders keep working.Read Your AIConnect Claude, Claude Code, Cursor or any MCP client once and manage every connected WordPress site through one server, with each change checked first.Read Malware sweepA weekly sweep of files, users and settings on every site. Cleanup moves files to quarantine instead of deleting them, and every step can be undone.Read

The sites keep running.
So do you.

Connect your first site in two minutes. Free during launch.

Start free How to connect a site