Own product · In production
Latens Chat: privacy, ephemeral memory and control
Private, ephemeral messaging without registration, email or phone number to create or enter a conversation.
Open Latens Chat
01
Problem
Private conversations often require a persistent identity and leave content or metadata around longer than necessary. Latens Chat starts with a different question: what can be removed from the flow without preventing a useful conversation?
02
Solution
Access uses a room code and PIN. Content is encrypted on devices and travels in real time through SignalR and WebSockets. The server acts as a relay that does not receive readable message content.
How it works
- No account, email or phone number
- Room code and PIN access
- End-to-end encryption
- Real-time communication
- Temporary in-memory content
- Conversation purge
- Manual and automatic room destruction
03
An explicit data lifecycle
Content lasts while the conversation exists or until a participant purges it. The room can be destroyed and deletion remains under user control. The system is not described as storing content on disk, and it makes no absolute security claims.
04
Security and privacy
X3DH establishes initial key material and Double Ratchet evolves message keys. This describes the published design; it is not a substitute for an external audit and does not claim the system is invulnerable.
05
Confirmed stack
- PWA
- ASP.NET Core API
- SignalR
- WebSockets
- X3DH
- Double Ratchet
Interface
Clear access on desktop and mobile
Do you need to solve a similar problem?
Let's discuss the real context, data and constraints.