GDPR Compliance

Under the GDPR, users must be informed about which personal data or personalized settings are stored when using the application. In addition, users must be given the option to customize these settings individually (privacy settings).

In the BPC frontend, ExtJS components that store their state (state) are affected. These states are stored in a StateProvider (typically LocalStorage or CookieStorage). Some states that are not strictly necessary for the application to function should, in accordance with the GDPR, only be stored if the user consents.

In the following, we will refer only to “cookies,” even if other technologies such as local storage are used for storage.

To allow the user to control this behavior, cookie_showBanner must be enabled under Core Services

A user can choose which cookie categories to allow. They can deselect all non-essential categories.

Cookie Categories

Currently, the following categories are available:

Necessary
Personalization (ID: personalization)

If additional categories (such as Marketing) are needed, please contact Support.

Assigning a Component to a Category

A prefix in the stateId can be used to define whether a component is assigned to a specific category. To do this, the prefix must match the ID of the desired category. If this is not the case, the component is always assumed to belong to the "Required" category. In the stateId, the prefix is separated from the rest of the ID by the $ character.

Example ID

stateId: "personalization$my_state_id"

Manual verification of authorized categories

If the user selection from the cookie needs to be verified manually, this can be done as follows.

Call:

Ext.state.Manager.getProvider().get("optionalCookieSettings");

Example return value:

{
  "personalization": true
}

This returns an object containing all categories to which the user has consented. Rejected categories do not need to be included in the object.

Keywords: