Protects free speech
Talk in a room built for the conversation itself, not for distribution, engagement, profiling, or later inspection.
NullTrace
A private space
to speak freely.
End-to-end encrypted rooms. Invite your people, choose who enters, and talk without a permanent chat archive.
What it does
NullTrace is not a feed with privacy bolted on. It is infrastructure for people who need to speak freely and leave no platform-owned trail behind.
Controls who enters
Entry happens through a temporary invite capsule. You approve participants instead of publishing to an audience you do not control.
Encrypts before transport
Messages are encrypted in your browser before they move. The server passes encrypted traffic; it is not a place where readable conversations live.
Leaves less behind
No permanent chat archive, no ad profile, no account timeline. NullTrace is built for conversations that happen, serve their purpose, and disappear.
Why it works
Free speech needs more than a policy promise. NullTrace makes the room technically hard to abuse: approve entry, encrypt locally, rotate keys, store no readable history.
Encrypt first. End-to-end encryption starts locally, before a message leaves your device.
Hybrid keys. X25519 and ML-KEM-768 establish session secrets; Double Ratchets refresh epoch delivery keys.
Short-lived entry. Signed invite capsules carry an expiration time and require host approval.
Approved members. Participants enter through verified handshakes and fresh room keying.
Traffic shaping. Padding and random cover frames add traffic variation; timing remains observable.
One active session. Access is limited so quiet account sharing and invisible parallel use get harder.
Signal Comparison
Signal and NullTrace serve different workflows. Signal is a persistent messenger; NullTrace focuses on temporary, host-approved browser rooms. Their encryption and retention models differ.
Area
Signal
NullTrace
In practice
Identity
Starts from a phone-number account, with usernames added as a contact layer.
No phone number or public profile; access uses user and restore keys.
Room identities are separate from phone numbers and address books.
Room control
Groups live inside a persistent messenger account and contact graph.
Rooms are created on demand with signed, temporary invite capsules and explicit approval.
Hosts approve membership for each temporary room.
Encryption model
PQXDH and the Triple Ratchet, combining the Double Ratchet with post-quantum SPQR.
X25519 + ML-KEM-768 setup, vodozemac Double Ratchet for epoch delivery, and per-message sender chains.
NullTrace's ongoing DH ratchet is classical; Signal also ratchets post-quantum secrets.
Message isolation
Ratchets derive fresh message keys and delete earlier keys.
Each sender chain derives a new XChaCha20-Poly1305 key per message; signatures bind sender and packet metadata.
Used keys are erased; a bounded, temporary key cache permits reordered messages.
Membership secrecy
Group history belongs to the device history and group conversation model.
Fresh epoch seeds go to current members after approval, removal, and periodic rotation.
New members receive no previous epochs. Removed members receive no subsequent epochs.
Message retention
Device message history, app state, and notifications can leave OS-level residue depending on settings.
No push notifications, no inbox archive, no platform notification previews, burn timers, deadman, one-tap wipe.
Burn timers remove visible messages; browser and OS traces are still possible.
Server breach
A messenger service still has account, device, delivery, and abuse-prevention structure around users.
Browsers encrypt content; the relay holds short-lived ciphertext. Access records are stored separately.
Relay data alone cannot decrypt content; compromised browser code can expose it.
Server visibility
A delivery service for known accounts, devices, and contactable identities.
The relay sees connection and room metadata but does not receive message plaintext or keys.
Encryption protects content; it does not hide connection timing or room membership from the relay.
Intended use
Everyday private messaging in a persistent app.
Temporary browser rooms with host approval and no permanent chat archive.
Choose according to room controls, retention needs, and device security.
FAQ
Do I need an account?
No. NullTrace does not need usernames, phone numbers, email addresses, or a public profile. Access is controlled by your user key and restore key, so the product can stay focused on rooms and encryption instead of identity collection.
Can NullTrace read my messages?
No readable chat history is stored for NullTrace to browse later. Message content is encrypted before transport, sent as protected room traffic, and only the approved participants in that room are meant to decrypt it.
What happens if I lose my keys?
You can lose access. Save both keys somewhere offline before continuing. If it happens, contact us and we can look at what is still possible, but the system is intentionally designed so keys matter.
How many people can be in a group conversation?
A room supports up to 16 participants, including the host. Each participant needs host approval, and membership changes trigger fresh epoch keys.
Choose access
Payment
Plan
Exact SOL amount
Deposit address
Waiting for payment...
Save your access keys
Anyone with these keys can access or reset your NullTrace access. Store them offline. If your restore key is exposed, someone can revoke your current session.
User key
Restore key
Sign In
Your key is all you need. Paste it below to enter.
This access is currently active somewhere else. Enter your restore key to move access here. The old session will be logged out.