PERSONAL
Some conversations should stay in the room
For difficult moments that do not need to become a permanent record.
Private conversations that leave no trails here
Nema routes messages live between two people and writes nothing to disk.
No server archive.
No offline inbox.
No stored ciphertext.
When the space ends, it's structurally gone — not just deleted.
What changes
Live only
No server trail
Private by design
MOMENTS
Built for conversations that feel wrong to leave behind by default
Not every conversation needs a permanent record. These are the kinds of moments Nema is built for.
CONFIDENTIAL
Discuss the work. Not the trail it leaves behind
For technical, internal, and high-stakes conversations where discretion matters.
URGENT
A warning delivered live, not stored for later
For time-sensitive conversations where privacy matters before, during, and after the message.
INTIMATE
Not every private night should leave a trace
For conversations shaped by trust, distance, and what should remain between two people.
HOW IT WORKS
A private space, a verification step, that stays live only
Nema is built for a narrower use case than a normal messenger. You open a private space, verify who is on the other side, talk live, then end it.
01
Open a private space
Enter the other person’s exact username. If they are online, they receive an invite. There is no contact discovery and no offline queue.
02
Verify before sending
Compare the safety number out of band. Sending stays blocked until both sides verify, reducing impersonation and wrong-recipient mistakes.
03
Talk live, then end the space
Messages move only during the active private space. End Space stops live delivery for both sides and clears the in-app conversation view.
Why Nema exists
Privacy is not an edge case. It is the point.
Most communication infrastructure assumes retention. Not because it is necessary — but because storage is cheap and nobody said otherwise.
Everything is stored, synced, queued, indexed, and kept indefinitely. The default was never chosen. It accumulated.
Private conversation is normal. The fact that infrastructure can retain everything does not mean it should. Capability is not justification.
Corporations and governments should not inherit long-term visibility into personal conversation as a side effect of using a messaging product. That inheritance was never negotiated. It became the deal because the industry kept treating storage as the neutral default — and most people had no alternative.
Nema is the alternative. Live, encrypted, private conversation with no server-side message history. When the space ends, it ends — not archived, not recoverable, structurally gone.
That narrowness is not a missing feature. It is the argument.
What Nema stores and what it does not
We store
- Your username and a password hash, never your plaintext password
- Authentication/session state used to keep you signed in and invalidate sessions when needed
- Your optional E2EE public key material for identity binding in private spaces
- Subscription and plan state where applicable
- Limited rolling anti-abuse and rate-limit counters needed to protect the service
We do not store
- Message bodies or conversation history
- Offline inbox or queued delivery
- Server-side transcript or archive
- Contacts uploads or ad-tracking identifiers
Important reality
No web app can reliably stop device-level screenshots or recordings.
Nema’s promise is narrower and real: no server-side message history exists to recover later.
FAQ straight answers
Does Nema store messages?
No. Messages are relayed only during an active private space. No server-side transcript exists.
Can I message someone who is offline?
No. There is no offline inbox and nothing is queued for later delivery.
Why is verification required?
Because sending to the wrong person once is enough. Nema requires both sides to verify before messages can be sent.
What does End Space do?
It stops live delivery for both participants and clears the in-app conversation view for both sides.
Can Nema prevent screenshots?
No. Device-level capture cannot be reliably prevented in a web app. Nema is designed to avoid server-side history, not to claim impossible protections.
Is this a replacement for everyday messaging?
No. Nema is a narrower tool for live private conversations where reducing retention matters more than convenience features like offline delivery and persistent history.
Get started
Open a private space that ends with the conversation.
Nema is built for messages that should happen live, stay between the people involved, and leave nothing sitting in a server archive afterward.