Open security model

Don't trust us.
Verify us.

Security claims are cheap. This page names every mechanism behind ours — and is honest about today's limits.

What we do — and don't

We do

  • Encrypt every message end-to-end with AES-256-GCM.
  • Keep keys on your device, gated by passkey.
  • Let you verify a contact's fingerprint yourself.
  • Seed key material with quantum entropy.

We don't

  • Ask for accounts, phone numbers, or email.
  • Store messages on any server.
  • Keep logs we could be forced to hand over.
  • Claim to hide metadata we can't yet hide (see below).

The mechanisms

Identity Lock

Passkey

Your identity key never leaves the device, and only unlocks with your biometric.

Honest limit端末そのものが侵害された場合、パスキーは守れません。デバイスのロックと最新状態の維持が前提です。
Implemented
Transport

WebRTC · Peer-to-Peer

Devices talk directly. The signaling server only introduces peers — it never sees the conversation.

Honest limitNAT越えのためTURN中継が必要な場合があります。中継時もペイロードは暗号化済みですが、接続メタデータ(誰がいつ接続したか)は完全には隠せません。
ImplementedMetadata hardening · planned
Encryption

AES-256-GCM

Every message is sealed with authenticated encryption — confidentiality and tamper-detection in one.

ImplementedPost-quantum KEM · planned
Randomness

Quantum Entropy

Key material is seeded with true randomness from the ANU Quantum Random Numbers API — not a software PRNG.

Honest limit量子乱数は"鍵生成の質"を高めるものであり、それ単体がプライバシーを保証するわけではありません。土台はあくまで「保存しない・E2E・パスキー」です。量子源が利用できない場合はOS提供のCSPRNGにフォールバックします。
Implemented

Independent audit — on the roadmap

Third-party audit · plannedOpen source client · planned

Read it. Then decide.

Transparency is the feature. The rest is up to you.