> 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/soda-ai/ai-security-compliance-and-privacy.md).

# AI security, compliance & privacy

Learn what data is sent to a model provider by Soda AI features, what Soda stores, and what your organization remains responsible for.

Each Soda AI feature sends requests to a large language model (LLM) hosted by a **third-party provider**. The built-in Soda provider is **OpenAI**. With bring your own key (BYOK), the provider is the one your organization configured: OpenAI, Anthropic, Google Gemini, Azure OpenAI or Portkey. The provider's terms that apply depend on which of the two you use. This page covers:

* what the requests contain
* what Soda and the provider store
* which settings admins control
* what your organization remains responsible for when it relies on AI output

<h4 align="center">AI features covered in this page</h4>

<p align="center"><a href="https://docs.soda.io/soda-documentation/soda-ai/soda-ai-agent.md" class="button primary medium">Soda AI Agent</a><a href="https://docs.soda.io/soda-documentation/soda-ai/contract-copilot.md" class="button primary medium">Contract Copilot</a></p>

{% hint style="info" %}
[Soda MCP](https://docs.soda.io/soda-documentation/soda-ai/soda-mcp.md) and the root cause analysis (RCA) agent run inside AI tools **you choose and configure**, such as Claude Code. Soda returns data to your agent, and **your agent's provider and your agreement with that provider govern what happens to it next**.
{% endhint %}

> Learn more about [Soda AI](https://docs.soda.io/soda-documentation/soda-ai/overview.md) and its features.

***

## Model providers

Every AI feature runs through a provider. Admins manage providers in the **AI** tab of **Organization Settings**.

<figure><img src="https://1123167021-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA2PmHkO5cBgeRPdiPPOG%2Fuploads%2FoUGKJWaQiIGTRzkBd48P%2Fimage.png?alt=media&amp;token=5912013a-a9cb-4de6-882f-a8406475970e" alt=""><figcaption></figcaption></figure>

<h4 align="center">Which account receives the requests?</h4>

<table data-card-size="large" data-view="cards"><thead><tr><th align="center"></th><th></th><th></th></tr></thead><tbody><tr><td align="center"><h4>Bring your own key (BYOK)</h4></td><td><p>With <a href="https://docs.soda.io/soda-documentation/soda-ai/bring-your-own-key-byok.md">bring your own key (BYOK)</a>, requests go to <strong>your organization's own account with the provider you configured</strong>, under your agreement with that provider.</p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Enterprise plans use BYOK only.</strong></p></div></td><td><ul><li>The retention, privacy, and regional settings of your own provider account apply.</li><li>Soda stores a reference to where the API key lives and never the key itself.</li></ul></td></tr><tr><td align="center"><h4>Soda-managed AI</h4></td><td>With the built-in Soda provider, requests go to an OpenAI account that Soda operates, under Soda's agreement with OpenAI.</td><td><ul><li>Usage is included in your Soda license.</li><li>Soda chooses the models.</li></ul></td></tr></tbody></table>

<figure><img src="https://1123167021-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA2PmHkO5cBgeRPdiPPOG%2Fuploads%2FCPk4HSG5z2Zz9fJOPf7J%2FSoda%20AI%20vs%20BYOK.png?alt=media&amp;token=39efe2a2-19e6-4c5b-8719-ec20f6d22847" alt="" width="563"><figcaption><p>Soda-managed AI provider vs Bring your own key (BYOK)</p></figcaption></figure>

> Using your own supported provider account, agreement, and data-handling settings, Soda AI can fit easily within **your organization's existing security and governance** arrangements.
>
> Set up your own provider by [bringing your own key (BYOK)](https://docs.soda.io/soda-documentation/soda-ai/bring-your-own-key-byok.md).

### Data sent to the model provider

**Row-level data**, such as individual records or personal data in your datasets, **is not sent** unless an admin enables it for Contract Autopilot.

| Feature                                                                                     | Data sent to the model provider                                                                                                                                                                                                                                                                          |
| ------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [**Soda AI Agent**](https://docs.soda.io/soda-documentation/soda-ai/soda-ai-agent.md)       | <ul><li>Your messages</li><li>Files you attach to a message: images, PDFs and text files</li><li>Soda documentation content</li><li>Basic information about the Soda Cloud page you have open</li><li>Dataset schemas</li><li>Non-identifiable column-level metadata when a request needs them</li></ul> |
| [**Contract Copilot**](https://docs.soda.io/soda-documentation/soda-ai/contract-copilot.md) | <ul><li>Your request</li><li>Column names and data types</li><li>Available check attributes</li><li>The data source type</li><li>The existing contract</li></ul>                                                                                                                                         |
| **Contract Autopilot**                                                                      | <ul><li>Computed profiling metrics</li><li>The data source type</li><li>The dataset schema</li><li>A sample of up to 100 rows when <strong>Send row-level data to Soda</strong> is enabled</li></ul>                                                                                                     |

* A contract you generate from the chat runs through Contract Autopilot, so the Contract Autopilot row applies to that request.
* Contract Autopilot computes its profiling metrics from a sample of about 10,000 rows. **Only the resulting metrics go to the model provider**, not the sample.
* Failed rows stored in Diagnostics Warehouse stay in your own data warehouse and **are not available to any AI feature**.

> Learn more about [Diagnostics Warehouse](https://docs.soda.io/soda-documentation/understand/diagnostics-warehouse.md).

## Storage and retention

The chat keeps the conversation history in **your browser**, on your device. The browser stores it in IndexedDB, or in local storage when IndexedDB is not available. The files you attach are kept with the history in IndexedDB. In local storage, only the name of a file and a small preview are kept.

The browser keeps up to 50 conversations and drops a conversation 30 days after its last message. The history does not carry over to another browser or device, clearing the browser's site data deletes it, and anyone using the same browser profile can read it.

What the model provider stores depends on the provider:

* **OpenAI and Azure OpenAI.** The chat and Contract Copilot continue a conversation by referring back to responses stored with the provider. Requests and responses stay in the provider account for that provider's retention period. The same applies to Portkey with OpenAI behind the gateway.
* **Anthropic and Google Gemini.** The provider does not store the conversation for the chat. The browser sends the whole conversation again with each message, including the files attached earlier, and Soda passes it to the provider. The same applies to Portkey with Anthropic or another provider behind the gateway.

With the built-in Soda provider, the provider account is Soda's OpenAI project, covered by [OpenAI's API data policies](https://platform.openai.com/docs/guides/your-data). With BYOK, it is your own provider account, under your settings and your agreement with the provider.

{% hint style="warning" %}
**Soda AI features do not support OpenAI projects with zero data retention**. Zero data retention disables the stored responses that the chat and Contract Copilot depend on.

On Azure OpenAI, the resource stores each response of the chat. Soda has no setting that turns this storage off.
{% endhint %}

## Model training

**Soda does not use your data, metadata, prompts, or results to train or fine-tune any AI model**. With the built-in Soda provider, OpenAI does not train its models on API request data, and Soda's OpenAI project has input and output sharing with OpenAI turned off. With BYOK, your agreement with your provider and the settings of your provider account decide whether the provider can use your requests.

In some AI features, you can rate a response, and Soda records the rating in its product analytics.

## Access and human oversight

**AI features work only inside an authenticated Soda Cloud session and act with your permissions**. They cannot do anything in Soda Cloud that you could not do yourself.

Contract Autopilot publishes each generated contract as soon as its scan succeeds, with no separate approval step. Generated contracts carry a purple checkmark until someone edits them. Review them before you rely on them, especially when a contract gates a pipeline.

## Admin controls

Admins with the **Manage Organization Settings** global role control AI features from **Organization Settings**:

* In the **AI** tab, under **Soda AI**, enable or disable each AI feature. In an organization without the **AI** tab, these switches are in the **Organization** tab.
* For Contract Autopilot, enable or disable **Send row-level data to Soda**, which controls the 100-row sample.
* In the **AI** tab, add your own provider and make it the active provider.

> Contact <support@soda.io> to request access to an AI feature or setting that does not appear in your organization.

## Terms and compliance

Your agreement with Soda governs your use of Soda AI features, and nothing on this page changes that agreement. Whether AI features are available to your organization can depend on the AI terms in that agreement.

AI processing within the Soda's services detailed on this page runs under the same security controls as the rest of Soda Cloud and is covered by **Soda's SOC 2 Type 2 compliance**. Data is encrypted in transit and at rest.

> Read the [Soda Privacy Policy](https://www.soda.io/privacy-policy).

{% hint style="info" %}
**Model providers operate under their own separate security policies**. Please note **users are responsible for their arrangements with the model provider**, including the provider agreement, the data processing agreement, appropriate account settings, and provider charges.

For the built-in Soda provider, go to [OpenAI's security information](https://openai.com/security-and-privacy/). With BYOK, refer to the security information of your own provider.
{% endhint %}

## Risks and your responsibilities

**Language models are probabilistic**, so output varies between requests and can contain errors or omissions. A generated check can look plausible and still be wrong for your data. **Your organization remains responsible for checking that results suit its data and intended use**, including results used in automated workflows.

* **Keep meaningful human oversight** of any decision with legal or similarly significant effects.
* **Do not enter personal data**, **credentials**, or other **confidential information** in a prompt. Your messages and the files you attach go to the model provider.
* Soda monitors its AI features for **availability** and **technical errors**. It does not check whether each individual answer or suggestion is correct.

<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/soda-ai/ai-security-compliance-and-privacy.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.
