> 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/activity/rights.md).

# Data subjects rights (DSR)

Indicate which rights are applicable for this processing.

Every data subject has rights over the data that concerns them. These rights, defined in [**Articles 15 and following of the GDPR**](https://gdpr-info.eu/chapter-3/), apply depending on the lawful basis chosen for the processing or on the applicable legal regime. For example, the right to data portability only applies to processing based on consent or necessary for the performance of a contract.

For each right, you are asked to specify how it is exercised. It can be automated, for example when people exercise their right directly in an online environment. Otherwise, it is exercised manually or on demand.

The **Subject's rights** section lets you specify how data subjects can exercise their rights for this processing activity. Under the accountability principle, you must define the process that ensures data subjects can effectively exercise their rights. As a good practice, you can write a specific procedure: in this case, refer to it in this section.

## Describe the exercise of rights

1. In **Data subject rights description**, describe the general process for exercising rights, for example by indicating whether a general rights policy is in place.
2. For each right, choose how it is exercised: **None**, **Manual or on demand**, **Automatic** or **Non applicable**.
3. Once an option is selected, add details in **Give details** if needed.

The rights listed are:

* **Right of information**
* **Right of access**
* **Right of erasure**
* **Right of rectification**
* **Right of restriction**
* **Right of portability**
* **Right of opposition**
* **Right to advance directives before death**: this right, provided for by Article 85 of the French Data Protection Act, allows people to give the data controller specific instructions on the storage, erasure and communication of their personal data after their death.

Hover over the information icon next to each right to display a reminder of what it covers.

## Rights filtered according to the lawful bases

Dastra hides the rights that do not apply under the lawful bases of the purposes entered in the **Purposes** section. A right is hidden only when it does not apply to any of the purposes of the processing activity:

| Lawful basis             | Rights hidden                                               |
| ------------------------ | ----------------------------------------------------------- |
| Contract                 | Right of opposition                                         |
| Legitimate interest      | Right of portability                                        |
| Legal obligation         | Right of portability, Right of opposition, Right of erasure |
| Public interest          | Right of portability, Right of erasure                      |
| Safeguard vital interest | Right of portability, Right of opposition                   |
| Consent, Other           | None                                                        |

When some rights are hidden, a message explains it. Switch on **View the hidden user rights** to display and fill them in anyway.


---

# 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/activity/rights.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.
