Security

Experimental alpha, honest security posture.

Callrift has real security foundations, but it is not yet a mature secure messenger. Use the alpha for inspection and development, not high-risk communication.

Implemented in the current alpha

  • Username-native identity with no phone-number registration.
  • Argon2id password hashing, CSRF protection, secure production cookies, CSP, and strict referrer policy.
  • Invite-only signup, contact requests, blocks, DM permissions, moderation events, and audit foundations.
  • Browser-side local-alpha message sealing, server-side ciphertext envelope persistence, worker-verified OpenMLS readiness, transitional OpenMLS delivery for direct rifts and selected server text channels, multi-credential Welcome delivery, public commit replay, worker-level OpenMLS remove commits, and settings-driven credential retirement that attempts browser-generated remove commits before metadata-only retirement.
  • Contact-gated 1:1 WebRTC signaling, TURN credential minting, and diagnostics without media recording.

Not claimed

  • No Signal-grade, military-grade, unbreakable, anonymous, metadata-free, or MLS-complete claims.
  • Final E2EE, complete OpenMLS device removal across unavailable browser state, group key rotation, recovery flows, and media E2EE are not complete.
  • Rust is the runtime, but runtime choice is not a security claim by itself.