...
The result of the anonymisation process is summarised in table below:
| Group lead has created contact | Contact has logged in to his account since he received the consent email | Group lead has booked or bought tickets on behalf of group member | Result |
|---|---|---|---|
| No (already existing contact) | Not relevant | Not relevant | Remove contact from the group |
| Yes (contact created by group lead) | No (fully inactive) | No (just added contact to his group) | Delete contact |
| No (fully inactive) | Yes | Reassign tickets in the future to the group lead and delete the contact | |
| Yes | Not relevant | Contact is kept as is |
Getting started
Better filtering of information displayed to the group lead
To benefit from these improvements, you have to set the configuration key config.friendsAndFamily.GDPR.hideGroupMemberInfo to true.
...
| Warning | ||
|---|---|---|
| ||
In order to cope with the Privacy by default principle required by many data privacy regulations, this new behaviour will become mandatory during 2025. More precisely, after delivery of release 2025 V2 (July 2025), this behaviour will be enabled by default with no way to disable it. |
Removal/anonymization of group members that haven't given their consent
To use this feature, create an additional schedule for the anonymisation batch using the parameters illustrated in section above.