SecretPaste

Receipts

Know when the handoff happened.

Know when, where and on what device it was opened. See delivery events and the coarse context available for a reveal, without keeping the secret itself.

See receipt plansHow it works

Receipts

Keep a record of delivery. Leave the contents out.

A receipt helps answer whether a link was opened and what happened next. It describes the delivery event; it does not expose the encrypted message or prove that someone read and understood it.

Event

A useful event timeline

Follow the available creation, reveal, and terminal-state events. Check the handoff without asking someone to paste the secret back into a conversation.

Reveal recorded

Context

Context with limits

Where available, receipts show coarse location and browser or device context. These are signals about a request, not precise location tracking or proof of someone’s identity.

Coarse, when available

Content

A record outside the payload

Receipts contain metadata about the handoff. They do not contain your text, the original file contents, or the private decryption key.

Never in the receipt

A straightforward handoff

From your browser to theirs.

  1. 01

    Choose receipt access

    Compare plans and sign in to use the receipt and sender controls included with your plan.

  2. 02

    Share your link

    Create and send an encrypted handoff. The recipient opens it through the same explicit reveal flow.

  3. 03

    Check the delivery record

    Open the sender’s receipt to review the events and available request context.

“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 receipt prove the person read the secret?

A receipt records a reveal event. It cannot prove that a particular person read, understood, or retained the contents.

Is the location exact?

No. Location is coarse when available, and can be affected by VPNs, proxies, or network routing. Browser and device context can also be incomplete.

Do receipts contain the secret?

No. Delivery metadata is separate from the encrypted payload. Receipts never display the plaintext or the private decryption key.

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

Close the loop on sensitive deliveries.

Choose a plan with receipt access and keep a useful record around each handoff, without keeping the secret in that record.

See receipt plans