Stealth Commander
Privacy
Stealth Commander is provided by nexusmap.ai. This page explains the data used by the Windows client, account service and chat connection.
Last updated October 29, 2026
Account and paired PC data
The website uses an essential sc_session sign-in cookie with a maximum age of 12 hours. It is restricted to secure connections and is not readable by page scripts. The account service stores your email address, display name if supplied, a salted password hash, account credentials and creation time. Pairing adds device identifiers, PC hostname, Windows username, operating system, connection addresses and device credential records. These records let the service sign you in, select your PC and reject access to other accounts.
Commands, results and images
The gateway passes requested tool arguments to your paired PC and returns its results to your chat client. Results can include file contents, command output, window information and images. The normal proxy does not save these payloads in the account database. Your chat provider receives the content returned to it and applies its own privacy and retention settings. Avoid returning data you do not want included in a conversation.
Data on your PC
The Windows client keeps pairing credentials and settings locally. Local usage history keeps the most recent 40 events, including a short operation summary. Hidden sessions, logs and captured image files can remain in their local work folders after a task. A short-lived image export cache does not erase those files. Review and remove local work folders when you no longer need them.
Service providers
Cloudflare runs the website, gateway and account storage, and may carry remote connections through a tunnel. OpenAI receives tool content when you use the plugin in ChatGPT or Codex. Client downloads use GitHub; installation can download dependencies from PyPI or npm. Those providers handle requests under their own policies. The Stealth Commander website does not include an advertising or analytics tracker.
Retention
Account and paired-device records stay in the service while the account exists. Sign-in sessions and temporary authorization records expire. Operational logs and backups maintained by hosting providers can have separate retention periods; this page does not promise immediate erasure from those systems. Files and history on your PC remain under your control.
Your controls
Use the account dashboard to unlink a PC or rotate its account key. Disconnect the plugin in your chat client to end that connection. Account settings also provide Delete account, which removes the service account and paired-PC records and revokes access. A temporary hashed identifier prevents older requests from restoring a deleted account. It expires after 15 minutes and is removed during routine storage cleanup. Deleting the cloud account does not uninstall the Windows client, erase your chat history or remove local projects, logs and screenshots. Manage those copies separately.
Self-service help
Setup and troubleshooting are available on the Support page. There is no staffed support inbox. Use the account controls above to manage your access and cloud account data.