Your data stays
unreadable on the server.
Content is encrypted on your device before upload. The server, and therefore the admin, cannot read it.
The best protection for your data is when only you can decrypt it
On the scopes you choose, your content is encrypted with keys that only your devices hold. Neither an admin, nor an attacker, nor even us can read what you do.
- encrypted before upload
- Device
- protected by your secret phrase
- Vault
- admin reads of encrypted content
- 0
- mail, drive, docs, chat, calendar, contacts
- 6 apps
Where to enable encryption
One key per resource. Enable folder by folder.
| Application | Enabled by... | What is encrypted... |
|---|---|---|
| Ultimail | Account or folder | Subject, body, attachments |
| UltiDrive | File or tree | File contents |
| UltiDocs / UltiCells | Drive-linked document | Text and cells |
| UltiChat | Channel | End-to-end messages |
| UltiCal | Calendar | Event titles and details |
| Contacts | Sensitive records | Record contents |
Lost your secret phrase? See the FAQ
Your vault, your passphrase
A key pair is created on your device. The private key stays protected by your passphrase. One vault serves the whole suite.
Vault on your device
Your private key is passphrase-protected and unlocked for the duration of your session.
Only the public key goes to the server
The server stores only what it needs to lock each resource, never your private key.
Rotation and revocation
A compromised key: revoke it and register a new one.
Multi-device
Export or import your vault, or create one key per device.
The server can neither read nor search
On locked perimeters, the database only keeps ciphertext. Search and AI reach it only after decryption in your session.
Opaque storage
The database and file storage only contain unreadable blocks.
Read on your device
You only see content after unlocking your vault in the interface.
AI after decryption
Decrypted in the browser before analysis. On-premise model: text stays on your infra.
Webhooks without leaks
External integrations receive notifications without plaintext bodies of locked resources.
Keys exchanged on your device, content unreadable to the server
Each message, file or cell is encrypted on your device before storage. The server only sees unreadable data.
Military-grade encryption
AES-256-GCM for content, X25519 (or Ed25519) for key exchange.
Same server and client logic
Key locking is identical between the backend and your browser.
Progressive activation
Enable account, folder, file, calendar, or channel, no all-or-nothing.
Enable Zero Trust across the entire suite
Create your vault and protect your sensitive data.