Data policy

Last updated 11 November 2026

The detail behind the privacy policy: exactly what is stored, where it goes, which providers are involved, how long each kind of data is kept, and how to export or delete it.

What is stored in Sitecommand

  • Account: email, name, account address, plan, settings, team members and their roles.
  • Sign-in: password hash and two-factor details (held by our sign-in provider), session cookies in your browser.
  • AI clients: the name and redirect address of each client you approve, and its access tokens as hashes.
  • Sites: address, platform and versions, the list of installed software, a signing secret (encrypted), tags, schedules and permission scope.
  • Monitoring results: uptime probes, health checks, domain and certificate dates, performance scores, outside security checks, sweep reports, update runs, incidents.
  • Activity log: tool name, site, time, result and who started it. Not the code, queries or file contents.
  • Alert channels: the webhook link, bot token or chat ID you enter, and delivery errors.
  • Google Analytics (only if the owner connects it): the connected Google login's email and account ID, an encrypted access token, the list of its Analytics properties with their website addresses, and for each linked site the latest 28-day traffic summary.
  • Reports and status pages you create, with the branding you set.
  • Support: tickets and the details you agree to attach, wishlist requests, feedback on Commander answers (your question, up to 300 characters, never the answer or site data) and on sweep results.
  • Crash reports: error text with tokens, emails and identifiers masked.

What stays on your site

Your content, database and files stay on your own hosting. The connector keeps its own records there: its settings, a local audit table, restore points made before updates, files moved to quarantine by a cleanup, and the Code Lock baseline. Removing the WordPress plugin deletes its settings; the quarantine folder is kept so nothing you might need is lost.

Providers we use

These providers process data for us. We choose them for the job listed and send them only what that job needs.

  • Vercel (hosting and serverless functions, and the AI service behind Commander): everything that passes through the hub. Functions run in Singapore.
  • Supabase (database and sign-in): all stored account and site data, and sign-in emails such as password resets.
  • Google (the AI model that answers Commander questions, through Vercel's AI service): your question and the site information needed to answer it.
  • Google (sign-in and Analytics, only if you use them): Google confirms who you are when you sign in with Google, and answers our read-only requests for your Analytics properties and their traffic numbers.
  • GitHub (connector releases): your sites download connector updates from GitHub. No account data is sent.

Outside services used for checks

To check your sites, the hub asks public services about them. Each receives only what is listed.

  • Google PageSpeed Insights: the site address, for performance scores.
  • Google Web Risk and abuse.ch URLhaus: the site address, to see whether it is on a malware or phishing blacklist.
  • OSV.dev: names and versions of the npm or Composer packages your app uses, to find known vulnerabilities.
  • Wordfence Intelligence: we download its public vulnerability feed; nothing about your sites is sent.
  • DNS and domain registries (Google and Cloudflare DNS over HTTPS, registry RDAP servers): the domain name, for DNS, and expiry dates.
  • WordPress.org: file checksums for core, plugins and themes, requested by your own site.

Services you connect yourself

Alert channels (Slack, Discord, Telegram, your own webhook, and automation tools such as n8n, Make or Zapier behind it) and the AI clients you approve receive data because you set them up. They are not our providers; their own terms and privacy policies apply to what they receive.

How long data is kept

  • Account, sites, settings, activity log, incidents, reports: while your account exists.
  • Individual uptime probes: 7 days. Daily uptime summaries are kept with the account.
  • Daily health history: 90 days.
  • Sweep reports: the latest 12 per site, plus every sweep that found malware.
  • Crash reports: 30 days.
  • AI client access tokens: valid for 1 hour; refresh tokens for 90 days; expired and revoked tokens are cleared after 30 days.
  • One-time connect keys: expire after 10 minutes if unused.
  • Google Analytics summaries: only the latest 28-day summary per site is kept; each daily refresh replaces it. The token and summaries are deleted when the Google login is disconnected.

Our providers keep their own short-term backups and logs for a limited time under their own policies, so deleted data can remain in those for a short period before it is overwritten.

Export

The account owner can download the account's data at any time from Dashboard → Settings → Export.

Deletion

  • Disconnect a site: removes that site and its monitoring history from your account. The site is told to forget the pairing.
  • Delete your account (Settings, owner only): access for every AI client is revoked first, then the account, its sites, settings and history are deleted from the live database and the sign-in is removed. This cannot be undone.
  • Leave an account (team members): your membership and your AI clients for that account end at once.
  • By request: write to privacy@sitecomand.xyz from the account's email address and we will delete it for you within 30 days.

How data is protected

  • Site signing secrets are encrypted before they are stored; on the site itself the secret is sealed with a key kept outside the database.
  • Access tokens and connect keys are stored as hashes, never in readable form.
  • Every request between the hub and a site is signed, time-limited and protected against replay.
  • Connector updates are installed only when their signature and file hash check out.
  • Staff see counts and account details needed for support; opening a specific site's details is logged, and the staff console requires two-factor sign-in.

See the security page for how the product protects your sites.

Questions

Write to privacy@sitecomand.xyz. If you need a specific statement about data handling for your own clients, ask and we will tell you plainly what we can and cannot confirm.

Data policy: storage, retention, deletion · Sitecommand