A private group on infrastructure you choose
GComm does not require a corporate chat account. Your Desktop client connects to the GComm server selected by your administrator. That server may run on your own Windows computer, your organization’s network, or infrastructure you rent.
The app includes no advertising or behavioral analytics. In a self-hosted deployment, conversations are not routed through a PESystems messaging cloud or collected there for advertising profiles. Your chosen hosting and network providers still operate the infrastructure you use.
How access and content are protected
| Layer | Purpose |
|---|---|
| TLS + certificate pinning | Protects the client/server connection and checks the intended server identity. Invitations include the server fingerprint; clients retain their server trust information. |
| Shared passphrase proof | The client proves knowledge of the shared phrase without sending the phrase itself in its network handshake. The copyable email may explicitly include it for the recipient. |
| Device enrollment | A single-use invitation enrolls a device. Later connections prove possession of that device credential. Administrators can release registrations. |
| Channel authorization | The server controls which devices can see and contact one another. Shared-channel authorization applies to relay and direct paths. |
| Authenticated content encryption | Messages and file contents are protected using AES-GCM with independent random 256-bit channel keys. A channel key is separate from the shared admission passphrase. |
| Membership changes | Changing device memberships or releasing a device rotates affected keys and refreshes authenticated permissions. |
Who you still need to trust
Recipients can save files, export chat, take screenshots, or share content elsewhere. Removing a membership or releasing a device cannot recall content already delivered. A person belonging to multiple channels can intentionally send content across those groups.
Routing metadata remains visible to the server, including device identity, display name, presence, addresses, channel membership, and message routing information. Encryption of content does not make the group anonymous. GComm does not claim forward secrecy.
Protect the Windows machines, shared passphrase, invitation emails, server data, and backups. Self-hosting gives you control over those choices and responsibility for operating them.
What is stored and where
| Location | Information and control |
|---|---|
| GComm server | Configuration, server identity/certificate, device registrations, invitations, channels, keys, and license/capacity data. The operator controls the host and its logs. |
| Message routing | The server relays messages and transfers without a persistent conversation archive or offline delivery queue. Recipients need to be online. |
| Windows Desktop | Settings, device credentials, server trust information, and saved transcript/history. Local file copies and saved exports remain on the computer and must be managed separately. |
| Invitation email | The rendered default email includes the one-use invitation and shared passphrase. Those copies are handled by the administrator’s and recipient’s email systems. |
| Reusable email instructions | Saved per Windows user and server identity, with live invitation credentials normalized to placeholders. The copied email itself still contains current credentials. |
Use Clear screen to clear Desktop’s transcript and saved restart history. Manage chat exports and physical files separately. Removing access is a server authorization change; it is not remote deletion.
Network activity beyond the chat connection
A self-hosted chat connection does not mean the software can never contact another service:
- Updates: the Windows update feature retrieves PESystems release information and installers over HTTPS. These requests are separate from message content.
- Licensing: capacity requests, imports, or purchase workflows can involve PESystems licensing services. License/server identifiers and capacity information are distinct from chat content. Additional-seat sales availability is separate from the three included seats.
- Direct connections: clients can use peers and administrator-configured STUN/TURN infrastructure. Those providers can observe connection metadata relevant to their role.
- Email and hosting: invitation mail travels through the email service the administrator uses; rented server or VPN infrastructure follows its operator’s practices.