SecretPaste

Branded delivery

Your name. Their trust. One private handoff.

Your domain and identity around the same private payload. Give recipients a familiar place to receive sensitive text or a file.

Create a workspaceHow it works

Branded delivery

Recognizable on the outside. Private on the inside.

A familiar domain helps a client recognize who sent the link. Workspace branding surrounds the delivery experience while the browser encryption boundary stays the same.

Identity

A familiar domain

Connect and verify a workspace domain so recipients see a hostname they recognize. Domain ownership is checked before it can be used for delivery.

Your workspace

Domain

A consistent identity

Use your workspace identity across sensitive handoffs. Clients get a recognizable recipient experience whether you send credentials or documents.

Verified ownership

Payload

Encryption stays in the browser

Changing the domain or presentation does not reveal the plaintext to SecretPaste. The private decryption key still lives in the URL fragment.

Browser encrypted

A straightforward handoff

From your browser to theirs.

  1. 01

    Create a workspace

    Choose a plan with domain and branding controls, then set up your workspace identity.

  2. 02

    Verify your domain

    Follow the workspace domain setup and complete the required DNS verification.

  3. 03

    Deliver in your name

    Create a private handoff and share the branded link with the intended recipient.

“The recipient gets the secret. Our servers never get the plaintext or the decryption key.”

— The SecretPaste browser encryption boundary

Before you share

A few useful answers.

Does a custom domain change the encryption?

No. Browser encryption and the private URL fragment work the same way. Branding changes the surrounding identity and presentation.

Can I use a domain I already own?

Yes, supported workspace plans let you connect a domain you control. You must complete the domain verification and configuration before using it.

Does a logo prove a link is safe?

No. Recipients should still check the hostname and confirm unexpected requests with the sender. Branding helps recognition; it is not a substitute for verification.

More ways to make it private.

Text secrets

Encrypted in your browser, gone after one view. Send a password, a token, or an environment file without leaving its contents in a message thread.

Explore feature

File transfer

Streamed to storage, never through our API. Share a file or a folder with browser encryption and a lifetime you control.

Explore feature

Burn after reading

One atomic claim per view, then the ciphertext is gone. Give sensitive text or a file a clear end to its availability.

Explore feature

Make the handoff feel familiar.

Create a workspace, connect a domain you control, and give recipients a familiar place to open their next private handoff.

Create a workspace