Legal & Privacy Center
Absolute transparency regarding our Zero-Knowledge data handling, cryptographic protocols, and software licensing terms.
Privacy Policy
Our core directive: If we don't have your data, no one can demand it from us.
1. Data Minimization & Cryptography
- Blind Identity Protocol: We do not store your raw username, email, or phone number. We utilize client-side Argon2id hashing. The server only stores a cryptographic hash (`usernameHash`), rendering your identity mathematically irreversible to us.
- Encrypted Metadata: Your display name, bio, and avatar are symmetrically encrypted on your device. To our infrastructure, your profile is an opaque blob of ciphertext.
- E2EE Communication: All direct messages, voice notes, and file attachments are End-to-End Encrypted using the Signal Protocol (Double Ratchet).
- Zero-Knowledge Burner Sessions: These sessions operate exclusively within your browser's volatile memory (RAM). No account metadata is stored on disk or server; keys are cryptographically shredded the instant the tab is closed (Zero-Footprint).
- Secure Media Enclaves: Every image or file attachment is mutated into a randomized binary blob on your device using XChaCha20-Poly1305 symmetric encryption before cloud transmission. NYX servers act as blind storage enclaves and never possess the keys to decrypt your media.
2. Ephemeral Network Logging
To maintain network integrity and prevent DDoS/Botnet attacks, we temporarily process:
- IP addresses (irreversibly hashed upon connection).
- WebSocket connection timestamps (swept automatically from Redis).
- Encrypted offline message queues (automatically purged upon successful delivery to the recipient).
Terms of Service
Critical Disclaimer of Liability
NYX is provided "AS IS", without warranty of any kind. The maintainers shall not be held liable for any data loss, compromised keys, or service interruptions. You are solely responsible for managing your cryptographic Recovery Phrase. If you lose your password and Recovery Phrase, your account and data are permanently inaccessible. We cannot bypass our own encryption.
If you need guidance, consult our common:help .
- Trust-Tier Gating: To protect the network, unverified accounts are placed in a restricted "Sandbox Mode". Full capabilities require biometric hardware verification or cryptographic Proof-of-Work.
- Zero-Tolerance Abuse Policy: You agree not to utilize the NYX network for illicit activities, automated API abuse (botting), or distributing malware. Violations will result in immediate network bans.
Software Licensing & Enterprise
The NYX source code is proudly open-source and fiercely protected under the GNU Affero General Public License v3.0 (AGPL-3.0).
The AGPL-3.0 Constraint
If you modify the NYX codebase and allow users to interact with it over a network (e.g., hosting it as a SaaS), you are legally obligated to release your modified source code to the public. Closed-source SaaS deployments of NYX under this license are strictly prohibited and constitute copyright infringement.
Commercial Dual-Licensing
For corporations, enterprises, or startups wishing to integrate NYX into a proprietary, closed-source product without the AGPL obligations, we offer a Commercial License.
Contact Command for Enterprise PricingAI & Telemetry
NYX operates with Zero Telemetry. We do not track your clicks, screen time, or feature usage.
Smart Reply (Optional AI)
We provide an experimental "Smart Reply" feature utilizing the Google Gemini API. This feature is strictly Opt-In.
- Messages are decrypted locally before being sent to the AI.
- The NYX Server acts as a blind proxy; it does not log the prompt or the AI's response.
- Data processed by the Gemini API is ephemeral and is not used to train foundational AI models, per Google's enterprise API terms.
Security Architecture
Our cryptographic implementations are open for audit.
Signal Protocol
X3DH key agreement and Double Ratchet forward/backward secrecy via libsodium (XChaCha20-Poly1305).
WebAuthn PRF
Passwordless biometric vault decryption leveraging hardware secure enclaves (Secure Enclave/TPM).
Volatile Memory
Cryptographic keys are wiped from RAM (`sodium.memzero`) immediately after decryption cycles.
Peer-to-Peer Migration
Device migration uses an encrypted WebSocket tunnel. The server relays chunks blindly without key access.