- Duale AI
- Documentation
- Security
- End-to-end encryption
End-to-end encryption: scope, guarantees, and limitations
Describes which Duale AI SDK and Dashboard exchanges use end-to-end encryption, what the protection guarantees, and its limitations.
This page covers which exchanges are protected, what the protection guarantees, what stays visible to observers, and what the protection relies on.
- Protected exchanges between SDK, Dashboard, and Duale AI.
- Integrity guarantees for requests and responses in transit.
- Network metadata visible to observers.
- HTTPS dependency and forward secrecy limitations.
Summaries were generated by AI.
Duale AI adds end-to-end encryption, on top of HTTPS, to the SDK and Dashboard requests listed below, and you configure nothing. Your SDK process or browser encrypts each request before it crosses the network, and Duale AI encrypts each response. Duale AI is not a zero-knowledge service: it decrypts your data to process it, and can then send it to the destinations you configure, such as your model providers.
Which exchanges are protected
| Client and exchange | Protected between |
|---|---|
| Python SDK Task requests, live Task events, and Tool Host exchanges | Your SDK process and Duale AI |
| Python SDK Library management and document requests | Your SDK process and Duale AI |
| Dashboard Tenant operations, including identity and access administration | Your browser and Duale AI |
- Client and exchange
- Python SDK Task requests, live Task events, and Tool Host exchanges
- Protected between
- Your SDK process and Duale AI
- Client and exchange
- Python SDK Library management and document requests
- Protected between
- Your SDK process and Duale AI
- Client and exchange
- Dashboard Tenant operations, including identity and access administration
- Protected between
- Your browser and Duale AI
How data moves to and from Duale AI lists the paths that use HTTPS without this protection.
What the protection guarantees
Your client and Duale AI check each request and response for changes in transit. Your client rejects a response or a live Task event that was changed.
What stays visible
A network observer can see that a client contacts Duale AI, the endpoint, message sizes and timing, and identifiers that link the requests of one platform token. The address, headers, body, status, and Task event content stay encrypted.
What it relies on
- The protection starts over HTTPS. Your client sets up the protection over HTTPS when it gets its platform token, and your browser loads the Dashboard code over HTTPS. A party that can terminate or change that HTTPS traffic, such as a proxy in your network that inspects TLS, can read your credential and your later protected requests. Exempt Duale AI from that inspection, or treat the proxy as trusted.
- Getting a platform token has no forward secrecy. A party that records the request that gets a platform token and the requests that use that token, and later obtains a long-term private key of Duale AI, can read those requests.