> 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-6-document-compliance.md).

# Step 6: Document compliance

To prove your compliance with the regulations, you need to compile and consolidate the necessary documentation. The actions and documents carried out at each stage must be regularly reviewed and updated to ensure ongoing data protection.

**Your application must include the following information:**

| Category                                                        | Documentation                                                                                                                                      |
| --------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| DOCUMENTATION ON YOUR PERSONAL DATA PROCESSING                  | **Record of processing activities** (for data controllers) or categories of processing activities (for data processors)                            |
| DOCUMENTATION ON YOUR PERSONAL DATA PROCESSING                  | **Data Protection Impact Assessments (DPIAs)** for processing operations likely to generate high risks for the rights and freedoms of individuals. |
| DOCUMENTATION ON YOUR PERSONAL DATA PROCESSING                  | **The framework for data transfers** outside the European Union (in particular, standard contractual clauses, BCRs and certifications)             |
| INFORMING PEOPLE                                                | **Information notices**                                                                                                                            |
| INFORMING PEOPLE                                                | Models for **obtaining the consent of the persons concerned**                                                                                      |
| INFORMING PEOPLE                                                | Procedures for **exercising rights**                                                                                                               |
| CONTRACTS THAT DEFINE THE ROLES AND RESPONSIBILITIES OF PLAYERS | **Contracts with subcontractors**                                                                                                                  |
| CONTRACTS THAT DEFINE THE ROLES AND RESPONSIBILITIES OF PLAYERS | Internal procedures **in the event of a data breach**                                                                                              |
| THE RIGHTS OF INDIVIDUALS AND THE EXERCISE OF THEIR RIGHTS      | Proof that data subjects **have given their consent** when their data is processed on this basis.                                                  |

If your documentation shows that you meet the obligations laid down by the European regulation, then you've passed this stage. Congratulations!


---

# 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-6-document-compliance.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.