Content protection
Message bodies and attachments are encrypted on the endpoint with AES-256-GCM. Device keys are created through WebCrypto and private keys remain non-exportable in the browser.
Conversation keys are wrapped separately for each authorised device using ECDH and HKDF. The server transports envelopes and ciphertext but should not hold a content key.
- X25519 with P-256 as a platform fallback
- Versioned key envelopes per device
- Encrypted message editing
- Local decryption into short-lived file URLs
Ratchet maturity
The active baseline uses forward-moving sender chains with periodic renewal. A Double Ratchet implementation exists and has browser evidence, but activation remains limited through an explicit pilot allowlist.
Therefore VENTEX Connect currently claims neither universal post-compromise security nor Signal-level assurance.
Visible metadata
End-to-end encryption does not automatically remove all traffic data. The service still coordinates delivery, membership, devices and time.
- Communication relationships and memberships
- Time, delivery state and approximate activity
- Attachment media type and ciphertext size
- IP and security records according to the operating policy
Device verification
Safety numbers expose key changes. An optional strict mode can block sending to unverified devices.
Voluntary verification protects only when people compare the number over an independent channel and respond to warnings.