How MirsalGo works

Private content.
Clear paths.

A message or file starts on a device, travels as protected data and becomes readable again only on an authorised recipient device.

From a readable file
to an opaque envelope.

The service has a job to do: authenticate, route, store and deliver. The content boundary is visible at every step.

01
↗

Created on a device

The sender writes a message or chooses an attachment. The supported encrypted messaging path protects the content before upload.

Readable content
02
▤

Carried by the service

The server receives an encrypted envelope, checks access and routing, then stores or forwards it for delivery.

Opaque encrypted data
03
↙

Opened by the recipient

The authorised recipient device uses its local keys to open the content and show it in the conversation.

Readable content

A service boundary
you can explain.

Use this model when you are deciding where the service belongs in your organisation and incident process.

SenderWindows · Android · iPhoneContent is prepared on the device
encrypted envelope
MirsalGo serviceAuthenticate · route · retainMetadata needed to operate remains visible
encrypted envelope
RecipientAuthorised deviceLocal keys open the content
The boundary to remember

The server can see who needs delivery, when data moves and how large it is. It is not given the content keys for supported encrypted messages and attachments. Compromised endpoints and independently saved copies are separate risks.

Attachments follow
the same idea.

Sending a PDF, photo or voice note does not turn it into a server-readable file.

Prepare

The app reads the selected file locally and prepares encrypted content for the message.

Upload in pieces

The service accepts ciphertext with limits, resumption and ownership checks. It does not need the original filename contents to route the upload.

Deliver and open

The recipient downloads the encrypted object and the app opens it using device-held keys.

What remains visible: attachment size, delivery timing, participants and operational records. Encryption protects content, not all metadata.