> 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/model-danych/rodo-zarzadzanie-danymi-osobowymi.md).

# GDPR in the data model

## Page purpose

This page contains a practical guide for low-coders on how to configure handling of personal data in the low-code platform's data model.

## General configuration rules

To enable the Eximee Platform to correctly handle personal data, identify the data model nodes containing such data. To do this, in the field **Data type** of a given node, select a type belonging to the personal data category in [the data inventory](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/model-danych/typy-danych-i-inwentarz-danych.md), e.g. a type describing an applicant or customer.

* Data types and their properties are defined at the deployment level, e.g. `firstName`, `lastName`, `pesel`, `birthDate`. Node fields should be selected from the list of properties of the assigned type.
* A data type may contain nested structures, e.g. a mailing address or contact channels, which belong to their own categories of personal data.
* The platform supports only fields corresponding to type properties as personal data. A field outside the schema does not belong to the inventory and is not covered by GDPR mechanisms, even if it contains personal data.
* The data type catalog is shared by all applications in a given deployment. The type structures should not be modified locally in a single application.

Instructions for setting the type and adding fields are described on the page [Data types and data inventory](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/model-danych/typy-danych-i-inwentarz-danych.md).

{% hint style="info" %}
Setting a data type on a node instead of adding individual fields without a type reduces the risk of omitting important personal data.
{% endhint %}

## Configuration example

The application handles a loan application. The borrower's data are stored in the node `borrower` with the data type **Applicant**, belonging to the category *Identification data of individuals*:

```json
{
  "key": "borrower",
  "type": "applicant",
  "items": [
    { "key": "firstName", "items": [] },
    { "key": "lastName", "items": [] },
    { "key": "pesel", "items": [] }
  ]
}
```

The platform recognizes the values of the fields `firstName`, `lastName` and `pesel` as personal data and covers them with the mechanisms described below. The subject type (natural person) is a constant value of the type, therefore it does not require adding a separate field in the model. A complete example of a model with several data types is in the section [Example](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/model-danych/typy-danych-i-inwentarz-danych.md#przyklad).

## GDPR handling mechanisms

The platform automatically applies personal data processing mechanisms. Field handling differs depending on whether the field value is stored in the data model or dynamically retrieved using providers.

| Mechanism             | Data stored in the data model                                                                                                | Dynamically retrieved data                                                                                                                                                     |
| --------------------- | ---------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **depersonalization** | performed automatically for marked personal fields                                                                           | no action                                                                                                                                                                      |
| **retention**         | the storage period for personal data is configured globally                                                                  | no action                                                                                                                                                                      |
| **audit**             | access to personal data is automatically logged by the platform, see Eximee Audit Trail                                      | access to personal data is automatically logged by the platform, see Eximee Audit Trail                                                                                        |
| **access control**    | access control is enforced by the platform; the low-coder can additionally control data permissions in the application logic | access control should be enforced by an external service; if no such mechanism exists on the service side, the low-coder can control data permissions in the application logic |
| **export**            | personal data can be exported in a secure format, see Eximee Audit Trail                                                     | data values read within the application can be exported in a secure format, see Eximee Audit Trail                                                                             |
| **deletion**          | the platform supports deleting personal data in accordance with the retention policy and GDPR requirements                   | no action                                                                                                                                                                      |

{% hint style="warning" %}
Depersonalization and deletion of personal data is performed automatically. The low-coder does not need to configure this mechanism, but must ensure the correct markings.
{% endhint %}

## Best practices

* Data types should be assigned to nodes with personal data already at the model design stage.
* Field keys should be selected from the list of type properties instead of being entered manually.
* The data type structures should not be modified locally in a single application.
* Values retrieved from external services should not be stored in the data model unless justified by application requirements.

## Related information

* [Personal data and GDPR](https://docs.eximee.com/documentation/documentation-en/wprowadzenie/rodo-zarzadzanie-danymi-osobowymi.md) - an overview of functionality and architecture.
* [Data model](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/model-danych.md) - information about the data model in the platform.
* [Data types and data inventory](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/model-danych/typy-danych-i-inwentarz-danych.md) - setting data types on model nodes and inventory categories.


---

# 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/model-danych/rodo-zarzadzanie-danymi-osobowymi.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.
