Aa a general principle, data privacy legislations impose that a person only sees the personal data he needs to carry out his tasks. Applied to the Friends & Family feature, this means that the group lead should only see the information needed to carry out his tasks, like paying the group member's reservation. Several small adaptations have been brought to the content of Ticket Shop pages to stick more tightly to this data privacy principle.
Solution
This section describes the group member's personal information that a group lead can't see anymore, even if the group member has given his consent. Note that an internet user will still see his own files and orders as before.
List of friends and family
The group lead doesn't see anymore the email address of the group members.
Although Becky Smith has given her consent to be a member of the group, the group lead doesn't see her email address.
Payment of a reservation performed by a group member
Selection of a delivery method
When the group lead pays a reservation performed by a group member, he will be able to reuse the shipment mode selected by the group member during the reservation.
In example above, the group lead simply reuses the postal shipment selected by the group member. This means that the tickets will be shipped to the group member without disclosing the group member's postal address to the group lead. The group lead may still decide to get the tickets by selecting another shipment mode. Only by selecting the first shipment mode displayed, the tickets will be shipped to the group member.
Order summary displayed during order finalisation (order payment)
If the shipment contact (in our case: the group member) is different from the payer contact (in our case: the group lead), only the delivery method is displayed.
File summary and content (select a file from the order history)
The Print file summary button has been removed from the File summary section to avoid the disclosure of personal data (for example postal address) displayed on the file summary document.
The group lead will only see the delivery contact (first name and last name of the group member) but he won't see any email or postal address.
The button in the change history to print the order summary has been removed since the order summary displays some personal data like the postal address.
Removal/anonymization of group members that haven't given their consent
S-360 now provides you the ability to clean up the contacts that haven't given their consent after a duration of your choice. To achieve this, a new option has been added to the already existing anonymisation batch, as illustrated below:
The result of the anonymisation process is summarised in table below:
| 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.
This new behaviour will become mandatory during 2025!
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.