> For the complete documentation index, see [llms.txt](https://docs.aqua-cloud.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aqua-cloud.io/documentation/capture/capturing-with-video/option-to-pause-resume-while-capturing-the-video/masking-sensitive-information-while-capturing.md).

# Masking sensitive information while capturing

Learn how to mask sensitive information in videos during screen capture, ensuring privacy and compliance throughout your recording process.

This articlet explains how to use the 'Masked Inputs' feature in Capture, allowing you to decide which fields should be masked in video recordings or captured events. This feature is useful for hiding sensitive information, ensuring data privacy during recordings or event captures.

To set up masked fields, click on the Capture extension and then on the settings icon.

<figure><img src="https://3920520305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyZbW8vbNs5hz8x57emJJ%2Fuploads%2F1maAoZAbVCIXaY2rPtUG%2Fimage.png?alt=media&amp;token=8390329f-8dfa-45f2-aa80-2c8b139bb055" alt=""><figcaption></figcaption></figure>


---

# 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.aqua-cloud.io/documentation/capture/capturing-with-video/option-to-pause-resume-while-capturing-the-video/masking-sensitive-information-while-capturing.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.
