AI agents: the content index is at /llms.txt. Every page is also available as Markdown — send the request header Accept: text/markdown, or append .md to the page URL.
Xperience Docs
  • Community Questions & Answers (opens in a new tab)
  • Contact support (opens in a new tab)

Cookie consent

We use necessary cookies (opens in a new tab) to run our website and improve your experience while browsing. Additional cookies are only used with your consent. You may revoke your consent on the Cookies Policy (opens in a new tab) page or in your browser at any time.

Configure (opens in a new tab)
  • Documentation
    Administration interface basicsDevelopers and adminsBusiness usersChangelogGlossary
  • Guides
    Welcome to Xperience by KenticoAdministration interface basicsCustomer journeysDigital marketingConfigurationDevelopmentArchitectureUpgrade to Xperience by Kentico
  • Training
    For AdminsFor Business usersFor DevelopersFor Solution architects
  • API Examples
    ConfigurationContent managementDevelopmentDigital marketing
  • Changelog
    Documentation updatesSecurity advisories

Data protection

  • Introduction to data protection
  • Define a module that maps cookie levels to consent
  • Implement the cookie consent module
  • Create a cookie consent widget
  • Handle cookie consent requests
  • Build a tracking consent banner component
  • Handle the tracking consent banner data
  • Hide builder content from visitors who have not consented to tracking
  • Understand the Identity collectors
  • Prepare data writers
  • Collect personal data
  • Implement the data erasers
  • Learn more about Data protection

Module: Data protection

1 of 13 Pages

Introduction to data protection

This module takes a detailed look at Data protection in Xperience by Kentico, diving into complex examples.

We'll go over how to build all of the following:

  • A mapping between consents and custom cookie levels
  • A widget allowing visitors to consent to different cookie levels
  • A tracking consent banner to accept all consent levels at once
  • A Page builder section that hides its contents from visitors who have not consented to tracking
  • An identity collector to gather contacts associated with a given email
  • A data collector to collect personal information associated with provided contacts
  • A data eraser to remove all data associated with provided contacts

Some of the materials in this module are not exclusive, and may look familiar if you've already completed other modules.

Prerequisites

This module's hands-on materials require the following:

  • Familiarity with C#⁠ (opens in a new tab), .NET Core⁠ (opens in a new tab), Dependency injection⁠ (opens in a new tab), and the MVC pattern⁠ (opens in a new tab).

  • A running instance of Xperience by Kentico, preferably 29.6.1 or higher.

    Some features covered in the Training guides may not work in older versions.
  • Basic experience using Page Builder widgets.

The example presented in this Data protection series is a valid implementation of data protection for Contacts in Xperience by Kentico. (Note that it does not cover the collection and erasure of Members and their associated data.)

You can copy-paste the code samples into your own solution.

However, if you choose to do so, make sure to consult your legal team to determine whether the implementation, texts, and consent levels meet the requirements of your region and market.

Code samples

You can find a project with completed, working versions of code samples from this module and others in the finished branch⁠ (opens in a new tab) of the Training guides repository.

The main branch⁠ (opens in a new tab) of the repository provides a starting point to code along with the guides.

The code samples in this guide are for .NET 8⁠ (opens in a new tab) only.

They come from a project that uses implicit using directives⁠ (opens in a new tab). You may need to add additional using directives to your code if your project does not use this feature.

← Previous page

1 of 13

Mark complete and continue →