Skip to content

Using Receive Addresses

Overview

Receive Addresses are shareable inbox addresses for Vault Messaging. They let you receive messages and files to a Safe through an address.

Each Receive Address has: - Its own keypair - Its own intake policy (usage limit, throttle, attachments) - Client-side hashed routing (vaultxAddressHash) so the raw address is not sent to the server

This makes intake compartmentalized and easy to revoke.

Capabilities by Tier

Both Sovereign and HighRisk can create and manage Receive Addresses, send messages and files, and allow replies. Complete new-Safe activation before configuring addresses.

Create a Receive Address

Prerequisites: - Sovereign or HighRisk tier - Authenticated Safe session

  1. Open Messaging In the Safe app, open the Messaging section.

  2. Go to Receive Addresses Select the Receive Addresses (or Addresses) tab.

  3. Create a new address Click New Receive Address.

  4. Configure address settings Set optional controls:

  5. Sender message: public note shown to senders in UnoLock Drop. You can use this as a pre-shared code word so senders can verify they are using the correct address.
  6. Private label/description: internal-only label for your inbox.
  7. Usage limit: cap how many times the address can be used.
  8. Throttle: rate limit incoming drops.

  9. Attachments: allow or block file uploads.

  10. Save and generate The app generates a Receive Address and a shareable URL.

Share a Receive Address

  • Copy the address and share it directly, or
  • Share the URL to open the UnoLock Drop client with the address prefilled.

Manage Address Lifecycle

  • Disable an address to stop new messages while keeping it visible.
  • Delete an address to revoke it entirely.
  • Rotate by creating a new address for a new source or project.

Where Messages Appear

Messages sent to a Receive Address appear in Messaging, grouped by address. Decryption happens client-side inside your Safe.

Operational tip

Use a different Receive Address per source, campaign, or project. This minimizes cross-linking and keeps revocation simple.

Code-word check

For higher assurance, agree on a short code word with the sender and place it in the Receive Address sender message. The sender should only send if that code word is displayed in UnoLock Drop.

High-risk sender guidance

If you share a Receive Address publicly, advise senders to use Tor Browser with UnoLock Drop for stronger network anonymity.

If you are looking for anonymous sending instructions, see How to Send a Message with UnoLock Drop.