Encrypted · Temporary · Zero-knowledge

My field

My field

Share Secrets Securely, Just Once

Type a note or attach a file. AshNote encrypts it in your browser, hands you a one-time expiring link, then forgets it ever existed. Why this matters →

Access Mode
Content
File Attachment (optional)

Drag & drop a file, or browse

Access protection

Anyone with the link can view

Send via

Two ways to use it

From personal handoffs to encrypted team workflows.

Anonymous

Quick, private one-to-one shares

  • Zero-knowledge encryption
  • Single-use, self-destructing
  • Expiring access windows

Workspace

Shared vaults for teams & orgs

  • Zero-knowledge encryption
  • Hybrid post-quantum key exchange
  • Vault expiry + grace period
  • Per-vault member access control

Harvest now. Decrypt later.

What you encrypt today
could be plaintext tomorrow.

Right now, adversaries are recording encrypted data they cannot yet read. Network traffic. Cloud transfers. Email attachments. Backups. File shares. Bank wires, health records, contracts, API keys, internal credentials: anything with a long enough shelf life to be worth saving. They do not need plaintext today. They need patience.

The harvest target isn't the encrypted file itself, symmetric crypto (AES, ChaCha) shrugs off Shor's algorithm. The target is the key-exchange handshake that protected it. Break the handshake, recover the key, decrypt every byte you ever recorded. So when a vendor says “post-quantum-ready,” the only question worth asking is: is your key exchange hybrid post-quantum, or still classical?

Not a roadmap item. Not a premium tier.

Post-quantum protection where it actually matters: key exchange.

“Post-quantum-ready” should not be a slogan. It should describe what protects the cryptographic flow.

AshNote uses the right primitive for the job: strong symmetric encryption for the secret itself, and hybrid post-quantum key establishment when keys need to be exchanged between users, devices, or vault members.

Different layer. Different threat. Different primitive.

No vague roadmap promise. No enterprise-only checkbox. Just modern cryptography built into the way sensitive material is shared.

“Post-quantum-ready” (everyone else)

  • “PQ on the roadmap.” Someday.
  • Server-side encryption keys you can't audit.
  • Plaintext lingers in chat, email, archives.
  • Classical-only key exchange. One Shor's run, every byte falls.
  • Premium tier. Enterprise add-on. Pay-to-survive.

AshNote (today)

  • AES-256-GCM + Argon2id on every secret payload. Symmetric, nothing for Shor's to break.
  • Encrypted in your browser. The key never reaches our servers.
  • Single-use links. Deleted after view or expiry. No archive.
  • X25519 + ML-KEM-768 (FIPS 203) on every workspace key exchange. Hybrid: if either primitive falls, the other still holds.
  • Standard. Every tier. No PQ upsell.

Don't take our word for it. Open DevTools and watch your browser encrypt it →

What’s actually in the harvest archive?

If it shouldn’t be readable in 10 years, encrypt it like it.

The everyday handoffs that pile up in inboxes, chats, and shared drives. They become tomorrow’s leak.

01

API Keys & Credentials

Pass API keys, database passwords, or SSH material to a teammate without leaving them in Slack or email.

02

Environment Variables

Share .env files or config snippets. The monospace editor preserves formatting exactly.

03

Legal & Financial Docs

Share wire details, tax documents, contracts, or deal terms through encrypted expiring links.

04

Wi‑Fi & Personal Passwords

Send Wi-Fi passwords, logins, or other personal info to family without leaving a trail in chat.

05

Healthcare & Patient Data

Reduce plaintext exposure when exchanging records, results, or sensitive coordination between parties.

06

Encrypted File Drops

Attach any file: PDFs, screenshots, certificates. Encrypted before upload, same expiring delivery.

Built into every secret

The security model in four pieces.

Single-use, then permanently deleted

After the first view, the encrypted payload is purged from storage. Small burn secrets are held exclusively in RAM (never written to disk), so once they're gone, they're gone. Unredeemed secrets are automatically cleaned up at expiry.

AES-256-GCM + Argon2id + post-quantum KEM

Content is encrypted client-side via the Web Crypto API. Passwords derive key material locally through Argon2id. Team and workspace key exchange uses hybrid X25519 + ML-KEM-768 for protection against both classical and quantum threats.

Encrypted file attachments

Files are encrypted in the browser before upload and transmitted as ciphertext. Same single-use delivery and expiry model as text secrets.

Team vaults with hybrid post-quantum key exchange

Vault keys are distributed via a hybrid KEM combining X25519 and ML-KEM-768 (FIPS 203), so only invited members can decrypt. Vaults support expiry, grace periods, and access controls.

Read the full security model