The Core Principle
Memoria Orbis was built from the ground up on the principle that your second brain is highly sensitive personal data. We do not treat security as an afterthought. It is the core foundation of our platform.
01. Isolated Key Management (KMS)
Our infrastructure splits logic and cryptography physically. We run an isolated Key Management Service (KMS) on a secure, restricted Virtual Private Server (VPS).
- The Master Key: A 256-bit cryptographically secure Master Key resides only within the memory of our KMS daemon. It is never stored alongside your database.
- Transit Handshades: All communication between our Web API and our Integration Bots relies on hardened 256-bit Hex Transit Keys, assuring only authorized nodes can package or unpack encrypted data envelopes.
02. Per-User Database Encryption (DEK)
We do not use a single "blanket" encryption key for the entire database. Instead, Memoria Orbis utilizes a sophisticated enveloped-key architecture.
- Unique Data Encryption Keys: When you first save a memory, a unique Data Encryption Key (DEK) is generated explicitly for your account.
- Zero-Knowledge Storage: Your unique DEK is encrypted by the KMS Master Key before ever touching a database row. If the database is compromised, the encrypted data remains effectively useless since the DEKs cannot be unlocked without the physical separation of the KMS.
- XChaCha20-Poly1305: All actual text data (content, thoughts, summaries, and context histories) is encrypted at-rest using the industry standard XChaCha20-Poly1305 AEAD cipher.
03. Volatile In-Memory Decryption
When you log into your Web Dashboard or query your Vault in Discord:
Your encrypted DEK is securely passed via Transit Encryption to the KMS. The KMS unwraps the key and passes a volatile, short-lived transit-encrypted version back to the executing script. Your memories are decrypted only in the active RAM of that specific worker thread. The moment the webpage renders or the message is delivered, the process exits, wiping the unencrypted memory instantly.
04. Platform Context Hygiene
You may use Memoria Orbis in Direct Messages, Private Channels, and Public Servers. We strictly adhere to the following when you run the "Save Memory" command:
- We fetch the target message and the brief surrounding context only upon explicit invocation of the Context Menu command by a verified user.
- We immediately strip non-essential platform metadata. Every message logged into your vault is stripped down to Author ID, Timestamp, and Content.
- Context is instantly pipelined into the XChaCha20-Poly1305 encryption routine before disk write.
05. Zero Third-Party Telemetry
We do not use Google Analytics. We do not use third-party user tracking pixels. We do not farm your vault data for LLM training inputs behind your back. Your notes are dark data—visible only to you when authenticated.
Last updated: March 2026