Precision over promises.
This page states exactly what is protected, how, and what isn't — because a security claim you can't pin down is worth nothing.
What's encrypted, and with what.
The post-quantum design targets harvest-now-decrypt-later: traffic recorded today can't be decrypted by a future quantum computer, because key agreement already includes CRYSTALS-Kyber-768.
How ORION Architect fits into the encryption model
ORION Architect is a participant in your encrypted conversation — not a silent observer.
When you message ORION Architect, your message is encrypted to ORION Architect and must be decrypted on the Architect side so it can process your request, generate a response, and maintain the memory you choose to keep.
Your other conversations remain separate. ORION Architect cannot see your private chats with other people; it receives the messages that you explicitly send to it.
In short: ORION Architect can process what you ask it to process, and nothing more.
Where the encryption terminates.
Almost every serious platform encrypts. The question that separates them is where the encryption stops — and who holds the keys on the other side. The comparison below is Table 1 of Sovereign AI (R. E. Grant, August 2026).
| Privacy & security property | ORION Architect | ChatGPT · Claude · Gemini · Microsoft Copilot |
|---|---|---|
| TLS / transport security | Yes | Yes |
| Provider-excluded E2EE for protected private conversations | YES | No for ordinary consumer AI chats |
| Provider lacks private conversation decryption keys | YES | No comparable architecture |
| Post-quantum E2EE architecture | YES | No comparable ordinary consumer-chat implementation publicly documented |
| Decentralized encrypted private storage | YES | No comparable architecture publicly documented |
| Company technically unable to read protected private conversations | YES | No |
| No readable corporate conversation repository | YES | No comparable architecture |
| No monitoring of private conversation content | YES | Different architecture/policies |
| Private message excluded from push notification | YES | Different architecture |
| Sensitive notification routing information receives PQ protection | YES | No comparable architecture identified |
| Direct PWA access without mandatory App Store / Play Store distribution | YES | Web access available |
| No advertising monetization of User conversations | YES | Different business model / policies |
| No AI training on User conversations | YES | Product / settings dependent |
| User data sovereignty expressly embedded in governing philosophy | YES | Different architecture |
Methodological note: “No comparable architecture” means that no equivalent mainstream consumer implementation was identified in the providers’ publicly documented AI-chat architecture. It does not imply that these companies conduct no post-quantum research or use no advanced cryptography elsewhere within their organizations. The four services carry an identical posture in every row of the source table, so their columns are shown here as one.
Read the research: Sovereign AI — Why ORION Architect Was Deliberately Built Differently →What we know about you.
- A username and email. No phone number or names, ever.
- Encrypted content. Message and attachment ciphertext — we cannot read it.
- Account recovery is yours. A mnemonic recovery key is generated on your device and stays in your hands — it's the way back into your account.
- No third-party analytics. Zero tracking SDKs in the app. Crash reports go to our own servers, not a vendor's.
- Payments via Stripe. Card details never touch our servers.
Found something? Tell us.
Report vulnerabilities through the channels on our contact page — the fastest path is a direct message to @orionsupport inside the app. We read every report and respond to serious ones fast.