...
| Group lead has created contact | Group lead has booked or bought tickets on behalf of group member | Contact has performed some action since he received the consent email | Result |
|---|---|---|---|
| No (already existing contact) | No (just added contact to his group) | No (fully inactive) | Remove contact from the group |
| Yes (has performed some other action like buying some tickets but didn't give his consent) | Remove contact from the group | ||
| Yes | No (fully inactive) | Remove contact from the group and reassign ticket to group lead | |
| Yes (has performed some other action like buying some tickets but didn't give his consent) | Remove contact from the group and reassign ticket to group lead | ||
| Yes (contact created by group lead) | No (just added contact to his group) | No (fully inactive) | |
| Yes (has performed some other action like buying some tickets but didn't give his consent) | |||
| Yes | No (fully inactive) | ||
| Yes (has performed some other action like buying some tickets but didn't give his consent) |
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.