Ciphertext + nonce + version model
Message persistence follows a structured encrypted format that supports compatibility and key lifecycle evolution.
VeilAppEncrypted payload architecture
Message bodies are handled as ciphertext with nonce and version metadata, keeping plaintext outside server storage paths.
Veil uses an encrypted payload model in direct chats, groups, and channels. The backend persists ciphertext structures while delivery and read states are tracked through safe metadata flows.
How this works in Veil
Cross-context consistency
The same encryption-first approach appears across direct messaging, group messaging, and workspace collaboration surfaces.
Identity-aware routing
Identity and key-management pathways support scoped identity behavior and controlled communication boundaries.
Implemented capabilities
- Server-side message storage uses ciphertext/nonce/version fields.
- Read and delivery timestamps are updated without exposing plaintext.
- Communication operations integrate with authenticated user context and policy checks.