# Privacy
Source: https://docs.chain.link/cre/privacy
Last Updated: 2026-08-05

> For the complete documentation index, see [llms.txt](/llms.txt).

CRE has two features designed to keep part of a workflow confidential from Workflow DON node operators during execution. Both run inside a secure [enclave](/cre/key-terms#enclave), a running instance of a [Trusted Execution Environment (TEE)](/cre/key-terms#tee-trusted-execution-environment), and fetch secrets from the [Vault DON](/cre/key-terms#vault-don) instead of the regular Workflow DON runtime.

## Privacy features

- **[Confidential Workflows](/cre/concepts/confidential-workflows)** (private beta): Runs a handler's full callback logic inside a TEE, for workflows where more than a single request is intended to remain confidential: risk thresholds, proprietary scoring, multi-step reasoning over sensitive inputs.
- **[Confidential HTTP](/cre/capabilities/confidential-http)**: Executes a single outbound HTTP request inside a TEE, with secrets injected via templates and an optional encrypted response.

## Guides

- **[Making a Workflow Confidential](/cre/guides/workflow/using-confidential-workflows/making-workflow-confidential)**: Step-by-step guide to registering a TEE handler.
- **[Making Confidential Requests](/cre/guides/workflow/using-confidential-http-client/making-requests)**: Step-by-step guide to making a single confidential HTTP request.

## Learn more

- **[Requesting Confidential Workflows Access](/cre/account/confidential-workflows-access)**: How to get enrolled in the private beta.
- **[Key Terms](/cre/key-terms#confidential-workflow-or-confidential-execution)**: Definitions for TEE, enclave, Vault DON, and confidential execution.