Secure Link

📚 This article has been moved to new structured guides

Security First

Secure One-Time Link: Key Stays in Address

Need to share a password or note so no one can read it along the way? We encrypt text directly in your browser. The key only goes into the URL fragment # and never reaches the server. Opened — read — done. Link burns.

🔐 AES-GCM 256-bit
🔗 Ключ в URL#
👁️ Одноразово

How It Works

1

Browser Encryption

Text is encrypted locally with AES-GCM 256-bit algorithm. Plain text is never sent anywhere. This is important.

2

Key in URL#

The key is added after the # sign. Server only sees ciphertext. We honestly cannot read the content. And that's good.

3

One View or TTL

Link works exactly as long as you set: one view or time-to-live (TTL). After that — record is automatically deleted. Re-access is impossible.

Why These Links at All

Sometimes a password 'flies away' to chat and stays there forever. We give you a secure link: it's one-time, can be time-limited, and the key is stored with the recipient — in the address. And one more thing. Not obvious — but important: messenger previews don't reveal our secret (unfurl-safe).

What You Get

🔒

Maximum Security

Используем банковские стандарты шифрования для защиты ваших данных на каждом этапе.

  • AES-GCM encryption (like banks use)
  • Key only in URL fragment — server can't see it
  • We store only ciphertext and deadline metadata
⚙️

Access Control

Полный контроль над тем, кто и когда может получить доступ к вашей информации.

  • Time-to-live: from 5 minutes to 7 days
  • View limit: default 1
  • 'Burn Now' button if you change your mind
🛡️

Privacy by Default

Минимум данных, максимум безопасности. Никаких лишних сведений о вас.

  • No registration or accounts
  • No content logs (technical events — yes)
  • Fits 'minimal necessary processing' principle

Seems dry, but that's how it should be.

When It's Convenient

🔑

Passwords & API Keys

Sharing access within the team.

🛡️

Personal Information

Card numbers, passport data, short secret notes.

📋

One-time Instructions

Prod access, client accounts, temporary tokens.

In short — when you need to encrypt a message and share it securely. And then not worry about it hanging 'forever' in correspondence.

Create One-Time Link

Go to Generator

FAQ

We encrypt in browser (AES-GCM 256-bit). Key is stored in URL# and not sent to server. Even if we wanted to, we couldn't decrypt your text.
By default — no. This is a one-time link. You can set multiple views, but... better stick to one.
Yes, you can add a password to the link itself. We recommend sending the password through a different channel. More precisely: link — to email, password — to messenger (or vice versa).
Without the key from #fragment, ciphertext is useless. After first view, link becomes invalid.
No. We return a safe response for preview bots (unfurl-safe).
We don't see content, store minimal tech data and delete it by TTL. Details — on /security page.

Short and Sweet

Creating a secure link takes 10–20 seconds. Key in address, one view, peace of mind. Sometimes that's all you need.

🔒 Zero-knowledge
⚡ Instant
📖 Open source