1. Create
Start a private conversation from the supported Chat256 app. The core workflow does not require a phone number or traditional public profile.
2. Invite
Use a supported private link, QR code or chat key. Direct invitations let participants decide who receives the connection information.
3. Talk
Exchange supported messages in real time. The current private-message architecture uses browser-side cryptography with server-side authentication and delivery.
5. Call
Move to voice or video through the WebRTC subsystem. Browser permissions and network connectivity still determine whether a call can connect.
6. Reduce persistence
Where supported, disappearing-message expiry can reduce how long messages remain available. It cannot stop a recipient from preserving a copy.
Start with the communication method you need
Create a room when you want a new conversation, or use the supported account and identity workflow when you need persistent contacts and sessions. Invitations can be shared directly using the mechanisms provided by the application.
Protect content before it travels
For supported messages and files, the browser performs the cryptographic work before protected data is sent through the service. The server therefore handles encrypted envelopes and transfer state rather than acting as a plaintext message reader.
Switch from chat to a call
When calling is available, the same conversation can use browser-based WebRTC voice and video. Signalling coordinates the connection while ICE, STUN and TURN determine how the media path is established.
Finish cleanly
Use expiry and deletion controls when appropriate, close calls when finished, and remove files you no longer need. These controls reduce retained data but cannot control copies made by another participant.