We do not describe security as an absolute. We break it into testable layers, documented boundaries and reproducible evidence.
Each installation has its own cryptographic identity. Private device keys are created as non-exportable and remain in the browser. New devices are visible, verifiable and individually revocable.
Short-lived access tokens are backed by rotating refresh tokens. Reusing an old token revokes the entire session family instead of failing silently.
Messages, reactions, attachments, local history and selected preferences use distinct encryption paths. The Double Ratchet remains a controlled pilot, not an overstated universal claim.
Web releases are signed away from the server. Independent rebuilding compares every delivered byte; the service worker verifies the signed manifest before caching assets.
Platform or hardware-backed second factor.
Controlled local wipe and server revocation.
Discrete sign-in path that revokes other sessions.
Restricts scripts and outbound browser targets.
Short-lived signed object URLs.
Continuously measures production files and scripts.
“A green test is only as strong as the rule it actually verifies.”
VENTEX security principle
Boundaries, evidence and outstanding audit work are documented explicitly.
