Creating consents

In Kentico, consents are records used to inform website visitors about the means of collecting and manipulating their personal data by the system, site administrators, marketers and anyone else who has access to said data, including third-parties to whom this data is forwarded.

You can use consents to comply with the requirements of the GDPR and other personal data regulations.

Whenever any personal data of a visitor is obtained, it is necessary to have a consent agreement from the visitor to legally process this data. This includes tracking of contacts and their activities on the live site. Every consent agreement of a visitor is directly connected to a corresponding contact. Deleting contacts from the system therefore also causes deletion of the contact’s consent agreements.

This page describes how to define consents and view the older, archived versions of consent texts. 

Creating consents

1. Open the Data protection application and switch to the Consents tab.

2. Click New consent.

3. Type a Display name and click Save.

4. On the Consent text tab, use the provided text areas to compose the content of the consent:

   • Short text – a brief explanation of the consent’s content for public users. The short text is shown to visitors when presenting an option to give consent agreements.
   • Full text – contains the full content of the consent. The full text content can be made available to everyone upon request, preferably through a dedicated privacy policy page.

5. When you are finished with the work, click Save (or Save this language version if multiple cultures are assigned to the current site).

6. (If multiple website cultures are present) Switch between cultures using the Language of consent selector and write the consent texts in the given languages. The selector lists all cultures available for the current site.
   

   Handling of untranslated consents

   If a consent is not available for the culture selected by a visitor, the website’s default culture is used instead.

The system saves the consent and its language versions. You can further modify the consent by editing () it from the Consents tab of the Data protection application.

Learn how to include consents on your website in:

• Working with consents (when using the Portal Engine development model)
• Working with consents on MVC sites (when using the MVC development model).

Viewing consent agreements

After you create consents and make it possible for visitors to give consent agreements on your website, you can view a list of agreements for individual consents:

1. Open the Data protection application and switch to the Consents tab.
2. Edit () the consent for which you want to view consent agreements.
3. Switch to the Consent agreements tab.

The tab displays a list of all visitors who have given an agreement for the selected consent. The list includes visitors who have given an agreement for an older, archived version of the consent, but not those who have revoked the consent at a later point.

The visitor information is based on the contact data available in the system.

Viewing archived consents

When a visitor gives a consent agreement, it is based on the exact text of the consent at the given time. However, consent texts may change at a later time.

To keep track of the exact consent versions for which visitors have given agreements, the system performs automatic consent archiving. When a consent with at least one agreement is modified and saved, an archived version of the original consent text is created. Every archived consent is represented by a unique hash string, and consists of all language versions created for the given consent.

To see the archived versions of a specific consent and all of its language versions:

1. Open the Data protection application.
2. Switch to the Consents tab.
3. Edit () the given consent.
4. Switch to the Consent archive tab.

The tab displays all archived versions of the selected consent for which at least one visitor has given an agreement. You can view () the short and full text of the consent language versions.