TEMPORARY
ENCRYPTED
ROOMS.
Boron 0.5 creates a chat room that exists only while people are in it. Messages are end-to-end encrypted in your browser. When a room ends, its context and records are deleted. No account, no durable server-side chat history, no files.
Keys are generated in this tab · nothing is stored
01. Encrypted on your device
Keys are generated in your browser and never leave it. The server relays ciphertext it cannot read, and holds no message content at any point.
02. No durable server-side chat history
Boron does not keep durable server-side copies of chat messages. Active rooms may provide a limited recent context window to verified participants, which clears when the room ends.
03. The room ends, the data ends
When the last participant leaves, the room and its coordination records are deleted and your keys are wiped from memory. Nothing durable remains.
How Boron works.
Initialize a temporary room
Create or join a room without an account. You get a unique link and a limited lifetime; all coordination data is temporary.
Exchange encrypted messages
Participants exchange encrypted text while the room is active. New joiners may receive a limited recent context window.
Room ends, context cleared
When the room ends or the lifetime expires, all active session context and ephemeral coordination records are permanently wiped.
No durable server-side chat history. Nothing durable remains after the room ends.
The server exists to introduce two devices to each other — not to keep a record that they met. Here is the full list of what it touches.
- — Message content, in any form, after a room ends
- — Private keys or ratchet state
- — Accounts, profiles, or contact lists
- — Files or attachments (not supported)
- — Durable server-side chat history after a room ends
- — Room record: id, expiry, capacity
- — Invite tokens, stored only as hashes
- — Bounded active-room context bundles
- — Presence rows with a last-seen stamp
- — Coarse rate-limit counters, no identifiers
- — Rooms expire at their chosen TTL
- — A stale participant is pruned after ~45 s
- — Empty rooms are destroyed after the grace window
- — A sweeper runs every minute, server-side
- — Keys are wiped on leave, close, or destroy
Encryption happens on your device: the server relays ciphertext it cannot read. Operational monitoring is aggregate-only — service health, never room or participant detail.
READ_FULL_POLICY