Vanquish Command App Privacy Policy
Last updated: November 15, 2026
About this policy
This policy covers the Vanquish Command app for Android (package org.vanquishnet.command), published by Vanquishnet Communications L.L.C. The app is for technicians who already have a Vanquish Command account. It opens the Vanquish Command phone console at https://command.vanquishnet.com/app/ inside Chrome as a Trusted Web Activity, so it uses the same sign-in and the same server as the Command web console.
Data about the computers your organization manages with Vanquish Command (devices, alerts, tickets) is handled under your organization’s agreement with us. Our main Privacy Policy covers this website.
Android permissions
The app uses notifications and network access. It requests notifications (POST_NOTIFICATIONS) so it can show alert notifications if you turn them on, and it uses network access to reach the Command server. Android app backup is turned off for the app.
The app does not include advertising or analytics SDKs. It does not access your contacts, camera, microphone, or location.
Signing in
- You sign in with your Command email and password, and a two-factor code when your account requires one. Sign-in uses the same endpoints and the same HttpOnly session cookie as the Command web console.
- The app remembers the email address you last signed in with on your phone, so you don’t have to type it again.
- Fingerprint sign-in (passkeys). If you add a passkey, your phone’s screen lock or fingerprint check happens on the phone; your fingerprint is never sent to us. The Command server stores the passkey’s public key, credential ID, signature counter, your account’s organization and user IDs, WebAuthn flags, AAGUID, and transports. It also stores a device name (your phone’s model name, or “Android phone” or “Phone” when the model is not available), when the passkey was created and last used, and the IP addresses it was created and last used from. The app keeps the credential ID on the phone so it knows this phone has one. When email is set up for the instance, adding or removing a passkey sends the account an email with the device name, the time, and the IP address. You can remove a passkey in the app under Settings, which asks for your password and a code, or an administrator can remove it. Those IP addresses have no automatic limit. They are deleted when the passkey is removed or the account is deleted.
Notifications
If you turn on notifications, your phone’s browser creates a push subscription and the app sends it to the Command server. The server stores the subscription endpoint and its keys, your account’s organization and user IDs, when the subscription was created and last refreshed, your browser’s user agent, and your notification settings (muted categories, quiet hours, and time zone). It also keeps an outbox of sent notifications, each with a status. Notifications are delivered through the push service of the browser that runs the app. A notification payload includes an alert type, a severity, a count, an item ID, and a reason code. For an outdated-agent alert it also includes the agent version. It does not include a computer name. The app loads the details from the Command server after you open it.
Turning notifications off asks the server to delete the subscription. Signing out deletes the subscription only if the app’s delete call succeeds; otherwise it stays. Push subscriptions and the sent-notification outbox have no automatic limit.
Data stored on your phone
- The email address you last signed in with. It stays on the phone when you sign out.
- A copy of the last Home screen the app loaded, so it opens quickly. It is removed when you sign out.
- Your recent searches in the app (up to 6) and your alert-grouping choice. These stay on the phone when you sign out.
- Whether this phone has a passkey for Command, and that passkey’s credential ID. These passkey flags stay on the phone when you sign out.
- The app’s own files (the app shell and icons) so it can open without a network connection. Signing out clears that shell and icon cache. Server responses under
/api/are never cached on the phone.
Diagnostics
When something goes wrong in the app, it sends a short diagnostic report to the Command server: the app version, an error type, an error message of up to 300 characters, and a short list of recent steps in the app (screens opened, actions such as “login” or “open remote”, and the request type and path of recent changes, with record IDs removed). The report is written to the server log with your Command user ID. Diagnostics are kept in rotating server logs; older entries are overwritten as the logs fill, with no fixed time limit.
Using Command from the app
The app shows the same Command data your account can see in the web console, such as computers, alerts, and tickets, and lets you act on it within your account’s permissions.
Ticket Copilot and the AI technician run through the Grok CLI on the Command server. Prompts go to xAI (Grok). Copilot sends the ticket subject and up to 30 messages, the computer hostname and operating system, a device snapshot (processes, disks, network, error logs, and matching apps), up to 5 prior AI session summaries, and tool output, including shell output and event logs. It does not send screenshots. The app starts Copilot in approval mode. In that mode, read-only tools run without asking, and an organization auto-approve rule can let change tools run.
Sessions, sign-in records, and remote access
- Session records store the IP address and the user agent.
- Sign-in and security events store the IP address, a name or email, and the country when the request includes one. These events are kept for 365 days.
- Audit events have no automatic limit.
- Opening a Remote Desktop or Shell session can email the customer the technician’s name, email, and source IP. Shell session text is recorded on the server.
- Remote Desktop uses a Google STUN server.
Sharing
We do not sell information from the app, and we do not share it for cross-context behavioral advertising.
Deleting your data
The app has no way to delete your account. Signing out clears the cached Home screen and the app shell and icon cache on the phone. It deletes the notification subscription only if the app’s delete call succeeds; otherwise the subscription stays. To request deletion, ask your organization’s Command administrator or email armin@vanquish.work. Deletion is on request. Security and audit logs are kept as described above.
