This help section provides reference information and guidance on using consents via the Right Consents tool. Your suggestions are welcome.
Presentation of the tool
The Fair & Smart Platform offers a tool for managing consents to the processing of personal data: "Right Consents". This offer includes:
Management of authentications and identification
Implementation of a register of consents
Time stamping of consents
The possibility to revoke a given consent
Secure storage of documents attached to a consent
The tool is based on the implementation of templates which can then be used via a collection form that can be integrated into most existing applications or websites (iframe, web redirection, paper printing).
The template for collecting consents is entirely customisable by the CLIENT. All the information linked to a template and the presentation styles can be configured via a web interface for setting up templates (Back Office).
The client remains solely responsible for compliance with the rules for collecting personal data and the consent rules in the forms integrated in the Fair & Smart Consent Management module.
Help pages
Management of consent templates
""Consent of the data subject means any freely given, specific, informed and unambiguous indication of the data subject’s wishes by which he or she, by a statement or by a clear affirmative action, signifies agreement to the processing of personal data relating to him or her." (European Data Protection Regulation Article 4, 11) ”
The consent template configuration module offers your organisation the possibility of customising as much as possible the consent collection forms displayed in the user journeys, so that they fit into your environment, while respecting the recommendations of the French Data Protection Agency (CNIL) (Integration of the name of the data controller, the processing purposes, the retention period, the name of the recipient of the data, and the contact details of the service to contact to assert rights).
This customisation includes: content, titles, graphic charter and multilingualism.
The organisation can create as many consent collection form templates as needed, depending on the customer journey.
Contents of this documentation:
The consent template creation wizard
The different fields are distributed in several sections.
Only the Footer, Other parameters, Label edition and CSS Styles sections are optional.
The other sections are necessary to comply with legal requirements and are therefore mandatory:
"Application provision";
"rocessing operations";
"Data controller";
mandatory fields are shown in bold, fields available in multilingual format are shown in italics.
"Information" section
Field name | Description | Example |
Template name | Corresponds to the name of the form template internal to your organisation. This name will not be displayed to the end user. | Marketing (test) |
Template language(s) | Corresponds to the different languages of the form (possibility to make a multilingual form). | French, English, Chinese, etc. |
Alias | Optional name for calling the consent API. It allows you to manage the replacement of one template by another, without having to modify all the calls to the template. Find out more. | |
Labels | Used to categorise consent templates in order to filter them and therefore find a template more quickly. | |
Visibility | Used to define the scope of access to the template. Find out more. | Private |
Consent email template to use | For using the "Send consent email" feature. Allows you to link a consent email template to a consent template. Find out more. (see step 2 of the tutorial by here) |
"Titles and application provisions" section
Field name | Description | Example |
Main title (Language) | Corresponds to the title of the form that will be displayed to the end user. | Collection of consent |
Title for provisions | Corresponds to the title of the insert dedicated to the application provisions. | Application provisions |
Application provisions | Corresponds to the content of the insert dedicated to the application provisions. |
"Processing operations" section
Insert name | Field name | Description | Example |
Data related to processing operations | Subtitle "Data related to processing operations" | Corresponds to the title of the section that must explain to the end user which of their data will be used for this processing. | What data do we use? |
Description of Data related to processing operations | Corresponds to the description (in accordance with the principles of the GDPR) of the data used in the context of the processing. | free text | |
Retention period | Subtitle "Retention period" | Corresponds to the title of the section that must explain to the end user how long their data will be kept after processing. | For how long do we keep data? |
The insert will appear in the form if and only if both fields of the insert are completed
Description of the retention period | Corresponds to the description (in accordance with the principles of the GDPR) of the data retention period in relation to this processing. | ||
Purpose(s) | Subtitle "Purpose" | Corresponds to the title of the section that must explain to the end user the purpose(s) for which their data will be used in the context of this processing. | What do we do with it? |
Subtitle "Sharing data with a third party" | Corresponds to the title of the corresponding section. | For this purpose, this data will be transmitted to: | |
Only displayed if data is shared with a third party (see Basis of consent), mandatory in this case. | |||
Description of purpose No. 1 | Corresponds to the description (in accordance with the principles of the GDPR) of the purpose of the use of data in relation to this processing. | ||
Basis of consent for purpose No. 1 | Marketing, Main Service, Enhanced Service, Research and Third party sharing | ||
References of associated processing operations | If the reference already exists (see "Processing operations" tab - link to be added), it can be selected, otherwise it adds a new processing operation reference. |
It is possible to add several purposes to the same processing operation, but it is also possible to add several processing operations to the same consent template.
"Data controller" section
Field name | Description | Example |
Name | Name of the data controller. | |
Telephone number | Telephone number of the data controller. | |
Email address | Email address of the data controller. | |
Address | Postal address of the data controller. | |
"Data controller" letterhead | Corresponds to an introductory section placed at the beginning of the paragraph devoted to the data controller. | |
May explain the purpose of a data controller, for example | ||
"Data controller" footer | Corresponds to a concluding section on the data controller placed at the end of the paragraph devoted to the data controller. |
If the name / telephone number / email address / address are already entered in the organisation configuration, they are pre-filled with this value.
"Validation button and footer" section
Field name | Description | Example |
Validation button label | Corresponds to the text that will be entered on the validation button in the consent form. | Submit |
Footer title | Corresponds to the footer title. | |
Footer description | Corresponds to the content of the footer. |
"Other parameters" section
Field name | Description | Example |
Page title | Corresponds to the title of the tab displayed in the browser on opening the consent form. | free text (by default, the field will be pre-filled: Collection of consent) |
Display an "Accept all" box | Checkbox to display an "Accept All" box on the form. | |
Text for the "Accept All" box | Corresponds to the wording of the box allowing to accept all processing operations of a form (whether one or more). | Accept all |
this field is only displayed if the previous checkbox is checked |
"CSS style" section
Template elements that can be customised
Section/ Element | Name of the CSS class | Position modifiable? |
Title | .fsc-global-title | |
Provisions | .fsc-dispositions.fsc-wrapper | |
Data controller | .fsc-data-controller.fsc-wrapper | |
Accept all | .fsc-accept-all.fsc-wrapper | |
Processing operations | .fsc-entries.fsc-wrapper | |
|
| |
Validate | .fsc-submit | |
Footer | .fsc-footer.fsc-wrapper |
A few examples
application of a style to the main title of the form
hide the action button on the receipt
change the colour of the "submit" button
change the order of the "data" and "purpose" fields
Lifecycle of a consent template
Viewing existing consent templates
Click Right Consents> Configuration > Consent forms;
If necessary, use the filters to refine your search;
Creating a template
Click Right Consents> Configuration > Consent forms;
Click New template;
Customise the template;
Once the name of the template has been entered, you can save it at any time by clicking "Save"
At this stage, the template is in draft form.
Modifying an existing template
Before modification, make sure that the template is in draft status: an active template can no longer be modified, in order to be able to guarantee the integrity and validity of the consents collected. The only modification allowed is the addition or removal of labels / aliases / email template / visibility. If the template needs to evolve, it will have to be duplicated to create a new template.
Access the templates by clicking Right Consents> Configuration > Consent Forms;
On the line of the template to be modified, click Ø, then Edit;
Customise the template;
To save the changes, click "Save";
Editing a template is subject to authorisation; remember to check your authorisations with your administrator
The role of labels
Labels are used to categorise consent templates in order to filter them and thus find a template more quickly.
Labels are optional.
In the template Information section, go to the Labels field;
A list with the labels already saved is proposed. Enter characters to filter the list, and then select the label;
Or enter a new label and validate the entry using the Enter key;
To delete labels from a template:
In the template Information section, click the cross to remove the label;
Labels are defined for a template and not for the template language
The role of aliases
The template alias is an optional name used when calling the Consent API.
Each alias can point to several templates, but only one of these templates can be active.
Use case: management of the replacement of one template by another, without having to modify all the calls to the template.
The alias can be changed even when the template is active.
The visibility of a template
The visibility of the template is used to define the scope of access to the template:
Public: the template can be called by any organisation;
Private: access to the template is only authorised for the organisation;
Restricted: Access is restricted to a defined list of profiles;
Visibility can be changed even when the template is active.
Customising the style
Your consent form can be given a style in line with your organisation's graphic charter.
In the
CSS Style section, define the style of the style of the different tags, insert icons, etc.;
Click Ø to preview the resulting form;
Save;