Multi-Layer E2EE Architecture
Arc Protocol: Signal Protocol (libsignal) as the foundation, with PQXDH (ML-KEM-1024) post-quantum cryptography, XEdDSA signatures, and client-side Sealed Sender.
Read it,or lose it.
WORLD'S FIRST KEY-DESTRUCTION E2EE
Receive
Key generated · 24h timer starts
24h elapsed
Still unread, 23 hours 59 minutes
Key destroyed
Mathematically impossible to decrypt
PQXDH Key Exchange
Hybrid post-quantum key exchange combining X25519 (Curve25519) and ML-KEM-1024 (NIST FIPS 203). Resistant to both classical and quantum attacks.
Double Ratchet
Per-message forward secrecy using DH ratchet + symmetric ratchet. Compromise of one key cannot decrypt past or future messages.
AES-256-GCM Encryption
Authenticated encryption with 256-bit keys. Each message encrypted with a unique key derived from the Double Ratchet.
XEdDSA Signatures (libsignal)
XEdDSA signatures via libsignal. Identity Key (X25519) doubles as signing key. Device list integrity verification included.
Client-Side Sealed Sender
Ephemeral X25519 key per message + HKDF-SHA256 derived AES key. Even the server cannot see who sent a message.
Read-or-Lose Encryption
Read it, or lose it.
Messages unread for 24 hours become mathematically undecryptable. Not deleted — the decryption key itself is destroyed. No court order, server subpoena, or device seizure can reconstruct the content.
How It Works
24-Hour Key Lifetime
Every message is encrypted with a decryption key that lives for exactly 24 hours. After that, the key is cryptographically destroyed — on the sender's device, the recipient's device, and the server.
Read Before 24h
If you read the message within 24 hours, the plaintext is safely stored on your device per your IGF timer (up to 52 weeks on paid plans).
Unread at 24h
If you don't read in time, the message becomes permanently unrecoverable. Even Atlas Associates cannot bring it back.
Read-Triggered Re-keying
The moment your inbox hits zero unread, your decryption key rotates immediately — maximizing forward secrecy.
Mathematical Guarantee
Not policy, not promise — the math itself prevents recovery. No court order, server subpoena, or device seizure can reconstruct the content.
Transparent Unread Status
Both sender and recipient see when a message expired unread. Like a missed call log — you know it happened, but the content is gone forever.
Works With IGF
Read-or-Lose protects the 24h before reading. IGF (up to 52 weeks) protects the plaintext after reading. Two independent layers of privacy.
Free on Every Plan
Read-or-Lose is a core Arc Protocol feature — included at no extra cost on Essential, Premium, and Intelligence plans.
The Missed Call Metaphor
Imagine a phone call you didn't answer. The log remains — you know someone called. But the voice? Gone. Arc's unread messages work the same way: you see that a message arrived, but its content is irretrievably lost.
AEGIS — Arc Enhanced Guard & Integrity System
AEGIS (Arc Enhanced Guard & Integrity System) is Arc's message authentication layer built on XEdDSA digital signatures via libsignal. Every single message you send is cryptographically signed, providing three critical guarantees:
Anti-Impersonation
Even if an attacker compromises the server, they cannot forge messages in your name. Your Identity Key (X25519) is used for XEdDSA signing and never leaves your device.
Tamper Detection
Any modification to a message — even a single character — instantly invalidates the signature. Recipients can verify that every message arrived exactly as sent.
Non-Repudiation
Cryptographic proof that you authored a message. XEdDSA uses your X25519 Identity Key for EdDSA-compatible signatures — no separate Ed25519 key needed.
XEdDSA (libsignal) · X25519 Identity Key · 64-byte signatures · Per-message signing
Unlike standard messaging apps, AEGIS goes beyond encryption. While E2EE protects message content, AEGIS protects message identity — ensuring that every message truly comes from who it claims to come from. Powered by libsignal's XEdDSA implementation.
Zero Key Conversion
Arc separates X25519 (key exchange) and Ed25519 (signatures) at the type level. Unlike Signal/WhatsApp, there is no Ed25519→X25519 key conversion, minimizing the attack surface.
Comparison with 17 Major Messengers
Independent review comparing Arc V2 against 16 competitors (Signal, iMessage, WhatsApp, Telegram, LINE, Threema, Wire, Element, Session, Viber, XChat, KakaoTalk, Slack, Discord, Chatwork, Google Messages) using an 8-axis 100-point rubric.
ML-KEM-1024 Parameters
NIST FIPS 203 standardized post-quantum Key Encapsulation Mechanism.
| Algorithm | ML-KEM-1024 (via libsignal-client) |
| NIST Security Level | Level 3 (AES-192 equivalent) |
| Classical Security | 2^128 bit (X25519) |
| Quantum Security | NIST Level 3 |
| Foundation | Module Lattice (FIPS 203) |
| Public Key Size | 1,184 bytes |
| Secret Key Size | 2,400 bytes |
| Ciphertext Size | 1,088 bytes |
Compliance & Standards
🇺🇸NIST CSF 2.0
NIST framework. 6 functions for systematic cyber risk management.
🇺🇸NIST SP 800-53
Federal security controls. FedRAMP foundation.
🇺🇸FIPS 140-3
Federal cryptographic module validation. Covers ML-KEM-1024.
🇺🇸NIST SP 800-175B
Cryptographic algorithm selection guide. Based on FIPS 203.
🌐ISO/IEC 27001
International ISMS certification. B2B/B2G trust foundation.
🇪🇺GDPR
EU General Data Protection Regulation. World's highest protection standard.
🇬🇧UK Cyber Essentials+
UK government-certified cybersecurity certification.
🇬🇧NCSC Cloud Security
UK NCSC 14 Principles. Cloud security assessment standard.
Developed in compliance with all prerequisites of US NIST, EU GDPR, UK NCSC, and international ISO.
Arc Protocol: Security Whitepaper
A comprehensive technical document describing Arc's cryptographic architecture, threat model, and security guarantees. Covers PQXDH key exchange (ML-KEM-1024), Double Ratchet forward secrecy, XEdDSA per-message signatures, Sealed Sender, and BLE Mesh offline communication.
15 Sections
Complete protocol documentation
Signal Comparison
Honest feature-by-feature analysis
Threat Model
STRIDE analysis with residual risks
System Architecture Documentation
Complete technical specification of Arc V2 — covering the 5-layer architecture, E2EE pipeline, PQXDH implementation, key lifecycle, group encryption, multi-device architecture, BLE Mesh networking, and on-device AI.
15+ Technical Sections
Layer architecture, PQC implementation, encryption pipeline, data storage, and more
Bilingual (EN/JP)
Full documentation available in English and Japanese with one-click toggle
Version 3.1 — March 2026
Includes Elixir PreKey Server, Sealed Sender, Sender Keys, and PQXDH ML-KEM-1024
This document is classified as confidential and available exclusively to NDA-bound partners, investors, and authorized technical reviewers. Access requires prior approval by Atlas Associates.