> For the complete documentation index, see [llms.txt](https://docs.yoplanning.support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yoplanning.support/en/yoplanning-academy/yoplanning-au-quotidien/communication-client/opt-in-et-les-regles-demailing-en-europe.md). # Opt-in and Emailing Rules in Europe Opt-in is a required practice in email marketing in Europe, stipulating that a user must give explicit consent before receiving advertising or commercial emails. Here's how it works and what it means for our team: #### Express Consent * **Simple opt-in:** The user must actively check a box or fill out a form to subscribe to the mailing list. * **Double opt-in:** After registering, the user receives a confirmation email to verify their consent. Only after this confirmation is the email address added to the mailing list. #### Emailing Rules in Europe (GDPR) In Europe, the General Data Protection Regulation (GDPR) sets strict guidelines for opt-in and email marketing: * **Transparency:** Why the data is being collected and how it will be used must be clearly explained at the time of collection. * **Right of access and deletion:** Users have the right to access their personal data and request its deletion. * **Security:** Collected data must be secured against unauthorized access. ### Implications for the team * Ensure all subscription forms are configured for clear and compliant opt-in. * Maintain proof of subscriber consent. (Yoplanning does this for you when the customer purchases online on the reservation module) * Set up an easy process for unsubscribes. * Protect subscriber data and respect their privacy in accordance with the GDPR. Adopting these practices not only ensures our compliance with European laws, but also strengthens the trust of our customers by showing that we value and protect their privacy. --- # 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.yoplanning.support/en/yoplanning-academy/yoplanning-au-quotidien/communication-client/opt-in-et-les-regles-demailing-en-europe.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.