> 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/nl/commencer/tutoriel/etape-5-implementer-les-processus-internes.md).

# Stap 5: Implementeer interne processen

Om te allen tijde een hoog niveau van bescherming van persoonsgegevens te garanderen, moet u interne procedures implementeren die ervoor zorgen dat te allen tijde rekening wordt gehouden met gegevensbescherming, rekening houdend met alle gebeurtenissen die zich tijdens de duur van een Verwerking kunnen voordoen (bijv. inbreuk op de beveiliging, beheer van rectificatie- of toegangsverzoeken, wijziging van verzamelde gegevens, verandering van dienstverlener).

Met Dastra kunt u ten minste enkele van de volgende interne processen digitaliseren en automatiseren:

* **Beheer van verzoeken om rechten uit te oefenen:**

{% content-ref url="/pages/f5JuezcTz619U9csqMLP" %}
[Rechten van betrokkenen beheren](/nl/features/gerer-les-exercices-des-droits.md)
{% endcontent-ref %}

* **Cookie toestemmingsbeheer :**

{% content-ref url="/pages/RdnmXMEwXRbZhncAky8q" %}
[Cookies](/nl/features/gerer-le-consentement-aux-cookies.md)
{% endcontent-ref %}

* **Beheer meldingen datalekken :**

{% content-ref url="/pages/3wwQj2Zv7maFzvfxBMKF" %}
[Gegevensinbreuken documenteren](/nl/features/documenter-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/nl/commencer/tutoriel/etape-5-implementer-les-processus-internes.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.