Skip to content

How it works

No accounts, no passwords, no trust required

AliasCloak is built so that we cannot read your messages even if we wanted to. Here is exactly how that works, in plain terms, followed by the technical detail if you want it.

How it works

A little less sign-up.
A lot more conversation.

There is nothing to configure. The cryptography happens automatically; you just decide who you are talking to and what you want to share.
1

Create a mailbox

Your browser generates a key pair and keeps the private half. We store only the public key and give you a readable alias like quiet_forest_owl. No email, no password, no confirmation step.

2

Share your alias or invite link

Anyone can write to you with just that alias — they do not need an account. Send an invite link instead and it opens straight into a chat with you.

3

Start a conversation

Write a message, start a chat, or send a file. Your browser encrypts the content before upload. Mail bodies are removed after all recipients confirm delivery; chat and attachments expire on their own schedules.

The detail

What actually happens when you click "Create mailbox"

Your browser generates an X25519 key pair using libsodium. The private key is written to local storage on your device and never transmitted. The public key is sent to us, stored, and paired with a randomly generated three-word alias. That is the entire signup process — there is no record connecting the mailbox to you, because no such information was ever collected.

What happens when someone sends you a message

Their browser looks up your public key by alias, generates a fresh symmetric key, encrypts the message body and any files with it, then encrypts that symmetric key to your public key. We receive ciphertext and an encrypted key we cannot open. When you next open AliasCloak, your browser downloads both and decrypts them locally.

What happens to the copy on our server

For one-shot mail, a recipient delivery record is acknowledged only after local decryption succeeds. Unacknowledged ciphertext stays on primary storage for seven days by default. If the operator’s optional cold archive is available at that cutoff, unread encrypted payloads can remain retrievable there for up to 30 additional days; if it is unavailable, the seven-day deletion policy wins. Fully acknowledged mail is not promoted just to extend retention. AliasCloak keeps no server-side plaintext archive; portable backups are created and passphrase-encrypted locally in your browser.

What we can see

That a mailbox with a given public key exists, that ciphertext of a certain size was addressed to it, and roughly when. We do not see who sent it beyond their mailbox key, what it says, what the files are called, or who you are. We do not run analytics or advertising trackers.

What happens if you lose your private key

The mailbox becomes unreadable, permanently, including to us. This is the cost of the guarantee: any mechanism that let us restore your access would also let us — or anyone who compelled us — read your messages. Export a passphrase-encrypted backup and store the backup file and passphrase separately. If you enable TOTP two-factor authentication, the authenticator secret is deliberately not included in the backup.


Want the cryptographic specifics — algorithms, key sizes, threat model, and what we explicitly do not protect against?

Read the security model

Private by design

Start private. Stay in control.

Create a free AliasCloak mailbox in seconds, then use the same private identity for encrypted mail, chat, and file delivery.