Skip to content

Documentation

HashTag is a cryptography toolbox that runs entirely in your browser. This guide explains the key concepts and how to use each tool.

Getting started

  1. Go to Keys and generate an OpenPGP “Ed25519 + X25519” key pair protected by a passphrase.
  2. Download your private key and keep it somewhere safe (password manager, encrypted USB drive).
  3. Sign in with Discord (optional) and publish your public key to appear in the directory.
  4. To write to someone, open their profile and click “Encrypt for…”. Only the recipient will be able to read the message.

Public key, private key

A key pair works like a padlock and its key. The public key (the padlock) can be shared freely: anyone can use it to encrypt a message for you. The private key (the key to the padlock) stays secret: only it can decrypt and sign.

Not every key does the same job: Ed25519 and ECDSA are for signing, X25519 is for establishing a shared secret (encryption), and RSA can do both. A modern OpenPGP key combines an Ed25519 signing key and an X25519 encryption subkey.

Encrypting a message

With a password

The password is turned into a key with Argon2id (64 MiB of memory, 3 passes) or PBKDF2-SHA256 (600,000 iterations), then the content is encrypted with AES-256-GCM. Send the password over a different channel from the message.

For recipients

HashTag generates a random session key, encrypts the content once, then protects that session key for each recipient with their OpenPGP public key. Everyone decrypts with their own private key.

With an SSH or age key

You can also encrypt for an ssh-ed25519 or ssh-rsa key, or an age identity (age1…, or age1pq1… for the post-quantum ML-KEM-768 + X25519 version). The result is a standard age file, which the recipient can also open with the age command-line tool. An SSH Ed25519 key is a signing key: age converts it explicitly, in a documented way, into an X25519 key.

Share link

An encrypted message can be shared as a link. The encrypted message sits after the # in the address: that part is never sent to the server. The link never contains a key or a password, and HashTag stores nothing.

Decrypting

Paste the message or drop the file: the format is detected. For OpenPGP, HashTag shows the IDs of the keys the message is addressed to. The result is only shown once integrity has been fully verified: a modified or truncated message is rejected.

Signing and verifying

A signature proves that the message comes from the holder of the private key and hasn't been modified. It doesn't hide the content. HashTag produces OpenPGP signatures, cleartext (for text) or detached (for files), as well as Ed25519, ECDSA P-256 and RSA-PSS signatures encoded in Base64.

Directory and key verification

Signing in with Discord proves that you control a Discord account, not that you own a key. A key is therefore “declared” at first. By signing a challenge with your private key from My keys, it becomes “verified”: you have proven that you hold the matching private key.

Even a verified key can belong to a compromised Discord account. For sensitive exchanges, compare the fingerprint with the other person over an independent channel (a call, in person). A change of primary key shows up in the history.

HashTag v1 file format

Password-encrypted messages use a documented, versioned binary container:

header   "HTAG" | version=1 | kdf | kdf params | salt (16) | nonce prefix (7) | chunk size (u32) | flags (1)
meta     length (u32) | AES-256-GCM(JSON { kind, name, type, size })
chunk i  AES-256-GCM(data)   nonce = prefix | i (u32) | last (0/1)

The whole header is authenticated with every chunk. The counter prevents chunks from being reordered, and the “last” flag detects truncation. Chunks are 64 KiB: a multi-gigabyte file is processed without loading it all into memory. As text, the container is Base64-encoded between -----BEGIN HASHTAG ENCRYPTED MESSAGE----- and the END line.

Compatibility

FormatWorks with
OpenPGPGnuPG, Thunderbird, Kleopatra, ProtonMail, Sequoia
PEM signaturesOpenSSL, Web Crypto, most programming languages
HashTag containerHashTag (open specification above)
age (X25519, post-quantum, passphrase, SSH Ed25519 / RSA)age, rage, typage — age -d -i ~/.ssh/id_ed25519 file.age