Ephemeral rooms
Random codenames by default, optional room phrases, participant votes, and leases that disappear after the session ends.
Daemonet Communications
Private conversations should belong to the participants.
Build direct chat, voice, video, file transfer, remote support, and temporary rooms with expiring capabilities instead of requiring every participant to create a permanent social account.
Communication without a biography
Create the session. Exchange only what the session needs.
A capability phrase can identify a temporary room without creating a public profile, contact graph, or recoverable chat archive. The host can keep room policy locally and transfer room authority through signed state.
Opt-in media
Negotiate authenticated peer media only after both participants accept the network and recording boundary.
Secure handoff
Offer a file, inspect its metadata, accept explicitly, verify integrity, and keep encrypted bytes out of coordination storage.
Temporary assistance
Grant a narrowly scoped, expiring support session without handing over permanent credentials or the rest of the network.
Participant policy
Vote to lock, unlock, or remove; keep durable workspace state only when participants explicitly choose a host.
Authenticated events
Use signed delivery triggers as a separate API primitive while the application keeps its actual state and authorization rules.
Session lifecycle
The coordinator introduces. The participants communicate.
Short-lived coordination makes the direct path possible without retaining the conversation. If a direct connection cannot be established, the current demo stops visibly.
Create a room
The browser generates fresh cryptographic state and a phrase with enough entropy to resist guessing.
Join deliberately
Each participant chooses a display name, accepts safety warnings, and proves possession of fresh session authority.
Introduce peers
1Man carries only encrypted, expiring signaling needed to attempt the WebRTC data connection.
Communicate directly
Messages and accepted file chunks cross the authenticated peer channel. Closing both tabs ends the room lease.
Responsible use
Encryption cannot control the person on the other screen.
Recipients can copy messages, photograph a screen, record a call, or retain a file after viewing it. “View only,” expiration, and download counts communicate policy; they are never DRM guarantees.
DaemonChat is not an emergency service, evidence vault, abuse-report archive, identity verification service, or promise of anonymity. Network operators can observe encrypted traffic metadata even when they cannot read content.
Legal boundary
Participants are responsible for what they send and for having the right to share it. Do not use the service for emergencies, imminent-harm reports, unlawful content, or situations requiring a durable evidentiary record.
Try the direct model