The processing of personal data is governed by GDPR rules.
In this section we provide practical advice to meet some of the obligations under the GDPR.
The form we consider here is divided into two sections: the first for collecting the contact's personal details, and the second for requesting the contact’s privacy consents (which, in the example below, purely by way of example, correspond to consent to process personal data for sending promotional updates and consent to process data for profiling purposes).
Personal information and privacy fields
The form fields used to collect personal information about the contact could be, for example:
- First name
- Last name
- Region/province
Whereas the fields useful to demonstrate that data subjects were properly informed and that the configured privacy consents were collected could be, for example:
- The link to the website’s Privacy Policy and Terms of Use
- consent to process data for sending promotional updates
- consent to process data for profiling purposes
Additionally, there is a CAPTCHA validation field:
If needed, you can link form fields to specific database fields to save preferences and contact data.
Remember that to link a form field value to a database field, simply, in the General tab of its properties, select from the Link to a database field dropdown the field where the value will be written:
Privacy policy
The full text of your Privacy Policy must be available on the same page as the form or on a page linked from it (also on an external site).
Consent for marketing communications
Contact data can be collected for different purposes.
For each purpose, you may choose to carry out the activity based on the data subject's specific consent. In that case, this means adding a dedicated checkbox (or a single-choice question, also known as a radio button) for each consent you intend to collect.
Consent to profiling
The contacts in your magnews databases are an essential asset for improving the performance of your digital marketing activities.
From target segmentation to report analysis, profiling is a constant practice across most of the activities managed in magnews.
When a contact grants or withdraws their consent to profiling, their preference can be saved to a specific shared system field, native to magnews. This field is called Disable contact profiling (ID: NOTRACK) and it is a Yes/No type field. In the contact profile you can view its value in the Settings section:
By following Profile Studio > Global database > Dashboard > Setup you will access the general database settings section, where the Privacy section is located.
The preferences in the Contact profiling section, in particular, are tied to the values of the Disabille contact profiling field.
If the value of the Disable contact profiling field is Yes, on this page you can choose between the following options:
Record the events without making them visible to the user
contact data will be used only for aggregated reports, from which it will not be possible to trace back to the contact's information and, above all, to the identity of the data subject.
In the contact profile, some tabs (e.g. Conversions, Activity, ...) will be hidden, where their aggregated data and the values of the fields for which the option Anonymise field values upon unsubscribe request has been enabled are shown (in the screenshot below, the option has been enabled for theemailfield):- Do not record events
no data related to the individual contact will be tracked, neither for profiling purposes nor as aggregated data for reports or statistics.
Configure profiling consent
Unlike a standard checkbox related to a privacy consent, the one for consent to profiling requires additional steps because it must write a value to the system field Disable contact profiling.
The ability to profile the contacts in your databases is one of the most advanced marketing features available to magnews users. The system field Disable contact profiling is not set by default; consequently, contact profiling will be active, while you can disable this feature at any time.
Therefore, if a contact/data subject says
Yes to profiling of their personal data, the value No must be written to the Disable contact profiling field, and vice versa.To achieve this result, you need to change the behavior of the form page's Save submit button.
Open the button properties and go to the Actions list:
Add a new action by clicking Add action.
As the action type select Assign expression result to a field:
Open the page where you define the rules for this action:
- Field to be valued
select the field in which to save the result of the operation, in this case: Disable contact profiling - Expression
choose the name of the form field that is the subject of the formula calculation (if it does not exist yet, you will need to create it in the relevant database) - Text area for the formula calculation
in this area you can write the formula to be evaluated
The goal of this action is to ensure that, when the contact gives their consent, if requested by you for profiling purposes, the value No is written to the Disable contact profiling field and vice versa.
Therefore, to save consent to profiling the formula will be:form.values.profiling neq 'true'
where:
- form.values.profilazione
represents the part of the formula that selects the value of the form field related to the consent request for profiling.
In particular, the value profilazione is the placeholder name of the field where the data subject grants or withdraws their consent. - neq 'true'
ensures that the Disable contact profiling field is assigned the value opposite to the one represented by the contact's choice in the checkbox.
The request to collect consent from the contact should be formulated in an affirmative/positive form. Its logic is therefore the inverse of the Disabile contact profiling field. Using the Assign expression result to a field action makes it possible to align the consent request with magnews logic.
Once you have finished configuring the operation, click Save.
When a contact/data subject grants or withdraws the consent given, for example for profiling purposes, the choice will be recorded in the database to which they belong: