Privacy

Your conversations. Your control.

Minyma is designed so message and attachment contents are encrypted on sender devices and decrypted on recipient devices. The relay still handles delivery duties, and Minyma is honest about that.

Get Minyma Read Privacy Policy

At a glance

Minyma's privacy position

Message and attachment content are designed to stay end-to-end encrypted
Private keys stay on user devices rather than on the relay
The relay still observes some operational metadata
Minyma protects message content end to end and continues reducing relay-visible metadata
Minyma IDs avoid a public phone-number directory as the core account model
Account deletion removes relay-held account data, not other users' local copies
Local reset and duress features are strongest on the current device
Trust review and linked-device controls stay visible to users

Protected

What Minyma is built to protect

Message text
Attachment contents
Attachment keys shared inside encrypted messages
Receipts, edits, and deletes carried in encrypted flows

Metadata

What still exists operationally

Which user or device is sending
Which user or device is receiving
Timing and frequency of messages
Encrypted attachment size and limited transfer metadata, such as upload/download timing and delivery state

Deletion

What Delete Account does

Delete Account is intended to remove relay-held devices, queued delivery data, profile information, push tokens, and uploaded ciphertext attachments.

It wipes the current device back to onboarding
It does not erase content already downloaded to other devices

Local

Reset and duress behavior

Local reset wipes the current device. Duress mode can wipe locally and, when enabled, first tries to delete the relay account before that wipe.

These tools are strongest on the current device
They do not remove content from other users' devices