> 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/getting-started/tutorial/step-6.md).

# Step 6: Document compliance

To prove your compliance with the regulation, you must compile and consolidate the necessary documentation. The actions and documents produced at each step must be regularly reviewed and updated to ensure continuous data protection.

## Your compliance file must include in particular

| Category                                                            | Documentation                                                                                                                           |
| ------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| Documentation on your personal data processing                      | **Record of processing activities** (for controllers) or of categories of processing activities (for processors)                        |
| Documentation on your personal data processing                      | **Data protection impact assessments (DPIAs)** for processing likely to result in a high risk to 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                                                    | Templates for **obtaining the consent of data subjects**                                                                                |
| Informing people                                                    | Procedures for **exercising rights**                                                                                                    |
| Contracts that define the roles and responsibilities of the parties | **Contracts with processors**                                                                                                           |
| Contracts that define the roles and responsibilities of the parties | 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 the processing of their data is based on it                                  |

If your documentation shows that you meet the obligations laid down by the European regulation, you have completed this step.

## Centralize this documentation in Dastra

* [File management](https://doc.dastra.eu/en/features/files.md) groups the documents associated with your objects in Dastra.
* [Contracts](https://doc.dastra.eu/en/features/contracts.md) lets you declare and follow your contracts.
* [The Trust Center](https://doc.dastra.eu/en/features/trust-center.md) creates a public transparency web portal for your customers, processors and employees.


---

# 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/getting-started/tutorial/step-6.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.
