| Table of Contents |
|---|
The General Data Protection Regulation (GDPR) is the key European standard with regard to the protection of personal data. It strengthens and harmonises data protection for individuals in the European Union. It will come into force on 25 May 2018.
...
- Prospects (contacts who have never bought or benefited from a ticket) are deleted.
- Contacts who have bought or benefited from a ticket are anonymised. This operation cannot be reversed. Operators are no longer able to view the history of this contact nor to access it for any reason whatsoever. Only SecuTix support personnel may recover information about this contact from logs. After the log information is deleted (this information is kept for a year), the information about this contact is irretrievably deleted. It may no longer be accessed, even by support.
- Beneficiaries (the first name and surname of a ticket holder are taken without creating an actual contact) are not anonymised. In practice, this information is used to enhance security (e.g. to identify all spectators at a match) and may not be used for marketing purposesalso anonymised.
New batch facility for anonymisation/deletion of inactive contacts
...
- 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
- (as of Whymper 1.7) explicit click on a SAM link
- (as of Whymper 1.7) modification of contact criterion
- (as of 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.
...
- In order to maintain performance levels, the indicator is only recalculated if a contact is eligible for deletion or anonymisation, 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 15 June 2018. The initial batch process runs and sets the indicator to 15 June. A few weeks later, the contact purchases a ticket for a performance on 1 September 2018. Suppose the batch was executed on 1 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 anonymised.
- The batch anonymisation process only deals with individual contacts and relays and not the structures themselves nor contacts with another role (eg, supplier, guide, exhibitor, producer, partner, contractor)
...
- If it does not yet exist, create a batch type "Deletion/anonymisation of inactive contacts"
- Schedule the following program function "Deletion/anonymisation of inactive contacts". By default, the period of inactivity is initially set to 36 months and simulation mode is chosen.
- If you don't find the mentioned batch type or function in the dropdowns, please ask our service team to activate these options
A contact's right to access their own data
...
- Use your best operational endeavours to minimise the number of contacts who have neither given their express agreement nor confirmed their wish to opt out.
- Specifically remove all contacts who have not given their explicit consent. SecuTix intends to widen the scope of automatic filtering in this contact category in a later version.
Marketing campaign "Explicit Consent Renewal"
Thanks to SAM, you can easily setup a marketing campaing targetted to contacts who will soon be anonymized.
Simply follow those steps:
- on your website, create a page (let's name it "consent renewal page") saying, for example, "Thank you for your continued interest! Data Privacy is of high concern to us and we'll only contact you if you accept to and with relevant information..."
- execute the Contact Anonymisation Batch IN SIMULATION MODE, with a delay of XX months (eg, 24)
- create a SAM Target filtering on contact indicator "GDPR Recency" and set a date (format "YYYYMMDD") XX months in the past (it corresponds to last activity of this contact), eg in this example, 3 years ago from today:
- create a SAM campaing with a text similar to "Hello <firstname>, we've not seen you from a long time, if you want to continue hearing from us, simply click this <link>" with <link> pointing to your "consent renewal page" (created at step 1)
- then, when the contact will click on the link, SAM will track this click and as exposed above, this action will be taken care in the GDPR recency indicator and is considered as an activity