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

# Security

> How Ordyn handles access and data.

Full documentation, reports, and the data-flow diagram are at [trust.ordyn.dev](/trust).

## Compliance

SOC 2 Type II and HIPAA compliant.

## Access

* Access to observability tools, cloud logs, and databases is **read-only**. Ordyn never modifies your monitoring configuration, log groups, or data. The one exception is Auto Monitors, which needs permission to create and edit the monitors it owns. You grant that separately during setup.
* On AWS, the setup command also attaches the AWS managed `ViewOnlyAccess` policy and read-only infrastructure actions, so Ordyn can list your resources, read their configuration, and see recent infrastructure changes. AWS configuration responses can include sensitive values; Ordyn redacts environment variables and known secret-bearing fields before saving resource snapshots. [AWS CloudWatch](/integrations/aws-cloudwatch#permissions) lists every policy and action.
* Ordyn's GitHub App reads code, posts pull request reviews, and opens pull requests on repositories you enable. It does not push to protected branches or merge.
* Database connections use read-only roles you create. Ordyn provides the setup SQL.

## Data

* Encrypted in transit and at rest.
* Logically isolated per customer.
* **Never used to train models.**
* Code is read during analysis and indexed for search. Credentials are stored encrypted and are never shown after entry.

## Enterprise

SSO/SAML, role-based access control, and deployment options are available on Enterprise plans. Contact [help@ordyn.dev](mailto:help@ordyn.dev).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.