> 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/commencer/tutorial/step-5-implement-internal-processes.md).

# Step 5: Implement internal processes

To ensure a high level of personal data protection at all times, you must put in place internal procedures to guarantee that data protection is taken into account at all times, taking into account all events that may occur during the life of a processing operation (e.g. security breach, management of rectification or access requests, modification of collected data, change of service provider).

Dastra enables you to digitize and automate at least some of the following internal processes:

* **Managing requests to exercise rights:**

{% content-ref url="/pages/-M31ydu73LeeHMZQ4ECM" %}
[Data subject right request](/en/features/gerer-les-exercices-des-droits.md)
{% endcontent-ref %}

* **Managing consent to cookies:**

{% content-ref url="/pages/-M31ynfUgMD579kUk9LB" %}
[Manage cookies consent](/en/features/gerer-le-consentement-aux-cookies.md)
{% endcontent-ref %}

* **Managing data breach notifications:**

{% content-ref url="/pages/-M31zD6jKngOCW1hmuCc" %}
[Manage data breach notifications](/en/features/notifier-les-violations-de-donnees.md)
{% endcontent-ref %}


---

# 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/commencer/tutorial/step-5-implement-internal-processes.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.