> 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/en/faq/pricing/essentials-or-paid-plan-what-your-visitors-see.md). # Essentials or paid plan: what your visitors see The consent requests of Sirdata and its partners on Essentials, their absence on the paid plans, and what Sirdata does with the data in each case. The difference between Essentials and the paid plans shows in the choice interface, that is, the consent window your visitors see on your site. ## On Essentials The choice interface presents your own consent requests, and also **the consent requests of Sirdata and its partners**, for their purposes. * Those requests are the same on all sites using Essentials. * Each visitor freely accepts or refuses them. The choice is applied like any other choice expressed in the interface. * You cannot remove them, in whole or in part, even by an option. In ABconsent, the partners concerned carry the **Essentials plan** label in the partner list of your configuration, and the purposes concerned cannot be blocked. * Sirdata alone determines those requests and may supplement, withdraw or change them at any time. The current list is the one shown by the choice interface. ### What happens to the data of visitors who accept When a visitor accepts Sirdata's requests, **Sirdata processes their data on its own account**, as an independent controller. Sirdata's partners do the same, each as a controller in its own right, for the data of visitors who accept their requests. For its own processing, Sirdata informs visitors in the choice interface and in its [privacy policy](https://www.sirdata.com/en/Privacy). It keeps evidence of their consent and handles requests to exercise their rights. Each party is responsible for its own part: Sirdata for its requests and those of its partners; you for your own requests and for the settings you choose. ### What Essentials does not impose on you Essentials imposes on you no data volume, no traffic, no consent rate, no access by Sirdata to the content of your pages, and no exclusivity. It is the same plan for all clients, whatever the traffic of their sites and the consent rate of their visitors. ## On Starter, Pro and Business The choice interface **does not present** the consent requests of Sirdata and its partners. It presents the requests you have set up. The same applies with the Association offer, which includes the features of the Starter plan: see [Pricing](/en/faq/pricing.md#association-offer). ## On all plans: data processed to run the service To run the service, Sirdata processes data about your visitors on all plans, Essentials included: for example the IP address, the user agent and device information, the choices expressed and their evidence, and technical logs. It does so **as a processor, on your behalf**. That data may not be used by Sirdata for its own purposes, nor for those of any other client or supplier, including for statistical purposes. The details are in [Annex 2 of the Terms](https://www.abconsent.com/terms-and-conditions#annex-2). ## When a paid site moves back to Essentials {% hint style="warning" %} As soon as a site moves to the Essentials plan, its choice interface again presents the consent requests of Sirdata and its partners. This happens: * if you choose Essentials for that site; * when its cap is reached, until the end of the month, if your rule is "Move to Essentials", if you have chosen no rule, or if you chose the higher plan without a valid payment method; * if your payment method is missing or has expired, or if an invoice remains unpaid more than 30 days after its due date, unless you chose suspension of the service in that event; * at the end of an offered plan, if you have not subscribed to a paid plan for that site; * if Sirdata ends the Association offer of your account. {% endhint %} For your visitors not to see the requests of Sirdata and its partners, you need a paid plan: see [Can I change plans?](/en/faq/pricing/can-i-change-plans.md) --- # 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/en/faq/pricing/essentials-or-paid-plan-what-your-visitors-see.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.