Core trust model
- Message bodies are represented with ciphertext, nonce, and version fields.
- Identity context can be conversation-scoped for controlled profile behavior.
- Disappearing behavior can further reduce retained message surface.
VeilAppSecurity & privacy4 min read
Understand the encrypted payload architecture
Veil messaging architecture uses encrypted payload patterns and identity-aware communication flows to support private conversation transport.
Quick summary
Messages are handled as ciphertext/nonce/version payloads, with identity-aware communication context.
What this means in practice
- Verify who you are chatting with before sharing sensitive material.
- Use message requests and blocking to limit unsolicited access.
- Combine retention controls with workspace policy for stronger governance.
Important limitation reminder
- No communication platform can fully protect against compromised endpoints.
- Pair encryption with device hygiene and strong access practices.
Related guides
3 min read
Revoke workspace devices
Remove compromised endpoints from workspace access and enforce revocation across channel activity.
4 min read
Audit logs and domain verification
Use audit records for visibility and DNS-based domain verification for organizational trust.
Still need help?
Include your device type, OS version, app version, and a short issue summary when contacting support.