> For the complete documentation index, see [llms.txt](https://docs.ccv.brown.edu/ai-tools/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ccv.brown.edu/ai-tools/data-privacy/ask-oscar-data-handling-level-2.md).

# Ask Oscar Data Handling (Level 2)

## Ask Oscar

As of February 2025, we do not collect or store any user data for this tool, and we have no plan to change that. Any chat messages that the users provide and the output generated by AI models are not stored by the service. All AI models that we use for this service comes from Vertex AI on Google Cloud Platform and strictly follows the [Zero Retention Policy](https://docs.cloud.google.com/vertex-ai/generative-ai/docs/vertex-ai-zero-data-retention), which guarantees that your prompts (inputs) and completions (outputs), your embeddings, and your training data:

* are NOT available to other customers.
* are NOT available to Google.
* are NOT used to improve Google models and all managed models on Google Cloud.


---

# 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.ccv.brown.edu/ai-tools/data-privacy/ask-oscar-data-handling-level-2.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.