/privacy — ZERO-PII & HARDWARE HSM POLICY
Cryptographic data isolation protocols, Poseidon ZK shielding, and hardware-enforced privacy guarantees.
01. ZERO RAW-DATA RETENTION
Incoming agent telemetry streams are processed strictly in-memory within isolated WebAssembly enclaves. Raw model parameters, unhashed prompts, and customer PII are never written to persistent disk storage or stored on external cloud infrastructure.
02. POSEIDON ZK-SNARK MEMPOOL SHIELDING
Prior to Base L2 settlement, telemetry is masked using client-salted Poseidon leaf hashing and Groth16 zero-knowledge proofs (mempool_shield.ts). Competing enterprise tenants sharing the same node network cannot inspect or reconstruct raw payload parameters.
State Proof = SHA256(Poseidon_Leaf(Payload, Nonce) + Timestamp + PKI_Signature)03. FIPS 140-3 LEVEL 3/4 HSM ENCLAVES
Cryptographic keys, root certificates, and micro-toll transaction signers reside inside dedicated FIPS 140-3 Level 3/4 Hardware Security Modules. Any physical or logical tamper attempt triggers immediate zeroization of Critical Security Parameters (CSPs).
04. POST-QUANTUM DATA IN TRANSIT
Gateway mTLS enforces TLS 1.3 with Kyber-1024 hybrid post-quantum key exchange protocols across all global edge ingress nodes. Primary jurisdiction: Ontario, Canada (ON_CA).