> 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/ropa/processor.md).

# "Data processor" record

Learn how to use Dastra's "Data processor" record.

## Introduction

Article 30 of the GDPR sets out specific obligations for the personal *data controller record* and the *data* *processor record*. If your organization acts as both a processor and a controller, your record must therefore clearly distinguish between the two categories of activities.

**In practice, in this case, the CNIL recommends that you keep 2 records:**

1. one for the processing of personal data for which you yourself are responsible,
2. another for the processing operations that you carry out, as a data processor, on behalf of your clients.

The rest of this page deals only with the "Data processor" record.

## The "Data processor" record

Each data processor is required to keep a less extensive record.

This record contains:

* the **contact details of the data processor**, its representative, if applicable, and its DPO
* the **contact details of all data controllers on whose behalf the data processor acts** (usually the clients)
* the **categories of data** processed
* the **recipients**
* the **transfers** outside the EEA
* the **security measures**

In Dastra, a processing activity created as a data processor is documented in 12 sections: **General**, **Parties involved**, **Purposes**, **Assets**, **Datasets**, **Controllers**, **Data subject**, **Subject's rights**, **Recipients**, **Measures**, **Documentation** and **Summary**.

Compared with a data controller activity, the **Controllers** section lets you declare the data controllers on whose behalf you act (usually your clients), and there is no **Impact assessment** section.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-bfea81715ee76f10104f677f68f9a2fe89280041%2Fropa-processor-1.png?alt=media" alt="Section navigation of a data processor processing activity"><figcaption><p>The different sections of a "data processor" processing activity in Dastra</p></figcaption></figure>

## The Controllers section

The **Controllers** section lists the data controllers on whose behalf you process the data, usually your clients. You must sign a contract with each of them that includes the clauses set out in Article 28 of the GDPR.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-6913209eef4d15563a148e0fec7e6628e900f777%2Fropa-processor-2.png?alt=media" alt="Controllers section of a data processor processing activity with the Add controller button"><figcaption><p>The Controllers section of a data processor activity</p></figcaption></figure>

To declare a controller:

1. Click **Add controller**.
2. Choose **Directory** to select a stakeholder of your repository, or **Select an organizational unit**.
3. Optionally, describe your operations in **Describe how data are processed**.
4. If the controller also receives the data, turn on **Is client/data controller recipient ?**. Under **What data does he have access to?**, choose **Access to all data (default)** or **Access to certain data sets** and tick the datasets concerned.
5. Confirm.

To add several controllers at once, click the arrow on the right of **Add controller**, then choose **Add actors in batch** to select several stakeholders, or **Add org. units in batch** to select several organizational units.

The menu at the end of each row lets you **Edit** the controller, **Edit stakeholder** or **Delete** it. When your workspace uses the Contracts module, **Generate DPA** creates the data processing agreement of the controller. To delete several controllers, tick them and click **Delete**.

To send a controller only its own data, use the **Export for customer/data controller** option of the export window: the file then excludes the other controllers (see [Export / import the record](https://doc.dastra.eu/en/features/ropa/export-import.md)).

***

{% hint style="info" %}
You can change the type of processing activity (from one created as a data controller to one created as a processor, and vice versa)\
[The procedure is available here](https://doc.dastra.eu/en/features/ropa/faq.md#how-can-i-change-my-type-of-processing-activity-from-one-created-as-a-data-controller-to-one-created)

When you switch a processor activity back to a data controller activity, the clients linked to it are removed.
{% endhint %}

## For more information

{% content-ref url="/pages/529ywLjSqAr94cjpWWxO" %}
["Data controller" record](https://doc.dastra.eu/en/features/ropa/controller.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/features/ropa/processor.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.
