Cryptographic Risk Disclosure

1. Zero-Trust & Local-First Architectural Notice

C-LabZero operates under a strict local-first, zero-trust engineering model. Cryptographic keys, encrypted vaults, database states, and local application parameters reside exclusively on physical hardware you own and control.

No Key Escrow or Recovery: We do not maintain central SaaS servers, backdoors, or key escrow mechanisms. We cannot recover lost private keys, passphrases, seed phrases, or master passwords.

Irreversible Data Loss: If you lose your keys or access credentials, any data or assets encrypted under those keys will become permanently unrecoverable.

2. Post-Quantum & Algorithmic Evolution Risks

While C-LabZero applications implement modern post-quantum cryptographic primitives (including ML-KEM and ML-DSA parameters), you acknowledge and accept the following operational realities:

Evolving Standards: Post-quantum cryptography is an actively evolving field. Algorithms, key sizes, and mathematical assumptions are subject to ongoing global research, cryptanalysis, and standardization updates.

Implementation & Side-Channel Vectors: No software execution environment is guaranteed to be completely immune to side-channel analysis, physical memory extraction, or low-level hardware vulnerability exploitation.

No Immutable Future-Proofing: Deploying post-quantum primitives mitigates quantum decryption threats but does not eliminate risk vectors originating from compromised underlying host platforms or operating systems.

3. Host Environment & Physical Hardware Responsibility

You are solely responsible for securing the execution environment hosting C-LabZero binaries, modules, or network interfaces.

Malware & Memory Interception: Key generation, encryption, and decryption occur in your host system’s memory. If your host OS is compromised by keyloggers, rootkits, or unauthorized process inspection, your key material may be exposed.

Hardware Health & Storage Failure: Local-first architectures rely on your storage media. You are responsible for executing secure, encrypted off-site backups of local vault configurations.

SPI / TPM Hardware Extensions: When pairing local applications with hardware security modules (e.g., TPM 2.0 or secure elements via SPI/bus connections), you are responsible for physical access security, bus monitoring risks, and proper initialization parameters.

4. Mesh Networking & Peer-to-Peer Transport

When operating C-LabZero applications across local or distributed mesh networks:

Endpoint Verification: You are responsible for verifying peer identities and license bindings prior to establishing secure channels or routing data over untrusted networks.

Network Boundary Controls: You must ensure that local firewall configurations, routing rules, and isolated container parameters align with your organizational security policies.

5. Regulatory, Compliance & Import/Export Restrictions

Jurisdictional Laws: Encryption technology is subject to varying legal restrictions, import duties, and deployment regulations worldwide.

User Compliance Obligation: You are responsible for ensuring that downloading, compiling, executing, or distributing C-LabZero cryptographic software complies with the local laws, trade regulations, and statutory licensing frameworks of your operating jurisdiction.

6. Limitation of Liability

To the fullest extent permitted under English law, C-LabZero, its developers, and contributors explicitly disclaim all liability for any direct, indirect, special, or consequential damages resulting from:

Loss or compromise of cryptographic keys, access tokens, or encrypted vault data.

Incomplete or improper local deployment configurations.

Software disruptions or hardware failures occurring during cryptographic execution.

7. Contact Information

For technical security questions or statutory verification inquiries:

Email: neo@c-labzero.live