SAM targeting: Automatic filtering of contacts who didn't give their explicit consent
Since release Whymper V1, SAM (SecuTix Audience Management) filters out automatically all contacts that refuse explicitly marketing communications (except if the campaign contains only "operational" (and non-marketing) information directly related to contractual obligations towards the customers, for instance informing them about major changes affecting an event for which they ave purchased tickets). In this case, you must select the campaign type called "Information directly related to a contact's purchase or reservation".
In order to be fully compliant with GDPR regulations, release Whymper V3 of SAM will filter out automatically all contacts that did not give their explicit consent. As a result, as of mid-November 2018, contacts who have not provided any consent information (neither positive, nor negative) will not receive your marketing campaigns anymore.
Several improvements have been brought to SecuTix during Whymper V2 regarding the new General Data Protection Regulation (GDPR). These improvements aim at:
- Improving the flexibility of the bulk contact anonymization batch
- Improving the information provided to the operators and internet users with regard to the data privacy policy
Batch facility improvement for anonymization/deletion of inactive contacts
Contact inactivity period calculation
The batch process calculates the inactivity period by checking the date of the last transaction for a contact. This data is held in a special indicator (calculated directly by the batch process) called the GDPR recency. This recency covers:
- Option acquisition
- Option confirmation
- Reservations and sales made, either as a purchase contact or a cultural contact. Completing payment does not, therefore, modify the contact recency.
- Being added to the waiting list
- (since Whymper 1.7) explicit click on a SAM link
- (since Whymper 1.7) modification of contact criterion
- (since Whymper 1.7) modification of contact authorizations, if at least one authorization is still "yes, I authorize"
- If the contact has not carried out any of the above actions, the contact creation date is used.
- All those information are taken into account at the institution level (through all its organizations). Therefore, a contact will not be anonymized if there was an activity with another organization as the one running the batch.
The indicator then refers to the validity date of dated products and the order date of undated products.
Comments:
- In order to maintain performance levels, the indicator is only recalculated if a contact is eligible for deletion or anonymization, given the current value of the indicator and the chosen period of inactivity. It does not necessarily provide the complete contact recency.
For example: A contact has purchased a ticket for a performance taking place on the 15th of June 2018. The initial batch process runs and sets the indicator to the 15th of June. A few weeks later, the contact purchases a ticket for a performance on 1st of September 2018. Assuming the batch was executed on the 1st of August after the purchase of the second ticket, the second batch process will not update the contact recency as it is too recent to be anonymized. - The batch anonymization process only deals with individual contacts and relays but not the structures themselves, nor contacts with another role, e.g., supplier, guide, exhibitor, producer, partner, contractor.
Removing a prospect / anonymizing a contact
- When a contact is anonymized, through a batch or manually by an operator, country, town and post code are kept. Allowing the reports on the geographical origin to remain accurate. The other address information are deleted so that the identity of the anonymized contact cannot be recovered. When a prospect is removed, all address information are deleted.
- All beneficiary information (except the country) and all answers to questions of type Address or Email linked to tickets which end validity is older than the duration specified in the batch are removed.
- The IP address of all orders containing only tickets which end validity is older than the duration mentioned above is removed.
You can select the minimum period of inactivity. The batch process has a default setting of 36 months, which corresponds to the recommended 3-year period in France. The batch process also offers a simulation mode, which displays the list of contacts about to be anonymized/deleted. Since this batch process will have a considerable and irreversible impact on your contact database, we strongly recommend you run in simulation mode first in order to identify all affected contacts. No contact who is a debtor or creditor to your institution may be anonymized. These contacts will be included in the run-time log. They will be anonymized when the batch process runs and their transaction has been settled.
How to use this new batch process
- Create a batch type "Deletion/anonymization of inactive contacts" (If it does not exist yet)
- Schedule the program "Deletion/anonymization of inactive contacts". By default, the period of inactivity is set to 36 months and on a simulation mode.
Information for internet users
"Contact creation on behalf"
SecuTix allows internet users to create contacts and integrate them to their community. By performing this action the users will be allowed to buy tickets for a member of their community.
If the internet user requests a login for any member of his community, the new community member will receive an email and all required information about data privacy policy. However, SecuTix cannot inform the new community member if no login has been created for him. In order to comply with GDPR regulations , a legal mention has been added to the "contact creation on behalf" page.
The purpose of legal mention is to urge the internet user , who created the contact, to inform the community member newly created about his rights regarding his personal data. The content of this legal mention is provided underneath:
When you share third party information (identity, contact details etc.) you undertake to have notified these third parties and, if necessary, obtained their consent for the processing of personal data when using our services and specifically with regard to achieving the purposes of management and monitoring of reservations and the ordering of tickets, creating and promoting communities, or managing our contact relations in general even carrying out communications and marketing activities for them. You also guarantee to us that you have brought to the attention of these third parties, the methods and characteristics relating to the processing of their data, the recipients of their data and the length of time their data will be kept etc. as well as details relating to their rights under the laws relating to the protection of personal data to which they are entitled and, in general, all the mandatory information which features in our "data protection policy", which you may read. |
|---|
Data privacy policy summary explicitly shown to the internet user
The ticketshop provides now two links to the data privacy policy that can be set up in the parameters of the point of sales
- Confidentiality guarantee: This parameter already exists in the previous releases of SecuTix. It contains a URL to your complete data privacy policy. This URL is displayed as a link on the Ticket Shop. The internet user has to click on this link to display the complete data privacy policy.
- Data privacy policy summary explicitly shown to the contact: This is a new parameter provided in Whymper V2. It contains a URL to a summary of your data privacy policy. This summary is directly displayed on the contact creation page of the Ticket Shop. The internet user won't have to click on a link to view it.
SecuTix recommands to create both pages (complete data privacy policy and summary) and to enter the respective URLs in above parameters.
Information for operators
Creation/modification of order remarks
SecuTix already provides information to the operator when he enters a contact notes or remarks, alerting the operator about the requirements on the remarks content defined by the data privacy regulations. This principle has now been extended to order remarks.
Request buyer's consent when saving the credit card alias for further payments
A message is displayed to the operator to ensure he has requested the buyer's consent before saving the credit card alias for further payments.
Data privacy legal obligations when exporting data
The operator is informed about his legal obligations when exporting a report from the reporting tool or from SAM.
Information for administrators
The login (connection code) of an operator cannot be modified or removed when this operator leaves your company. As a result, it's important that the identity of the operator cannot be discovered from his login. To achieve this, a message is displayed to the administrator to recall this requirement. Note that the operator first name and last name should be anonymized manually when the operator leaves your company.