One-Time Secret Link

Share encrypted text and passwords through a link that can be opened only once. Messages are encrypted in your browser and automatically expire.

Create a one-time secret link

Your browser encrypts the text before sending it. Only the encrypted data is stored on SwiftVecto.

Encrypted locally with AES-256-GCM 0 / 16,384 bytes

Privacy and one-time access

The encryption key remains in the URL fragment and is not included in normal requests to SwiftVecto. Your browser encrypts the message before upload.

Opening the recipient page does not consume a secret. The recipient must explicitly select Reveal secret. Once retrieval succeeds, its encrypted record is deleted from active storage.

A lost network response may consume the message before it is displayed. The service cannot verify the reader's identity, prevent copying, or guarantee immediate removal from infrastructure backups.

How to Share a One-Time Secret Securely

Create a link for securely sharing a password, token or private note. The recipient can reveal its contents once before the server-side encrypted copy is consumed.

Overview

One-Time Secret Link uses authenticated browser-side encryption to protect a message before it is uploaded. SwiftVecto stores only encrypted data. The recipient needs the complete generated link to retrieve and decrypt the message. The link must be delivered through a channel you trust, because anyone possessing it may be the first to reveal the secret.

Benefits

Encrypt sensitive text in the browser before uploading it.
Send a one-time link instead of putting the secret in a regular email or chat.
Set an automatic expiry for secrets that remain unopened.
Use the service without creating an account.

How It Works

Your browser creates a random encryption key and encrypts the secret using AES-256-GCM.

The server stores the encrypted message with an expiration time and an independent access token hash.

The generated link contains the decryption key in its URL fragment, which is not sent in normal HTTP requests.

An explicit reveal request atomically consumes the encrypted record; only the successful recipient can decrypt the returned ciphertext.

How to Use This Tool

  1. 1
    Enter the text you want to share.
  2. 2
    Choose when the secret should expire.
  3. 3
    Generate the encrypted one-time link.
  4. 4
    Copy the complete link and send it through a trusted communication channel.
  5. 5
    The recipient opens the link and chooses Reveal Secret to decrypt it once.

Helpful Tips

  • Verify the recipient through a separate channel for high-risk credentials.
  • A one-time link does not prevent a recipient from copying revealed content.
  • If the recipient loses the link or key fragment, the server cannot recover the plaintext.
  • Rotate shared passwords and tokens where appropriate after use.

Common Uses

Send a temporary account password to an IT colleague.

Share an application setup token with another developer.

Deliver a short confidential note without leaving plaintext in a chat history.

Worked Examples

The following examples demonstrate how this tool can be used in realistic scenarios.

Sharing a Temporary Password

Generate a unique link for a newly issued temporary password, send it to the intended recipient, and have them reveal the encrypted message once before it is consumed.

Common Mistakes

Avoid these common mistakes to achieve the most accurate results.

  • Posting the complete secret link in a publicly accessible location.
  • Assuming a one-time link verifies the identity of whoever opens it.
  • Assuming one-time retrieval prevents screenshots or copied plaintext.

Glossary

Definitions of the most important terms used by this tool.

AES-256-GCM

An authenticated encryption mode that provides both confidentiality and integrity checks.

URL fragment

The portion of a URL after #, which is not sent in an ordinary HTTP request to the server.

One-time retrieval

An access policy under which only one retrieval request can successfully consume a stored secret.

Frequently Asked Questions

Can SwiftVecto read my secret?

The tool is designed to encrypt the secret in your browser before sending it to SwiftVecto. The server does not receive the plaintext or the encryption key during normal creation or retrieval.

What happens after the link is used?

The server atomically consumes the encrypted record when a reveal request succeeds. The browser can display the decrypted message, but the same record cannot be retrieved a second time.

What if the link expires?

An expired link cannot be used to retrieve the message, and expired encrypted records are removed by scheduled cleanup.

Can I use the link more than once?

No. The Phase 1 tool allows one successful retrieval request per secret.

Things to Know

  • The recipient must receive the entire generated URL, including its fragment.
  • Opening the recipient page alone must not consume the secret; the user explicitly chooses Reveal Secret.

Disclaimer

Anyone with the complete link may attempt to reveal the secret; possession of a link is not identity verification.

Recipients can copy or save a secret after it has been revealed.

Removal from active storage does not guarantee immediate erasure from all infrastructure backups.

Official References

The following official resources were used when developing this tool and are useful for further reading.