Home

How AliasX handles data

Updated 5 November 2026

AliasX is an incoming email alias service. This page describes the data of a standalone AliasX account and of connecting existing mail. The browser extension has a separate description of its permissions and how it works with sites.

Extension privacyExtension permissions and how it works with sites

Account and addresses

For a standalone account you choose a username and a password. The AliasX username is used to sign in and does not create a mailbox by itself. Emails are received by separately created aliases.

The service stores information about the account and its sessions, data for checking sign-in, alias addresses, their labels and status, and protected copies of keys. The labels you give aliases are sent to the server: for example, a site name can reveal where you use an address.

Receiving and encrypting email

Regular internet mail arrives over SMTP. The receiving server processes the content of an incoming email before encryption. So a regular email from an outside site does not become an end-to-end encrypted message just because an alias is used.

The standalone account archive and short records for the message list are stored encrypted. The archive's private key is opened on your device. The server keeps protected copies of it, not the open private key. Service data — recipient address, time received, size and delivery status — is necessary for the service to work.

When you read an email, the browser decrypts it. The email's HTML is handled by a protected viewer; the sender's code does not run and external images do not load automatically. If you copy text or a confirmation code into another app, that app decides how it is handled from then on.

Device access and recovery

The recovery file contains secret data for restoring access. It is saved on your device before protected keys are sent to the server. Keep it apart from publicly accessible files.

The browser keeps protected connection data so that reopening the dashboard does not require a full sign-in every time. Signing out ends access for that session. Clearing browser data does not by itself delete the account or the server archive.

Connecting existing mail

When you connect a mail service, the password is entered on that service's account page. AliasX receives a separate permission to work with the selected aliases and the aliases created through that connection. Access to the main mailbox and its private key is not shared.

Connected mail history differs from the standalone AliasX archive: new emails after the permission is granted are available, within the last seven days. This is a limit on access through the connection, not a promise that all copies of an email are deleted after seven days. The main archive stays with the connected mail service.

Storage and switching off

Switching an alias off stops it from receiving new emails. Messages already received stay in the archive. Signing out and revoking a connection also do not delete emails.

The available archive size and number of aliases are limited by service settings. Limiting what is shown, deleting data from the browser and deleting server data are different actions. This page does not promise automatic deletion of the archive or backups after a set number of days.

Running and protecting the service

Web requests pass through Cloudflare and the server infrastructure. When a connection is established, these systems process the IP address and technical request details. They are used to deliver the site, limit abuse and diagnose problems. Encrypting the archive does not mean there are no service data or network logs.

If you connect another mail service, its handling of your account and mail is governed by its own rules. AliasX gets no extra rights just because two accounts have the same name.