> For the complete documentation index, see [llms.txt](https://eaclouddoc.eauditor.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eaclouddoc.eauditor.eu/eacloud-docs-en/features/tools/configuration/integrations/bluur/anonymization/text.md).

# Text

The integration also enables anonymization of text content without the need to upload the document. The Bluur mechanism can be used in the Text tab and when working with eA Intelligence features.

### Text anonymization

In the Text tab, enter the source text, and then start anonymization. Bluur automatically analyzes the content and anonymizes data belonging to all 32 supported categories.

The result is displayed next to the source text, enabling quick comparison of both versions. In this mode, the user does not select an anonymization scheme - the full set of categories is always applied.

<figure><img src="https://3262380731-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdzip3GyvGq5q5J3qckWN%2Fuploads%2FJFidSYhuX5OCstp8sZwT%2Fobraz%20(7).png?alt=media&amp;token=0f7ed08d-1dd9-4a35-86ca-b7e3029d3375" alt="Anonimizacja tekstu z wykorzystaniem integracji Bluur."><figcaption><p>Text anonymization with a preview of the source content and the result.</p></figcaption></figure>

<p align="center"></p>


---

# 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://eaclouddoc.eauditor.eu/eacloud-docs-en/features/tools/configuration/integrations/bluur/anonymization/text.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.
