> For the complete documentation index, see [llms.txt](https://decky.gitbook.io/decky-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://decky.gitbook.io/decky-docs/account-and-security/security-at-decky.md).

# Security at Decky

Get a quick overview of how Decky protects customer data.

Decky currently provides:

* SOC 2 Type II
* Encryption in transit and at rest
* SAML single sign-on
* Role-based access controls
* Customer content is not used to train AI models
* Defined data retention and deletion controls

Data is encrypted in transit using TLS 1.2 or later and encrypted at rest using industry-standard protocols.

### Detailed security information

For Decky’s complete security overview, compliance information, and Trust Center access, visit the [Decky Security page](https://decky.ai/security).

Security teams conducting vendor reviews should use the Security page and Trust Center. Do not rely only on this Help Center article.

The Help Center provides concise answers for product users. The Security page is authoritative for detailed security, compliance, procurement, and Trust Center information.

### Related articles

* [How Decky uses your data](/decky-docs/account-and-security/how-decky-uses-your-data.md)
* [Access, permissions & SSO](/decky-docs/account-and-security/access-permissions-and-sso.md)
* [Data deletion and retention](/decky-docs/account-and-security/data-deletion-and-retention.md)
* [Security documentation & reviews](/decky-docs/account-and-security/security-documentation-and-reviews.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://decky.gitbook.io/decky-docs/account-and-security/security-at-decky.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.