> For the complete documentation index, see [llms.txt](https://docs.ox.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ox.security/fix-with-ox/ai-remediation/ai-privacy.md).

# AI Privacy

**Disclaimer:** By using AI Remediation for AppSec security issue analysis, you acknowledge that code related to the issue will be sent for evaluation. OX Security cannot guarantee that no sensitive information is included in the submitted findings.

Before implementing AI-generated recommendations:

* Validate the generated advice with your security team.
* Assess the recommendation’s impact on your codebase and security posture.
* Apply professional judgment when deciding whether to implement the advice.

OX Security is not responsible for any consequences resulting from the use of the generated advice.

Azure OpenAI will not use any OX or OX customer data for training or improving its models.


---

# 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://docs.ox.security/fix-with-ox/ai-remediation/ai-privacy.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.