ServerGO Privacy Policy

Overview

ServerGO is an independent server management and AI operations client. You may use local features, configure a model API, or sign in to the official account service. These features have different data destinations. Signing in does not mean local servers, credentials or conversations have been uploaded.

Local data

Sign-in, sign-out and account restoration preserve existing local data. Signing out does not automatically delete connections, models or conversations, or restore revoked operation permissions.

Deleting a conversation does not automatically delete independent task audits or cancel an operation already submitted to a remote server. Device backups, exported files and data on remote servers have separate storage scopes.

Connections to your servers

The client communicates with targets through configured SSH, SFTP, PVE API, WebSocket or remote desktop connections. Authentication information such as usernames, passwords, tokens or key proofs is provided to the relevant target. Permission to authenticate is not permission to send these credentials to an AI model.

Monitoring, log and file reads, and operations you confirm, process data returned by the target. Initial host fingerprints and certificates need to be checked against that target; a connection failure is not a reason to automatically trust a new identity. Your proxies, VPNs, jump hosts and remote services can also affect the network path.

AI model requests

AI features require a provider, API address, model and credentials that you configure. Requests are sent from the client to your selected API endpoint. The current Alpha does not relay these conversations through the official account backend.

Requests may include:

• Messages you enter and conversation history needed for the current turn;
• Names, identifiers and scope information for associated resources;
• Monitoring data, logs, file contents or command results read within the current resource scope and tool permissions;
• Log excerpts or selected text you deliberately provide and confirm.

Associating a resource does not mean its data has been read. Ordinary questions can be sent directly; new log or file content follows the previews, confirmations and tool permissions provided by the app. SSH passwords, private keys, sudo input and model keys should not be sent as conversation text. Redaction cannot replace checking content you paste yourself.

API credentials are used to authenticate to the model endpoint. Providers may process or retain requests under their own terms; check the actual domain and provider privacy policy. Changing or deleting a local profile does not remove data already received by a provider or recall a request already sent.

Official accounts and devices

If you register or sign in, the identity service in the system browser processes your login identifier (a username or email-form identifier), unique account identifier and password. There is currently one login-identifier field, with no separate contact email, email ownership verification or email recovery. The service is designed to store password hashes and salts rather than plaintext passwords. The client stores authorization tokens to maintain or restore a session.

Account and device services process account identifiers, device registration identifiers, public keys, device names, platforms and recent presence information for sign-in, device lists, signature verification and access revocation. These functional device identifiers are different from advertising tracking identifiers.

Providing network services requires processing request addresses, times, outcomes and necessary security diagnostics. Do not submit complete server configurations, logs, tokens or passwords to public feedback channels.

Signing out, revoking a device, deleting an account and clearing local data are separate operations. Account deletion may require fresh authentication and revoke access before subsequent cleanup finishes. An unconfirmed outcome is not presented as completed. Backups and necessary security records may not be removed at the same instant; contact support to clarify the applicable scope.

The service retains revocation records, including disabled account identifiers, to prevent old tokens from recreating an account. Revoked devices, public keys, ended sessions and deletion queues may also retain technical state. A uniform final cleanup period for these records, production backups and infrastructure logs has not been established. Short authentication-token lifetimes are not retention periods for all user data; applicable retention and recovery rules still need to be implemented and published before public distribution.

Cloud synchronization and remote communication

The current Alpha does not promise that full cross-device encrypted synchronization or ServerGO's own cross-device desktop control is available. A capability can be used only when actually enabled and accurately described in the interface. Account sign-in does not imply local data import. Existing RDP or PVE consoles do not imply that an official remote control relay is enabled.

Signing in does not automatically upload local data. Before introducing additional cloud storage or relay capabilities, the product must explain the data scope, processing and retention rules and provide the relevant choices. This policy does not substitute for a new permission confirmation.

Notifications, diagnostics and tracking

The app may request system notification permission for configured local alerts and task updates. iOS background work is limited by the operating system; notification permission does not imply continuous cloud monitoring or an available remote push service. This Alpha does not list unfinished Android, FCM, Widget or Siri features as active services.

The current Alpha does not provide advertising or advertising-identifier tracking features. Troubleshooting may involve local logs and system-generated crash diagnostics. Before sharing feedback, remove addresses, accounts, business content and credentials. Do not submit complete terminal scrollback or unredacted logs.

Your choices and cleanup

• You can use available local features without signing in.
• You can manage connections, models, credentials and conversations using the controls provided, cancel future requests or revoke operation permissions.
• You can turn off notifications and manage application permissions in system settings.
• Account deletion, local cleanup, remote server deletion and handling data held by model providers are separate actions.
• Uninstalling the app does not delete an account, recall model requests or erase remote data. Device backups, exports and separate credential stores also need to be checked separately.

The product does not provide a service specifically for children. For data scopes not manageable in the interface or other privacy questions, contact support without including sensitive raw data.

Contact and updates

Support and privacy contact: hi@xicoai.com. Provide versions, redacted reproduction steps and only necessary screenshots. Do not send passwords, tokens, private keys or complete business logs. The project repository is private, so its Issues page is not a public support channel.

Material changes to data processing will be reflected in updated descriptions. Read this policy together with the capabilities of your installed version and the policies of your selected third-party services.

ServerGO is not affiliated with Proxmox Server Solutions GmbH and is not its official client. Third-party names and trademarks belong to their respective owners.