What is Consenter?

This documentation explains the data protection framework underlying the Consenter cookie banner and guides you through its setup, configuration, and ongoing management in the Consenter Manager.

At the core of the Consenter cookie banner—alongside its ability to communicate with the Consenter consent agent—is its integrated risk assessment. This assessment provides the methodological foundation for a legally compliant configuration. Unlike conventional cookie banners, Consenter goes beyond the mere technical collection of consent by systematically evaluating the data protection implications of your specific settings. In combination with the consent agent, this enables genuinely informed consent. As such, Consenter represents a new state of the art that website operators must consider, particularly in light of Articles 25 and 32 GDPR (see the Risk Assessment section for details).

The Consenter Risk Assessment illustrates how the use of specific technologies on your website, as well as their configuration, affects the fundamental rights of your visitors. The results are displayed in the Consenter Manager and form the basis for transparent communication within the banner. This allows users to make an informed decision about whether the benefits of consenting are proportionate to the associated risks.

By presenting both risks and benefits transparently, you can build greater trust with your visitors compared to conventional banners—especially when technologies are configured in a privacy-friendly way. Research conducted by our team, in collaboration with other institutions, shows that this approach significantly improves user experience and increases the likelihood that users will consent to data processing.

This documentation explains how the risk assessment works, which factors are taken into account, and how to use the provided configuration guides to achieve an appropriate balance between functionality and data protection.

In principle, any member of your team can set up the Consenter cookie banner. However, depending on the configuration step, it may be advisable to involve:

• Someone who can assess the necessity of the technologies’ functionality (typically marketing).
• Someone who can evaluate legal requirements (typically data protection or legal).
• Someone responsible for technical implementation and integrations (typically IT or web development).

We will indicate at relevant points which roles should be involved.

This documentation is continuously updated to reflect legal, technical, and functional developments.