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

# Personal data and GDPR

## Introduction

Managing personal data in the context of GDPR allows the low-code platform to recognize personal data stored in a business application and automatically apply the appropriate processing rules.

In low-code applications, the data structure evolves dynamically. It is therefore crucial to clearly mark personal data at the data model level. Knowing which data is personal, the platform can handle it securely regardless of changes in the application structure.

{% hint style="info" %}
Store personal data in the data model in nodes with the set [data type](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. This facilitates automatic identification and the application of GDPR rules.
{% endhint %}

### Minimization of data stored in the application

A very important principle is **minimizing the amount of data stored in the application**. The data model should store the minimum set of data. Any data that can be retrieved from source systems should be fetched dynamically using the [providers](https://docs.eximee.com/pages/82d8ebd66bc46080bae3f8ce85a19faf08a1aefa#%C5%BAr%C3%B3d%C5%82o-danych/edycja-modelu-danych#zrodlo-danych).

{% hint style="success" %}
Minimizing the data stored in the business application directly reduces the number of personal data processing operations carried out by the Eximee Platform.
{% endhint %}

## Architecture

The Eximee Platform stores the data needed to operate applications in many components. This distributed data model supports system optimization: instead of relying on a single central database for everything, Eximee builds smaller dedicated databases optimized for specific tasks, e.g. projection databases powering the task list. Each of these places must support personal data management. They do this in different ways, shown in the table below.

| Location    | Purpose                                                                                               | How does it support GDPR?                                                                                                                                                                                                  |
| ----------- | ----------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Data model  | Handling low-code applications according to their definition.                                         | <p><strong>For known customers:</strong> Automatic data depersonalization carried out as part of integration with the organization's systems.<br><strong>For prospects:</strong> Fixed, limited data retention period.</p> |
| Eximee BPMS | Control of the flow of cases defined in BPMN notation.                                                | Fixed, limited retention period for process data.                                                                                                                                                                          |
| Formstore   | Storing documents created during form completion along with attachments.                              | Fixed, limited retention period for business application data.                                                                                                                                                             |
| Task list   | Optimal powering of task list views and functionality (displaying, searching, filtering, sorting...). | Automatic depersonalization of data carried out as part of integration with the organization's systems.                                                                                                                    |
| Case list   | Optimal powering of case list views and functionality (displaying, searching, filtering, sorting...). | Automatic depersonalization of data carried out as part of integration with the organization's systems.                                                                                                                    |
| Registry    | Optimal storage of data outside the context of a single low-code application.                         | Variable, but centrally limited, retention period for data recorded by business applications.                                                                                                                              |
| Audit Trail | Data export for any consumers inside and outside the Eximee Platform.                                 | Fixed, limited data retention period.                                                                                                                                                                                      |
| System logs | Enabling diagnostics and error handling.                                                              | A sensitive log stream containing personal data, explicitly marked, handled by mechanisms available in the organization's infrastructure.                                                                                  |

A key place in the platform architecture is the data model. This is where the low-coder defines the application's data structure and marks objects containing personal data. The other platform components read these markings and apply the appropriate processing rules. The data model is also the central place that broadcasts data value changes, in particular changes that depersonalize personal data. In this way, the platform ensures consistent application of GDPR principles throughout the entire personal data lifecycle.

### How components work together

1. The low-code developer defines the data model and sets a data type on nodes with personal data, which in the data inventory belongs to the category of personal data.
2. The platform enforces the appropriate interpretation of personal data and takes it into account in dedicated personal data processing workflows.
3. Execution modules apply appropriate personal data protection mechanisms tailored to their purpose and processing context.

{% hint style="info" %}
The low-coder does not need to implement data masking or auditing mechanisms. The Eximee Platform does it automatically.
{% endhint %}

## GDPR principles supported by the platform

The platform supports key GDPR principles thanks to the proper configuration of the data model and automatic execution mechanisms.

### Data minimization

* Store only the personal data necessary to achieve the purpose.
* Use dynamic data sources wherever data can be retrieved in real time.
* Limit the storage of personal data to fields that must be saved in the model.

### Right to erasure and portability

* The system allows personal data to be deleted upon request, in accordance with the retention policy.
* Personal data can be exported in a readable and portable format.
* Integrations with external systems help ensure compliance with GDPR processes.

### Availability and control

* The platform logs access to personal data, making it possible to verify who accessed it and when.
* Access control depends on the source of the data value:
  * data retrieved from external services - access control is handled by the external service;
  * data entered by users - access control is handled by the platform.

{% hint style="warning" %}
Data retrieved from external services should not be stored in the data model unless there are serious grounds for doing so.
{% endhint %}

## Example

Below is an example visualization of a data model with a node on which the data type **Person**has been set, along with an expanded list of its personal fields.

<figure><img src="https://2112972046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CssJT0zIo4SJQLbSZ6l%2Fuploads%2Fgit-blob-ec1e13dfa239a5ec42e4fd12b2c3d5e5272d7c92%2FtypOsobaListaPol.png?alt=media" alt="Węzeł modelu danych z typem Osoba i rozwiniętą listą jego właściwości"><figcaption><p><em><strong>Figure 1.</strong> Node with the data type Person and a list of its properties</em></p></figcaption></figure>

## Related documentation elements

* [Data Model - GDPR](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/model-danych/rodo-zarzadzanie-danymi-osobowymi.md) - detailed configuration instructions in the data model.
* [Platform architecture](https://docs.eximee.com/documentation/documentation-en/wprowadzenie/architektura-platformy.md) - general information about the platform structure and the distinction between the platform and the application.
* [Business application](https://docs.eximee.com/documentation/documentation-en/wprowadzenie/aplikacja-biznesowa.md) - definition of a business application built on the platform.


---

# 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/wprowadzenie/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.
