Client-side encryption
Supported private messages are encrypted in the browser before delivery. Identity, session and routing records remain separate service data; the privacy notice explains which usage fields the service currently retains.
Private messaging without a phone number
Start a one-to-one conversation without putting a personal number or public profile at the centre of it.
Invite directly
Share a QR code, private link or chat key with the person you want to reach. The core chat flow does not require a traditional public account profile.
Messages are encrypted in your browser
Supported private messages use client-side ECDH key agreement, HKDF-SHA256 key derivation and AES-256-GCM authenticated encryption before the protected envelope is sent to the service.
Private content, operational metadata
Chat256 still processes session and routing information to deliver conversations, maintain service reliability and investigate abuse. Encryption protects message content; it does not make network activity anonymous.
Use expiry when it helps
Supported conversations can use message expiry. It reduces persistence in the service but cannot remove copies saved by a recipient.