> For the complete documentation index, see [llms.txt](https://docs.eximee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/praca-z-komponentami-bazowymi/walidacja-wartosci-komponentow/maska-danych-sensytywnych.md).

# Sensitive data mask

Masking sensitive data is used to hide sensitive parts of information in a text field or label by replacing selected characters with the symbol `*`. This makes it possible to protect data such as the PESEL number or credit card number so that it is not fully visible on the screen. The property **Sensitive data mask** can be found in the component properties panel, in the section **Security**. After enabling masking, the specified characters of the field value will be displayed as asterisks.

<figure><img src="https://2112972046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CssJT0zIo4SJQLbSZ6l%2Fuploads%2FlQTwdJ1kdByC77geDMBI%2Fimage.png?alt=media&amp;token=2d4f1d11-65a3-43a9-a281-3da4dbdde088" alt=""><figcaption><p align="center"><em><strong>Figure 1.</strong> Sensitive data mask in a Text Field</em></p></figcaption></figure>

It should be remembered that masking sensitive data **works only for fields populated with data from another source** (e.g. a value retrieved from another field or service). If the user **enters** data into the field themselves, the mask will not be applied – the entered characters will remain fully visible. For example, if a text field *A* is automatically filled with a value copied from another field *B* (data source from another field), then on field *A* we can apply a mask to hide part of the information. However, if the user enters data in *A* manually, masking will not work.

Masking can also be applied to components of type **Label (Text)** displaying application data. In the case of a label, in addition to simply enabling masking, an additional option is available **Sensitive data masking condition** – it allows you to define a condition (logical), when met, the given label will mask its value. This makes it possible, for example, to mask the PESEL number only for certain types of users or in specific process states.

<figure><img src="https://2112972046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CssJT0zIo4SJQLbSZ6l%2Fuploads%2FjFoJSku5TbgJpkfPk4pU%2Fimage.png?alt=media&amp;token=fe36c350-8d2f-4527-a74d-1bce27dbdfae" alt=""><figcaption><p align="center"><em><strong>Figure 2.</strong> Sensitive data masking condition in the Label</em></p></figcaption></figure>

{% hint style="info" %}
Note: Do not combine Sensitive Data Mask at the same time with other formatters on the same field. In the case of text fields, it is recommended not to apply sensitive masking simultaneously with a formatter (e.g. phone number formatting) to avoid conflicts and unexpected formatting behavior.
{% endhint %}

{% hint style="info" %}
Demo application: demoTextComponents
{% 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.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/praca-z-komponentami-bazowymi/walidacja-wartosci-komponentow/maska-danych-sensytywnych.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.
