> For the complete documentation index, see [llms.txt](https://docs.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didomi.io/consent-management-platform-cmp/consent-notices/default-conditions-for-re-collecting-consent.md).

# Default conditions for re-collecting consent

By default, the banner reappears after having previously interacted with it in three cases:

1. **After 13 Months (or the generic duration you have set in the console) :** In line with GDPR recommendations, the consent banner will reappear if more than 13 months have passed since the user's last consent.
2. **When Cookies are Cleared:** The consent banner will reappear if the user clears their browser cookies, as this action deletes the stored consent information.
3. **When Adding New Vendors:** if you select the option to declare “all IAB vendors” in you consent Notice. If new vendors are introduced to your tag configuration or the IAB vendors list, the consent banner will reappear to obtain consent for these additions, keeping the user informed about all active data processors.

Moreover, you can tailor when the consent banner reappears using the Didomi Console. For instance, you can specify a grace period during which the banner won’t appear, even if new vendors are added. By default, this period is zero days, meaning the banner reappears immediately with new vendor additions unless settings are adjusted.

For granular control over banner redisplay, the Didomi SDK allows setting specific dates for consent renewal or extending the interval before the banner reappears beyond default settings.

These configurations ensure that users' consents remain current and compliant with data protection laws and your specific regulatory requirements.

You can learn more about this behavior in this [documentation](https://developers.didomi.io/cmp/web-sdk/consent-notice/notice/behavior)


---

# 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.didomi.io/consent-management-platform-cmp/consent-notices/default-conditions-for-re-collecting-consent.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.