> ## Documentation Index
> Fetch the complete documentation index at: https://docs.redpill.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Compliance

> How the confidential computing architecture supports common compliance requirements, and how to request reports.

The platform's architecture is built for workloads with strict data-handling requirements. This page
explains what the technical controls give you and how to request compliance documentation. For
reports or a security review, contact [support@redpill.ai](mailto:support@redpill.ai).

<Note>
  Read [Trust boundary](/confidential-ai/trust-boundary) first. The gateway is attested and does not
  retain request bodies, but plaintext is visible to the attested gateway after TLS or E2EE decryption.
  Compliance posture depends on which model you use: confidential or routed.
</Note>

## Technical controls relevant to compliance

| Control                      | How the platform provides it                                                                                                                                                                                   |
| ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Data isolation               | Inference runs in a TEE (Intel TDX). The gateway is attested with a hardware quote.                                                                                                                            |
| No body retention            | The gateway stores hashes in receipts, not request or response bodies.                                                                                                                                         |
| Upstream zero data retention | `provider: {"zdr": true}` restricts routing to providers that do not retain prompt or completion content. Enforced fail-closed, including on failover. See [Zero data retention](/guides/zero-data-retention). |
| Verifiable processing        | A signed [receipt](/confidential-ai/receipts) binds each request and response to the attested workload.                                                                                                        |
| Confidential upstreams       | For a confidential response, the upstream enclave is verified and the channel bound before forwarding, confirmed by the receipt's `upstream.verified` event.                                                   |
| Encryption in transit        | TLS for all connections, with optional [E2EE](/confidential-ai/e2e-encryption) field-level encryption.                                                                                                         |

## Regulatory requirements

| Requirement               | How the platform helps                                                                                             |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------ |
| Data minimization (GDPR)  | No request or response body retention by default. Request `zdr` to extend the constraint to the upstream provider. |
| Storage limitation (GDPR) | Zero-data-retention providers do not keep prompt or completion content after serving a request.                    |
| Confidential processing   | TEE isolation with attestation and per-response receipts.                                                          |
| Auditability              | Verifiable attestation and signed receipts you can check independently.                                            |

The platform supports Data Processing Agreements (DPA) and, for healthcare workloads, Business Associate
Agreements (BAA). Certification status (for example SOC 2 and HIPAA) changes over time; contact
[support@redpill.ai](mailto:support@redpill.ai) for current reports and scope.

## Choosing a model for regulated data

* Use a [confidential model](/confidential-ai/confidential-models) when the upstream that runs the
  model must be attested and the prompt must not reach a non-attested third party.
* A routed model sends your prompt to a third-party provider that is not attested. Confirm that
  provider's terms meet your requirements before using it for regulated data.

## Requesting documents

For enterprise customers and prospects, the platform provides security documentation, a DPA, and (where
applicable) a BAA. Contact [support@redpill.ai](mailto:support@redpill.ai).