> For the complete documentation index, see [llms.txt](https://doc.dastra.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.dastra.eu/en/features/editer-le-registre/remplir-le-questionnaire/applications.md).

# Assets

This section allows you to list the applications or software that serve as storage media for personal data.

This is where you fill in the applications, software or other that are used to **store personal data**.

*For example, if you use a CRM software, add it in this list.*

This information, **which is not mandatory for the register**, allows you to **map the application chain linking the data together**.

**The objective is to allow you to control the data carriers and to link your assets to your data catalog.**

You can thus quickly and **simply specify the types of data processed through this processing activity**.

NB: Assets are not necessarily linked to subcontractors. Indeed, it can be for example a **software installed on the server without intervention of the editor in the processing of personal data**.


---

# 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://doc.dastra.eu/en/features/editer-le-registre/remplir-le-questionnaire/applications.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.