Local-first architecture
Core conversation traffic moves directly between permitted stations rather than depending on a central cloud chat server.
Security & trust
Security is designed in layers.
Station Chat separates device identity, station-to-station protection, encrypted local storage, and optional conversation-level encryption so each control has a clear role.
Local-firstAuthenticated meshEncrypted storageAdmin-controlled trust
Security posture
Independent controls protect different parts of the system.
Encrypted station mesh
Authenticated peer sessions derive directional AES-256-GCM traffic keys with HKDF-SHA-256, enforce replay-resistant counters, and reject plaintext after authentication.
Encrypted local persistence
Sensitive persisted state is protected with authenticated encryption. Endpoint access, backups, and physical device security remain customer responsibilities.
Admin-controlled enrollment
A new station joins only after mutual cryptographic proof and explicit administrator approval. Network policy still decides which segments may communicate.
Optional DM end-to-end encryption
Supported direct-message conversations can add a separate end-to-end encryption layer above the authenticated encrypted station mesh.
Updates and operating boundaries
Customers should keep Station Chat and supported operating systems current. No application replaces secure endpoints, administrator credentials, network controls, backups, or user practices.
Report a vulnerability
Send security questions or responsible vulnerability reports to the Station Chat security contact.
Need the technical detail?
Review device identity, mesh session encryption, replay protection, storage controls, and station enrollment separately.