Security

Strong cryptography,
plainly explained.

No buzzwords and no magic. Here's exactly how ArkAChat protects you, which algorithms it uses, and what it can and can't defend against.

Nothing to identify you

No phone number, email or username, and no global user ID. Each contact is a separate pairwise connection.

Encrypted end to end

Messages are encrypted on your device and only decrypted on your contact's. Relays only ever handle ciphertext.

Forward secrecy

Every message uses a fresh key derived from the last, and old keys are wiped, so past messages stay sealed.

Specification

What's under the hood

ArkAChat's encryption engine is Shield, developed by Dikestra AI. The same wire format is shared across Android, Web and Desktop, and tested against common test vectors.

  • 256-bit keys throughout. The best known quantum attack on 256-bit symmetric keys still leaves about 128-bit security.
  • Random padding. 32–128 bytes added to every message, so message length reveals nothing.
  • Out-of-band verification. Compare a short security code when you connect to rule out interception.
Identity model
None: one pairwise connection per contact
Key exchange
One-time QR invitation + security-code check
Message keys
256-bit, ratcheted forward on every message
Group & file data
AES-256-GCM, separate key per file
Group admin actions
ECDSA P-256 signatures, verified by every member
Message length
Hidden with 32–128 bytes of random padding
Local storage
Encrypted database; keys in the OS keystore
Desktop hardening
Sandboxed renderer, strict CSP, Electron fuses
Threat model

What we protect, and what we don't

Honest security means being clear about the limits.

Protected

  • Relay servers or network observers reading your messages
  • Your identity being tied to a phone number or email
  • Old messages being exposed if a single key leaks
  • Someone quietly adding themselves to a group
  • Message length giving away what you sent

Out of scope

  • A device that is already compromised by malware
  • Someone with your unlocked phone in their hand
  • A contact who screenshots or forwards your messages
  • Skipping the security-code check when you connect
Responsible disclosure

Found a vulnerability?

We'd like to hear about it. Please report security issues privately through GitHub's security advisory process, not in public issues. We'll acknowledge your report and keep you updated while we fix it.

ArkAChat is in early access. The code is fully open for review, but it hasn't had an independent third-party audit yet. If your safety depends on your messenger, take that into account. We'll publish audit results here when they're available.

See it for yourself.

Every line of ArkAChat is public. Read it, build it, verify it.