Privacy policy

Last updated 11 November 2026

What Sitecommand collects about you and the websites you connect, why, who else handles it, and the choices you have. The short version: we collect what the service needs to work, we do not sell it, and we do not use it for advertising.

Who we are

Sitecommand is operated by Noman E Jawad, an individual based in Bangladesh ("we", "us"). For anything about your privacy or this policy, write to privacy@sitecomand.xyz.

This policy covers the Sitecommand website, the dashboard, the connectors you install on your sites (the WordPress plugin and the Node.js and Laravel packages) and Commander, the built-in assistant.

What we collect

About you and your account

  • Your email address, the name and account address (slug) you choose, and your password, which is stored only as a hash by our sign-in provider.
  • Two-factor authentication details if you turn it on.
  • If you sign in with Google: your Google account's email address, name and Google account ID. We never see your Google password.
  • Team members and clients you invite: their email address and role.
  • Settings you choose: alert channels and their addresses or webhook links, quiet hours, report branding, notification preferences.
  • Messages you send us: support tickets, wishlist requests, and thumbs up or down on Commander answers and sweep results.

About the sites you connect. The site address, its software versions (core, plugins, themes, packages), a secret used to sign requests (stored encrypted), and the results of checks: uptime and response times, health, domain and SSL certificate dates, security sweep findings, update history, incidents and the state of Code Lock.

Activity log. Each action taken through Sitecommand is recorded: which tool ran, on which site, when, whether it worked, and which AI client or person started it. The log does not keep the code, database queries or file contents that were sent.

Technical data. Your IP address is used briefly to limit abuse (for example too many sign-in attempts). When a page crashes we record the error with tokens, email addresses and identifiers masked.

We do not collect payment card details: Sitecommand is free during launch and takes no payments.

Google sign-in and Google Analytics

Sign in with Google is optional. It asks Google only for your email address, name and account ID, and uses them to sign you in.

Connecting Google Analytics is optional and done by the account owner. It gives Sitecommand read-only access to the Analytics properties of the Google login you connect. We read the list of your properties with their website addresses, and for each property matched to one of your sites a 28-day summary: sessions, visitors and page views by day, the top pages and the traffic sources. We store that summary and an encrypted access token. We cannot change anything in your Analytics account.

How Google data is used. Analytics data is used only to show your traffic to you and the people in your account. It is not sold, not shared with anyone else, not used for advertising, not used to train AI models, and no person at Sitecommand reads it unless you ask us to for support, it is needed for security, or the law requires it. Sitecommand's use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

Disconnecting. Remove a Google login in Dashboard → Integrations at any time: its token and the traffic summaries that came from it are deleted, and we ask Google to revoke the access. You can also remove Sitecommand at myaccount.google.com/permissions.

What we do not collect

  • We do not copy your site's content, database or files into Sitecommand. Requests from your AI client pass through the hub to your site and the answers pass back; they are not stored, apart from the activity log entry described above.
  • We do not collect information about your sites' visitors or customers.
  • We do not use advertising or cross-site tracking cookies.

Why we use it

  • To run the service you signed up for: sign you in, connect your sites, carry out the checks and actions you or your approved AI clients ask for, and send the alerts you set up.
  • To keep the service and your sites safe: signing requests, limiting abuse, blocking code that matches malware patterns, and keeping the activity log.
  • To fix and improve the service: crash reports, the feedback you give, and counts of how features are used.
  • To contact you about your account: sign-in and password emails, and replies to support tickets.

We do not sell your data, rent it, or use it to train AI models.

Commander and AI

When you ask Commander a question, your question and the site information needed to answer it (for example which of your sites are down, or what a notice means) are sent to an AI model through our hosting provider's AI service. Commander can be turned off for an account or for one person in Settings.

The AI clients you connect yourself (such as Claude or Cursor) are run by their own providers under their own terms. Sitecommand passes them only what they request for the sites and permissions you approved.

Who else handles your data

We use a small number of providers to run Sitecommand. They process data on our behalf, and the full list with what each one receives is in the data policy. The main ones are our hosting provider (Vercel) and our database and sign-in provider (Supabase).

Alerts go to the channels you add (Slack, Discord, Telegram or your own webhook). Once delivered, that message is handled under that service's terms.

We may disclose information if the law requires it, or to protect the service and its users from fraud or abuse.

How long we keep it

We keep your account data for as long as your account exists. Monitoring history is trimmed on a schedule (the periods are listed in the data policy). When you delete your account, your account, sites, settings and history are removed from the live database straight away.

Your choices and rights

  • See and change your details in Dashboard → Settings.
  • Download a copy of your account data from Settings → Export.
  • Delete your account from Settings. This removes your data and disconnects every AI client.
  • Disconnect a site at any time from the dashboard or from the plugin's settings page.
  • Ask us for access, correction or deletion, or object to how we use your data, by writing to privacy@sitecomand.xyz. We answer within 30 days.

Depending on where you live (for example the EU, the UK or California), the law may give you additional rights, including the right to complain to your data protection authority.

Security

Site secrets are encrypted at rest, sign-in tokens are stored as hashes, every request to a site is signed and time-limited, and staff access to account details is limited and logged. More detail is on the security page. No system is perfectly secure; if we learn of a breach that affects your data we will tell you without undue delay.

Where data is processed

We are based in Bangladesh and our providers run in other countries, so your data is processed outside the country you live in. By using Sitecommand you understand that this happens.

Children

Sitecommand is a tool for people who manage websites. It is not intended for anyone under 18, and we do not knowingly collect data from children.

Changes to this policy

If we change this policy we will update the date at the top. For changes that affect how your data is used, we will tell account owners in the dashboard before the change takes effect.

Privacy policy · Sitecommand