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

# Security, licensing & compliance

Use these pages to answer security, privacy, and procurement questions about Soda.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Soda Trust Center</strong></td><td>Review Soda's security and compliance practices, policies, and certifications.</td><td><a href="https://trust.soda.io/">https://trust.soda.io/</a></td></tr><tr><td><strong>Data flows between Soda &#x26; user</strong></td><td>Follow each step, from the runner picking up instructions to results reaching Soda Cloud, for contract verification and metric monitoring with a self-hosted runner.</td><td><a href="https://docs.soda.io/soda-documentation/govern/security-licensing-and-compliance/data-flows-between-soda-and-user.md">Data flows between Soda &amp; user</a></td></tr><tr><td><strong>AI security, compliance &#x26; privacy</strong></td><td>See what Soda AI features send to the model provider, what Soda and the provider store, and which settings admins control.</td><td><a href="https://docs.soda.io/soda-documentation/soda-ai/ai-security-compliance-and-privacy.md">AI security, compliance &amp; privacy</a></td></tr></tbody></table>

## Licensing

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h4>Licensing &#x26; documentation access</h4></td><td>Find out how to get full access to the documentation.</td><td><a href="https://docs.soda.io/soda-documentation/govern/security-licensing-and-compliance/documentation-access-and-licensing.md">Licensing &amp; documentation access</a></td></tr><tr><td><h4>Soda licenses</h4></td><td>Learn how dataset-based licensing works and how Soda counts your datasets.</td><td><a href="broken://pages/nEeVAUUx8V57By8ALc2b">Broken link</a></td></tr></tbody></table>

## Access control

Control who can see and change what in Soda Cloud.

<p align="center"><a href="https://docs.soda.io/soda-documentation/govern/organization-and-admin-settings/global-and-dataset-roles.md" class="button primary">Global and dataset roles</a><a href="https://docs.soda.io/soda-documentation/govern/organization-and-admin-settings/user-and-user-group-management-with-sso.md" class="button primary">User and user group management with SSO</a><a href="https://docs.soda.io/soda-documentation/govern/organization-and-admin-settings/user-provisioning-with-scim.md" class="button primary">User provisioning with SCIM</a><a href="https://docs.soda.io/soda-documentation/govern/organization-and-admin-settings/service-accounts.md" class="button primary">Service accounts</a></p>

> For a step-by-step setup that keeps sensitive data inside your network, see [Manage sensitive data](https://docs.soda.io/guides-and-tutorials/data-governance/manage-sensitive-data.md).

<br>

***

{% hint style="info" %}
You are **not logged in to Soda** and are viewing the default public documentation.

Learn more about [Licensing & documentation access](https://docs.soda.io/soda-documentation/govern/security-licensing-and-compliance/documentation-access-and-licensing.md) or <a href="https://docs.soda.io/~gitbook/auth/login" class="button primary small">Log in to Soda Cloud</a>.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.soda.io/soda-documentation/govern/security-licensing-and-compliance.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
