Security you can
check the math on.
No secret sauce, no trust-us clauses. This page is the whole system: run the protocol, break the alternatives, read the exact numbers.
Every call gets its own key.
Every key dies with the call.
That's the entire idea: simple to say, brutally hard to build. Here is a call, from dial to hang-up.
A key is born
The moment you dial, a quantum random generator inside the phone creates a key that has never existed before.
Your call is sealed
That key wraps your voice end-to-end. It never leaves the phone’s hardware vault. Not even we can read it.
You just talk
On the line, your words. In the air, pure noise. Anyone listening in captures nothing but static.
The key burns
You hang up. The key is destroyed on both ends. Without it, a recording of the call stays sealed.
Eight steps.
Under one second. Zero rituals.
Don't take our word for the sequence. Run it. This is everything that happens between “dial” and “hello.”
Initiate
You dial normally. Nothing to launch, nothing to remember.
Session ID
A unique identifier is minted for this call and no other.
Key generation
The quantum RNG produces a key that has never existed.
Distribution
The key travels encrypted to both devices, and nowhere else.
Terminal sync
Each phone seals its copy inside the hardware enclave.
State exchange
Both ends confirm they hold the same secret.
Channel verify
QKD physics confirms nobody touched the exchange.
You talk
AES-256Q voice begins. At hang-up, the key is destroyed.
Three generations of defense.
Only one survives a quantum computer.
“Harvest now, decrypt later” is already happening. Intercepted traffic is stockpiled for the day quantum computers can open it. Drag the years forward and watch what holds.
The exact numbers.
For security engineers and compliance teams. For everyone else, click any row and it explains itself in plain language.
Want the long version?
The technical whitepaper covers the full protocol, threat analysis, and certification posture.