privacy and operational security

Encryption protects messages. UnoLock protects relationships.

If you’re a journalist, activist, lawyer, NGO, or anyone facing an adversary actively trying to identify you or access your data, you need more than content encryption. You need a system designed to minimize metadata, prevent correlation, and survive partial compromise.

Built to Survive

Threat-model-driven security for users under active targeting.

01.

Compromised Infrastructure

Client-side encryption and a zero-knowledge design reduce what a compromised server, logs, or cloud operator can reveal.

02.

Network Observation

Post-quantum key exchange and encrypted session channels protect data in transit and reduce opportunities for passive collection.

03.

Correlation & Relationship Graphs

Receive Addresses and local-only Known Addresses avoid global identities; multiple independent Receive Addresses let you compartmentalize transfer flows.

Three Data Transfer Primitives

Marketed as secure movement primitives, not “chat”.

VaultX Drop

Anonymous Ingress (Sender-Only)

Transfer data to a Receive Address without creating a Safe or inbox. VaultX Drop uses the same Receive Address format as Safe-to-Safe transfer, but the sender cannot receive replies.

For repeat workflows, VaultX Drop can save Known Addresses locally with password encryption.

Open VaultX Drop

Receive Addresses

Compartmentalized Destinations

Create multiple independent Receive Addresses and publish them for specific purposes (tips, case intake, research submissions, etc.). Rotate or revoke an address without exposing others.

Known Addresses are local-only labels you apply to Receive Addresses. They don’t create a global directory and don’t imply identity.

Read Documentation

Safe-to-Safe Exchange

Mutual Consent Channels

Two-way exchange without accounts or usernames. Consent is cryptographic; Reply Addresses enable controlled replies without exposing a persistent identity channel.

Data transfers are encrypted objects moving between Safes, designed to minimize metadata and reduce correlation over time.

Messaging Details

Starting Points

Same tech. Different story, depending on what you need to survive.

Journalists / NGOs

Publish a purpose-specific Receive Address and route sources through VaultX Drop to transfer documents without establishing identity-based channels.

Lawyers / High-Risk Professionals

Use compartmentalized Receive Addresses for case intake; save client destinations as Known Addresses locally; use Reply Addresses to control two-way exchange.

Security Researchers

Transfer reports and artifacts via purpose-specific Receive Addresses; rotate destinations; prefer VaultX Drop for one-way submissions when you don’t want an inbox trail.