Features for Sharing Secrets That Self-Destruct

Stop sending passwords through Slack, email, or WhatsApp. Seal a secret to your recipient's post‑quantum key and send a token that burns after reading.

Start Free NowView API Docs
  • Sealed in your browser to the recipient's key — we never see your data
  • Auto-destructs after first view or custom expiry
  • No account required — your keys live in a vault in your browser
  • How the post‑quantum sealing works

How It Works

Set up your key vault once; after that, a secret takes under a minute

  1. Write

    Sealed

    Choose the recipient (a contact, or yourself), paste your secret and set a passphrase. It is sealed to their key in your browser.

  2. Share

    Opened

    Send the token, and the passphrase through a different channel. Opening it takes the passphrase and the recipient's private key.

  3. Burn

    Destroyed

    Link expires after first view or time limit. No trace left behind.

Why NoTrust.now?

True zero‑knowledge architecture. Your secrets are encrypted before they leave your browser.

100% Client-Side Encryption
Secrets are encrypted in your browser before leaving your device. We never see your data.
No Content Logs
We can't read your secrets even if compelled. We keep only the encrypted blob until it is read or expires, never its content, your passphrase or a private key.
Bound to the Recipient
Each secret is sealed to the recipient's ML‑KEM‑768 public key, so only their private key, together with the passphrase, can open it. ML‑KEM resists quantum attacks, so a copy recorded today stays sealed.
Auto-Destruct
Secrets automatically delete after being viewed or when time expires. No persistent storage risk.
Quantum ML-KEM-768
  1. Secret and passphrase entered in your browser
  2. ML‑KEM‑768 encapsulation to the recipient's public key
  3. Key = scrypt(passphrase) combined with the shared secret
  4. ChaCha20‑Poly1305 encryption
  5. Optional ML‑DSA‑65 signature with your private key
  6. Ciphertext sent to the server
  • Server stores only ciphertext
  • Passphrase and private keys never leave your browser
  • Burned after reading or on expiry

Who Uses NoTrust.now?

Built for developers and ops teams

Developers
Share API keys, database credentials, and environment variables with team members securely.
Sysadmins & MSPs
Send server passwords and access credentials to clients without email exposure.
Teams
Onboard new employees securely. Share WiFi passwords, VPN configs, and access tokens.

Post‑Quantum, Every Time

There is one mode. Every secret is sealed to its recipient with ML‑KEM‑768 and still needs its passphrase to open.

Quantum‑Safe

The only mode

The secret is encrypted under a key that combines two factors: a shared secret that only the recipient's private key can recover, and a key derived from the passphrase. The server holds neither.

What it changes: AES‑256 and ChaCha20 are not broken by quantum computers. Key exchange is the exposed part — RSA and elliptic curves fall to a large enough quantum computer. ML‑KEM‑768 takes that step, so a secret recorded today stays bound to its recipient's private key.

Creating a secret needs a key vault in your browser. Setting one up generates your ML‑KEM‑768 and ML‑DSA‑65 key pairs, and the create page guides you through it.

  • ML‑KEM‑768 (FIPS 203) seals the key to the recipient
  • Passphrase as a second factor, derived with scrypt
  • ChaCha20‑Poly1305 authenticated encryption
  • Optional ML‑DSA‑65 (FIPS 204) signature from the sender
Create a Secret

Ready to Share Secrets Securely?

Set up your key vault and seal your first secret in a couple of minutes. No account required.

No account required • Free forever for basic use

Start Free NowView API Docs