> For the complete documentation index, see [llms.txt](https://docs.currents.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.currents.dev/resources/data-privacy.md).

# Data Privacy

- [Access to Customer Data](https://docs.currents.dev/resources/data-privacy/access-to-customer-data.md): Overview of Customer Data that Currents collects during its execution
- [Data Redaction](https://docs.currents.dev/resources/data-privacy/data-redaction.md): Learn how Currents automatically detects and removes sensitive information such as tokens, passwords, and API keys from trace files to ensure your data remains secure and compliant.
- [Bring Your Own Storage](https://docs.currents.dev/resources/data-privacy/byos.md): Learn how Currents can be integrated to your own S3-compatible object storage.
- [Data Retention](https://docs.currents.dev/resources/data-privacy/data-retention.md): Retention periods for different types of data collected by Currents
- [Cloud Endpoints](https://docs.currents.dev/resources/data-privacy/cloud-endpoints.md): A list of internet-facing Currents services and endpoints


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.currents.dev/resources/data-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 `build a script that syncs our docs to a CMS` 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.