Introduction to Consent Management

Processing personal data is protected by data protection regulations. There are a number of lawful basis’ for processing personal data, which consent is one of.

Consent must be freely given on voluntary basis and must be specific, informed and unambiguous. For consent to be informed and specific, the data subject must be notified of the following:

• Data to be processed
• Usage of data
• Purpose of the processing operations

The consent must be bound to one or several specified purposes. The data subjects must be informed of their rights to withdraw consent anytime. The withdrawal must be as easy as giving consent.

Temenos offers Consent Management as part of the Compliance and Regulation suite of products.

Consent Product Introduction

The consent management feature offers the following functionalities:

• Creating a new consent arrangement
• Amending a consent arrangement
• Closing a consent arrangement

The Consent Product line is built using the Arrangement Architecture (AA) framework and this section provides an overview of the construction of the consent product feature.

Product Line

A new AA Product Line has been released by Temenos to assist with recording and managing consent.

AA Activities

The following AA.ACTIVITY.CLASS records are released for the Consent product line:

• CONSENT-NEW-ARRANGEMENT - creates a new consent
• CONSENT–UPDATE–CDP.CONSENT - updates an existing consent
• CONSENT–UPDATE-OFFICERS - changes account officer
• CONSENT-VIEW-ARRANGEMENT - views an existing consent
• CONSENT–CLOSE–ARRANGEMENT - closes an existing consent

Every modification to the Consent Arrangement is considered as a change activity. This activity is effected on the date mentioned in the Effective Date of the activity.

Read the AA Product Builder user guide for more information on the product construction and configuration process.

Read the AA Property Classes user guide for more information on all Property Classes.

Illustrating Model Parameters

CK module records the status of a customer’s consent and allows a fully configurable set of consent types and sub types to be recorded within the system. Currently, consent is only used in relation to the Customer Data Protection (CZ) module.

Some of the key functionalities include:

• Creating a new consent arrangement
• Amending a consent arrangement
• Closing a consent arrangement

S.No.	Parameter	Description
1	CK.CONSENT.TYPE	This application captures different consent types for which the customer consent is sought. It contains the purposes for which consent is recorded and associated with the consent sub types. Records stored are mainly used for the purpose of Customer Data Protection processing.
2	CK.SUB.TYPE	The sub type of consent is the lower level of consent that a customer can give or retract. The sub types that are defined are allowed to be attached to the respective consent type. For example, Direct Marketing can be defined as a consent type, for which there could be many sub types such as Phone, Email, SMS or Post.
3	CK.PARAMETER	This is a table which is enabled with Automated workflow for Consent Creation and Consent Blocking. Also, it has the feature which will create the consent for Both customer and Prospect as well. When this feature is not enabled the consent creation and process will be carried out manually by the bank.

Illustrating Model Products

Model Products are not applicable for this module.