Private content belongs to trusted devices.

COMS does not call itself unhackable. It documents what the server can observe, what it cannot decrypt, and which capabilities are still gated.

Client-side boundary

Private messages and attachments must be encrypted before the server receives them. The current gateway rejects a plaintext message API.

Development adapters, disabled production features, and operational readiness are labeled rather than presented as finished security.

Cryptographic libraries, device authorization, mail, storage, and protocol changes remain gated until their evidence and review requirements are met.

Read the detail

Review the architecture and threat model before relying on any COMS capability.