MirsalGo Trust Center

Security explained
without shortcuts.

See the protections, service boundaries and operational choices behind MirsalGo. Read the limits alongside the claims.

Current public product descriptionLast reviewed 18 November 2026
01

A New key for each message

In end-to-end encrypted direct and group chats on Windows and Android, the sender encrypts each new message with a fresh, random AES-256-GCM content key. A Signal Protocol session wraps that same key separately for each authorised recipient device. The service never receives the unwrapped key.

Exposure of one content key alone does not unlock other messages.

See the message path
02

Transport protection

HTTPS protects the API and console, SIP over TLS protects signalling, and WSS carries events. Supported server-mode voice calls use encrypted media on qualified paths.

Read the privacy boundary
03

Managed access

MirsalGo Studio gives authorised administrators a place to manage accounts, permissions, devices, retention and administrative activity.

Explore Studio

What the service can see.

Trust grows when the boundary is specific. These are the categories needed to operate the service.

Visible for delivery and administration

  • Account and device records
  • Group membership and routing
  • Timing, delivery state and data sizes
  • Security and operational logs

Protected content boundary

  • Supported message content
  • Supported attachment content
  • Voice-note content in the encrypted messaging path
  • Call media on supported encrypted server-mode paths

Protection has limits.

Use MirsalGo with the same care you apply to every endpoint and administrator account.

Devices matter

An unlocked, modified or compromised device can expose content after it is decrypted. Use device locking and your organisation’s device policy.

Copies matter

A recipient can save, export, photograph or forward content. Remote deletion cannot erase independent copies.

History has a boundary

Content saved before an encryption policy was enforced does not become encrypted retroactively. Retention and backups have their own lifecycle.

Security questions or reports

Tell MirsalGo about a security concern through support@mirsalgo.com. Do not include passwords, private keys or confidential message contents.