> For the complete documentation index, see [llms.txt](https://docs.ngsurvey.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ngsurvey.com/form-management/tasks/task-items/redact.md). # Redact ## ❓‍ What is the Redact Task ? The redact task provides a robust mechanism to establish various rules intended to selectively filter out specific types of content from the respondent's answers. By applying these rules, the task can seamlessly replace the filtered content with a substitute value of your choice, ensuring that anonymization is both effective and efficient. The primary advantage of utilizing the redact task lies in its ability to deftly remove personal and sensitive information from your datasets. This not only aids in compliance with privacy regulations but also maintains the integrity and usability of the information by preserving all pertinent and non-sensitive details. ## 🔅 Redact Task Policy Rules * **`Rule name`** name of the rule * **`Target answer`** answer of your survey that will be parse and redacted. * **`Regex patterns`** a regular expression based pattern that will be used to look up the text to redact. You can add multiple regular expressions one by line. * **`Replacement text`** text that will be used to replace the text entered by the respondent. {% hint style="info" %} Once redacted its not possible to recover the original respondent text that has been entered. {% 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.ngsurvey.com/form-management/tasks/task-items/redact.md?ask=&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.