Encryption required
The client blocks sending until a Matrix room reports encryption as active.
Security model
Private by design. Honest by default.
VaultSec protects message content and narrows access surfaces without pretending that encryption makes endpoints, metadata or human choices disappear.
Keys stay local
Room keys are created and held on participant devices, not placed in marketing pages or automation.
Authority is server-attested
Elevated roles and permissions come from verified server state rather than a local label.
Updates are signed
The Windows updater verifies an Ed25519 signature, file size and SHA-256 before installation.
Automation is bounded
Bot Forge accepts declarative triggers and actions, never scripts, URLs, filesystem access or secrets.
Limits are stated
Metadata, compromised devices, screenshots and saved copies remain real security boundaries.
The actual boundary
What the relay sees — and what it does not.
The homeserver needs routing and membership metadata to deliver events. It relays ciphertext rather than readable message bodies, while approved participant devices hold the keys needed to decrypt.
No false promises
Encryption cannot recall a screenshot.
- A compromised endpointcan expose what its signed-in user can see.
- Downloaded or copied contentcannot be reliably removed from every external copy.
- Room and membership metadatais still processed where routing requires it.
- Security claimsmust match the exact released build, not a future roadmap.