Transparency & data
What the service can - and can't - see.
A privacy product should be willing to say exactly how it handles data. Here's the straight version: what stays unreadable to Minyma, what a relay still has to process, and how long anything is kept.
We'd rather earn trust by being specific than by making sweeping claims. Where something is a limit, we name it. Where something is still being built, we say so.
What Minyma can't read
Your content is designed to stay yours.
What a relay still processes
The operational middle.
To deliver a message to someone who might be offline, or to ring a phone for a call, a service has to handle some operational metadata. Minyma minimizes this and uses sealed-sender delivery to reduce it further - and we're straight that it isn't zero.
- Account identifiers and device records needed to route and deliver messages.
- Connection and delivery signals - the operational data that lets messages and calls actually arrive.
- Push-notification tokens, so your device can be woken for new messages and calls.
- Encrypted attachment blobs, held briefly so offline recipients and linked devices can fetch them.
Retention
Keep what you need. We archive nothing.
Minyma's posture on storage is simple, and it follows from the premise: the service is a courier, not an archive.
Attachments
Short retention, then gone
Encrypted attachment blobs exist on the service only long enough to be delivered to offline recipients and linked devices, then they're deleted. Save anything you want to keep to your own device - what you don't save isn't kept for you. The infrastructure that holds them is based in the European Union (GDPR).
Your account
Delete on your terms
You can delete your account, which removes relay-held account data. Naturally, that can't reach back to content other people already received and saved on their own devices.
What we don't do
Some lines we hold.
- No ads. Minyma is not funded by monetizing your attention.
- No behavioral tracking. We don't build advertising profiles of how you use the app.
- No content archival. The service is built to relay your messages, not to keep a copy for itself.
- No plaintext on the server. Message and attachment contents reach the service only as ciphertext.
Our commitments on clarity