Created on a device
The sender writes a message or chooses an attachment. The supported encrypted messaging path protects the content before upload.
Readable contentHow MirsalGo works
A message or file starts on a device, travels as protected data and becomes readable again only on an authorised recipient device.
The service has a job to do: authenticate, route, store and deliver. The content boundary is visible at every step.
The sender writes a message or chooses an attachment. The supported encrypted messaging path protects the content before upload.
Readable contentThe server receives an encrypted envelope, checks access and routing, then stores or forwards it for delivery.
Opaque encrypted dataThe authorised recipient device uses its local keys to open the content and show it in the conversation.
Readable contentUse this model when you are deciding where the service belongs in your organisation and incident process.
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.
Sending a PDF, photo or voice note does not turn it into a server-readable file.
The app reads the selected file locally and prepares encrypted content for the message.
The service accepts ciphertext with limits, resumption and ownership checks. It does not need the original filename contents to route the upload.
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.