Cryptographic Privacy

Understand how Loyal combines trusted execution environments and reproducible builds to keep data sealed.

Trusted Execution Baseline

• You require hardware that supports AMD SEV-SNP, Intel TDX, or equivalent confidential computing guarantees.
• Each enclave produces an attestation signed by the chip vendor, proving code identity and memory isolation.
• Reproducible builds ensure compiled binaries match open-source references bit-for-bit.

Never route private workloads to an agent that cannot present a fresh, verifiable attestation.

Data Lifecycle Controls

1. Session Initialization

   You generate ephemeral keys inside the enclave using its hardware RNG and negotiate encrypted channels before transmitting payloads.

2. Isolated Processing

   Inference runs entirely inside encrypted memory pages. Hypervisors, OS kernels, and co-resident workloads only observe ciphertext.

3. Secure Teardown

   On completion, the agent performs authenticated erasure on session keys and clears memory buffers before returning results.

   You receive a completion receipt confirming destruction of session state.

Side-Channel Mitigations

Timing

Agents batch cryptographic operations and pad runtimes to reduce observable differences between requests.

Memory Access

Sensitive inference paths randomize memory access patterns, limiting correlation opportunities for adversaries monitoring buses.

Traffic Analysis

Multi-hop routing and payment mixing increase the cost of linking queries to specific users or capabilities.

You should treat hardware trust as a living assumption—monitor vendor advisories and rotate hardware certificates whenever firmware updates land.