Compliance
Model Vault Encrypted is designed to help regulated organizations adopt AI while meeting their compliance obligations. This page summarizes how its guarantees map to common requirements. It is not legal advice; evaluate the controls against your own obligations.
How the guarantees support compliance
Most data-protection regimes care about who can access sensitive data and whether you can demonstrate that controls are actually in place. Model Vault Encrypted addresses both:
- Confidentiality enforced by hardware: data is protected in transit, at rest, and in use, and is not accessible to Cohere, the cloud provider, or the network. This is enforced by the trusted execution environment and made verifiable through attestation. See the Security Model.
- Dedicated infrastructure: your vault’s infrastructure isn’t shared with, and is isolated from, other customers.
- Zero Data Retention: ZDR is on by default, so prompts and responses are processed for inference but not retained. See Encryption & Key Management.
- Verifiable, not just contractual: remote attestation gives you cryptographic proof of the exact environment handling your data, which you can use as evidence rather than relying on a provider’s assurances.
Regulatory frameworks
The properties above map onto common frameworks:
- GDPR: hardware-enforced access restrictions limit processing to the attested environment, supporting data-minimization and confidentiality principles. Region selection supports data-residency requirements; Encrypted Vaults currently run in the United States, with the European Union and Canada coming soon. See Regions.
- SOC 2: dedicated infrastructure, encryption throughout the lifecycle, and verifiable attestation map to the security and confidentiality trust-services criteria.
Because the design removes Cohere and the cloud provider from the set of parties that can access your data, it directly addresses the third-party-access concerns that often block sensitive workloads from hosted AI.
Verifiable evidence and audit logging
Attestation produces a signed record you can use for audit purposes:
- Each attestation token identifies the environment, the policy that was evaluated, and when verification occurred.
- On AMD SEV-SNP, the token is created by the Cohere OHTTP proxy, which runs in your environment and whose source code is open for inspection; the only external service involved is NVIDIA’s, for the GPU. The token records the proxy’s own check, but it is signed by a temporary key inside the proxy, so a third party cannot verify it afterwards.
- On Intel TDX, the token is signed by Intel Trust Authority, so it gives a third party a verifiable trail of the environment serving your requests.
- On Intel TDX, for the strongest assurance, Intel’s Faithful Verification service lets you confirm that the attestation service itself ran genuine, unmodified code. See Remote Attestation.