Compliance

Read 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.

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.
Verifiable processing	A signed receipt 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 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 for current reports and scope.

Choosing a model for regulated data

Use a confidential model 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.

How It Works

Providers & Models

Trust

Technical controls relevant to compliance

Regulatory requirements

Choosing a model for regulated data

Requesting documents

​Technical controls relevant to compliance

​Regulatory requirements

​Choosing a model for regulated data

​Requesting documents

Technical controls relevant to compliance

Regulatory requirements

Choosing a model for regulated data

Requesting documents