PrivateTalk – Secure Message

Send 100% private, self-destructing messages. No logs, no tracking.

Write your message below. It will be encrypted in your browser and self-destruct after reading or expiration.

Extra Passphrase (optional):

The message can only be read using this passphrase (in addition to the link).

Warning: If you set an extra passphrase, the message will be destroyed after opening the link, even if the passphrase is incorrect. Please make sure you have the correct passphrase before accessing.

Auto-Expiration:

Choose a value from the menu or manually set expiration time:

Scheduled message:

Readable from:

...until (optional):

Set a start (required) and optionally an end time for when the message can be read.
Outside this window, no one will be able to access the message.

Option 1: Simple Sharing

Use this link for standard sharing through one channel (normal privacy).

Option 2: Dual sharing (maximum privacy)

1. Link (without key):

2. Secure fragment (#...):

Send the link and key (#...) through different channels (e.g. email + Signal).
The recipient just needs to append the key to the end of the link.

Export to personal log (Dashboard):

Save this line to your .txt file (you can add a tag after it, e.g., link,tag).
Then, in the Dashboard, you can manage and manually destroy messages.

Technical Details

Message ID:

Destruction hash:

Help / FAQ

Copy the personal log line above and use the Dashboard to monitor or destroy messages.
The code is open-source and fully auditable.
Public destruction/expiration logs are available (destruction | expiration).

Destruction proof hash:

Save this hash. After reading or expiration, check the public log to confirm your message was destroyed/expired.

How does it work?

The message is encrypted in your browser before being sent to the server.
You can optionally add an extra passphrase.
The server never has access to the original text or the encryption key.
The generated link contains a unique key (#fragment).
The message is destroyed automatically when read, or expires after the defined time.
You can set the message to only be read after a specific date/time.
Messages are only deleted when accessed with the correct key — failed attempts do not erase your message.
No data, cookies, or visitor tracking are stored.
Mathematical proof of destruction/expiration is available in public logs.
Open-source, transparent code for auditability.

Technical questions? See Bitcointalk Topic.

Secret message: