Security & Privacy
How Boron 0.5 protects your communication without keeping records.
How Boron Works
01.
Create or join a temporary room.
02.
Exchange encrypted messages in real-time.
03.
Room ends, session context clears.
Frequently Asked Questions
Do I need an account?
No. Boron 0.5 does not require signups, profiles, or email addresses. Each room is independent and anonymous.
Are rooms temporary?
Yes. Every room has a lifetime. Once that time expires, the room and its coordination data are permanently destroyed.
Do you store my chat history?
No. Boron 0.5 has no durable server-side message history. A verified participant joining an active room may receive a small recent context window from another participant. That context is encrypted for the recipient, exists only while the room is active, and is cleared when the room ends.
What happens when someone new joins?
If a room is live, a newly joined participant may receive a limited, recent context window (last 20 messages, up to 10 minutes old) to catch up. This data is strictly bounded and clears when the room ends.
Are files retained?
Boron 0.5 does not support file attachments or uploads. No files are retained.
How can I verify participants?
You can verify that you are talking to the intended person by comparing 'safety numbers'—unique fingerprints for your encrypted session—displayed inside your chat room.
Security & Privacy Overview
- Encrypted room communication: All messages are end-to-end encrypted using industry-standard protocols, ensuring that only participants can read them.
- Participant verification: You can verify your connection to other participants via safety numbers within the chat interface.
- Temporary teardown: Rooms are designed to be short-lived. Once a room expires or is destroyed, its coordination records are permanently deleted.
- Bounded context: When a verified participant joins a live room, they may receive a temporary, bounded window of recent messages for catch-up from a peer, which is never stored durably on the server.
- Zero durable history: Boron 0.5 does not store message content, durable server-side history, or user metadata after a room's lifecycle is complete.