E
Ephemeral
TTL-Based Architecture

Chat that disappears.

Real-time messaging with automatic expiration. No signup. No storage. Just ephemeral conversations that vanish by design.

All systems operational

Built for privacy and simplicity

Purpose-built architecture that prioritizes ephemerality, performance, and zero data retention.

Ephemeral by Default

Chat rooms automatically expire. Rooms, messages, and user data vanish after their TTL ends.

Real-Time WebSocket

Sub-millisecond message delivery. Live presence indicators and instant notifications.

Privacy First

Zero permanent data storage. No databases for conversations. Everything is stateless.

Admin Controls

Room creators can manage participants. Approve/remove users with granular control.

Simple Access

Join with just a Room ID. Optional password protection for sensitive conversations.

High Performance

Redis-backed auto-cleanup. Stateless backend scales infinitely. No maintenance needed.

Three steps to ephemeral chat

Simple, stateless, and designed for privacy.

1

Create or Join

Generate a new room or join an existing one with just a Room ID and optional password.

2

Real-Time Chat

Invite others and start messaging. Your session is saved locally—no login required.

3

Auto Expires

When the TTL expires, the room, messages, and all user data are automatically deleted.

Privacy by architecture

Traditional chat apps store everything forever. We store nothing permanently. Your conversations are managed entirely in Redis with automatic TTL-based cleanup.

  • Messages purged after room TTL expires
  • No permanent user accounts or databases
  • Session data stored only locally
  • Stateless backend—truly ephemeral
  • GDPR-compliant by default
redis-cli
> SETEX room:xyz 3600 {...}
OK
> LPUSH messages:xyz {...}
1
# After 3600s, all data is gone
> GET room:xyz
(nil)