> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/docs-en/platform/security/how-to-handle-gdpr-authority-requests.md).

# How to Manage Requests from the Authorities under the GDPR

The General Data Protection Regulation (GDPR) establishes the rules relating to the collection, processing and transfer of personal data within the European Economic Area.

In certain cases, competent authorities may request information about users, systems or services hosted on Plenit.

This tutorial explains how Plenit handles these requests, what each party’s role is (Plenit and the partner) and what responsibilities you need to know to ensure compliance.

***

### 1. Introduction

In this tutorial you will learn how to:

* Identify the role of Plenit and the partner within the GDPR framework.
* Understand how requests from competent authorities are handled.
* Learn about the transparency and security principles applied.
* Know what steps to follow when a request affects your clients.

**Objective:** to provide operational and legal clarity on data processing within the GDPR framework and avoid errors or misunderstandings in communication with the authorities.

### 2. Roles under the GDPR

Depending on the type of processing and the data involved, Plenit may act as:

* **Data Controller:** decides the purposes and means of processing personal data. Example: commercial data of partners or users registered in the control panel.
* **Data Processor:** processes personal data on behalf of the controller (the partner). Example: data hosted in the services that the partner provides to its clients.

### 3. Types of requests from authorities

Competent authorities (e.g., data protection authorities, law enforcement agencies, health authorities) may request:

* Identification of users (e.g., the owner of an IP address).
* Technical information about hosted servers or systems.
* Contact details of clients with HDS service, when required by the French health authority.

**Note:** all requests must be submitted through a formal demand in accordance with current legislation.

### 4. How Plenit handles these requests

The procedure depends on the role Plenit plays in each context:

* **As Data Controller:** it assesses the legality and scope of the request, informs data subjects if the law allows it, and shares only the information strictly necessary.
* **As Data Processor:** it immediately informs the partner (controller), does not share any data without its explicit instructions unless there is a direct legal obligation, and records the request and all associated communications for traceability purposes.

### 5. Special cases

**HDS clients (France)**\
French regulations may require the disclosure of contact details to the health authority, particularly the contact designated during the organization’s registration under the HDS service.\
Plenit will notify the partner in advance, unless the legislation expressly prohibits such notification.

**Requests from foreign authorities**\
They will only be handled if they are covered by European regulations or by valid international treaties.\
Any demand outside that framework will be formally rejected.

### 6. Transparency and security principles

Plenit applies the fundamental GDPR principles in all processes:

* **DPO intervention (Data Protection Officer):** all requests are reviewed and validated by them.
* **Data minimization:** only the necessary information is provided.
* **Traceability and record-keeping:** the entire process is documented, from receipt to final response.
* **Confidentiality:** exchanges are carried out securely and encrypted, in accordance with the principles of *privacy by design*.

### 7. What you must do as a partner

Your cooperation is essential to ensure compliance.

* Keep your clients’ information on the Plenit platform up to date.
* Designate a valid point of contact for privacy or compliance communications.
* Coordinate with the Plenit team if a request affects your clients or services.
* Inform your end clients when regulations require it.
* Keep an internal record of the requests and the responses handled.

**Tip:** if you manage clients with HDS services, also consult the tutorial **How to register a client in the HDS service** to learn about the specific obligations in France.

### 8. Limitation of liability

Plenit always acts in accordance with current legislation and the provisions of the GDPR.

However:

* The final responsibility for client data lies with the partner when acting as the Data Controller.
* Plenit will not be liable for penalties or claims arising from improper use of data by the partner or by third parties.
* In case of doubt, the partner must consult its legal advisors or its DPO before responding to any authority.

### 9. Contact

For any questions related to the handling of requests under the GDPR:\
📧 \**\[<dpd@plenit.com>]\**

🛈 **Note:** this channel is intended exclusively for compliance and privacy matters.

### 10. Conclusion

Proper handling of requests under the GDPR requires coordination, transparency and traceability.\
Knowing your role as a partner will allow you to act with legal certainty and maintain your clients’ compliance.\
For its part, Plenit ensures that all processes respect the principles of lawfulness, minimization and proactive accountability established by the European Regulation.


---

# 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://docs.plenit.com/docs-en/platform/security/how-to-handle-gdpr-authority-requests.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.
