> For the complete documentation index, see [llms.txt](https://cmp.docs.sirdata.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cmp.docs.sirdata.net/faq/legal/mecanique-de-refus-en-france.md).
# Mécanique de refus en France
La mécanique de refus est-elle obligatoire pour les utilisateurs français ?
Oui, depuis le 01 Avril 2021, une mécanique de refus est obligatoire lorsqu'il s'agit de traiter des données d'utilisateurs français. Elle peut prendre plusieurs formes et intégrer un :
* "Continuer sans accepter" ou
* "Tout refuser"
Nous recommandons d'utiliser le "Continuer sans accepter" qui autorise les finalités basées sur l'intérêt légitime car elles ne nécessitent pas un consentement.
D'autres pays européens imposent également cette mécanique. Chez Sirdata, nous poussons automatiquement cette mécanique de refus lorsque le pays le demande.
Néanmoins, si vous souhaitez forcer l'affichage de la mécanique de refus à tous vos utilisateurs, vous pouvez le faire sur votre plateforme
\> Configuration > Editer > Editer les paramètres avancés
---
# 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://cmp.docs.sirdata.net/faq/legal/mecanique-de-refus-en-france.md?ask=&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.
.png?alt=media&token=9096b670-0c57-4628-9341-adaf0a8578f9)