Skip to content

Privacy policy

Last updated September 7, 2026

The short version

We do not ask who you are, and the system is built so that we cannot find out. There is no account, no email address, no phone number and no password. We store public keys, aliases, and encrypted data we have no way to read.

What we collect

Public keys and aliases. When you create a mailbox, your browser generates a key pair and sends us the public half. We store it alongside a randomly generated alias. Neither identifies you.

Encrypted message content. Messages and files sit on our servers as ciphertext until they are collected. We hold no key that opens them.

Optional two-factor data. If you set up an authenticator app, we store the shared TOTP secret required to verify current codes. A successful verification can also create a random trusted-device token on your browser; only its hash, mailbox association, timestamps and a hashed user-agent identifier are stored server-side, and it expires.

Contact form submissions. If you write to us, we keep the email address and message you provide so we can reply.

Payment records, if you buy a custom alias. Card details are handled by Stripe and never reach our servers; we store the payment identifier, amount, entitlement state, lease dates, and limited refund/dispute identifiers and status needed to prevent a reversed purchase from keeping a paid alias.

Mailbox routing controls. To enforce receive-mail, receive-direct-chat and blocking choices, we store those mailbox-level flags and the public-key-to-public-key block relationships needed to route or suppress delivery. Quiet hours, notification preferences and per-conversation mute schedules stay on your device.

Optional closed-app notifications. If you enable browser/device notifications and AliasCloak Web Push is enabled, we store the browser push endpoint and its public subscription keys for the mailbox and notification channel you enabled. Push messages contain no AliasCloak payload at all: no sender, alias, subject, message text, conversation identifier, unread count, encryption key, timezone or quiet-hours schedule. Separate subscriptions are used per mailbox and per mail/chat channel, and dead subscriptions are deleted when the browser push service reports that they expired.

Sign in with AliasCloak. If you choose to use your mailbox to sign in to an approved third-party site, we process short-lived OpenID Connect authorization/session records and issue that site a pairwise pseudonymous identifier. Unrelated sites receive different identifiers. A site receives your AliasCloak alias only if it requests the optional alias scope and you explicitly approve sharing it.

What we do not collect

No names, email addresses or phone numbers for mailboxes. No advertising or analytics identifiers. No third-party trackers. No behavioural profiling. We do not store raw IP addresses — where an identifier is needed to limit abuse, a keyed one-way hash is used and discarded on a short cycle. Closed-app push subscriptions never contain your private keys, message contents or unread count. Sign in with AliasCloak does not give third-party applications access to mailbox private keys, messages, chats, files or contacts.

How long we keep things

For one-shot mail, each intended recipient has an independent encrypted delivery record. The encrypted text body is removed after every intended recipient has acknowledged successful local decryption. By default, unacknowledged one-shot ciphertext remains on primary storage for seven days. If optional cold storage is available at that cutoff, unread encrypted payloads may remain retrievable for up to 30 additional days; otherwise they are deleted at the seven-day cutoff. Cold-storage bytes remain encrypted and still count against the sender’s quota. Encrypted chat history is kept for a limited window so devices that have been offline can catch up, then deleted. Public keys and aliases persist until you delete the mailbox. Contact messages are kept until they have been dealt with.

What is stored on your device

Your private keys, your decrypted message history, chat transcripts, mailbox display/avatar preferences, notification preferences, quiet hours and conversation mutes are stored in your browser using IndexedDB. Private keys and decrypted content never leave your device. Clearing your browser data deletes them permanently — including the private keys, which we cannot replace. Use the backup export before you clear anything. New backups are encrypted locally with a passphrase using AES-256-GCM and PBKDF2-SHA-256 before the file is written; the backup passphrase and TOTP authenticator secret are not sent to or included by AliasCloak.

Cookies

We do not use tracking cookies and we do not run advertising. The app stores your preferences and your keys in local browser storage, which is not shared with anyone and is not sent to our servers. Stripe may set cookies on the payment form if you choose to buy a custom alias.

Who we share data with

Nobody, other than the infrastructure required to run the service, the browser/operating-system push service when you explicitly enable closed-app notifications, and Stripe for payments if you choose to make one. A push service receives the opaque browser push endpoint/protocol traffic needed to wake that installation; AliasCloak sends an empty push payload and the service worker supplies the fixed generic notification text locally. We do not sell data. We could not sell encrypted message contents even if we wanted to, because we cannot read them.

Legal requests

If we receive a valid legal demand we will comply with it to the extent we are able. Depending on what still exists, we may be able to produce the existence of a mailbox with a given public key and alias, creation and lease/payment metadata, mailbox routing-control flags or block relationships, active browser push subscription endpoints/public subscription keys if closed-app notifications were enabled, and ciphertext still within its retention window. We cannot produce decrypted message contents, local notification/quiet-hour settings, unread counts or the real-world identity of a mailbox owner, because we do not have them.

Your rights

You can delete a mailbox at any time from Settings, which destroys the record and every message waiting for it. Because we hold no personal data linked to you, there is generally nothing further to export or erase — but if you have contacted us and want that correspondence deleted, ask and we will remove it.

Children

AliasCloak is not directed at children under 13, and we do not knowingly collect information from them.

Changes

If this policy changes in a way that materially affects what we collect or how long we keep it, the date at the top will change and the change will be noted here. Because we collect so little, substantive changes should be rare.


Questions about any of this? Get in touch. For the technical detail behind these claims, see the security model.