Their customers can shop Phone Number Database anonymously in the supermarket. But if the customer wants a customer discount, he must request a customer card and have it scanned at the checkout of his shopping. This creates a data relationship in which the supermarket collects the customer's personal data, data about his shopping behavior (online and offline, date of purchase, location, average purchase Phone Number Database amount, products, repeat purchases, etc.) and stores it for as long as the supermarket itself wishes. And used for a long time for marketing purposes (newsletters, retargeting.
This data relationship, in which Phone Number Database power now rests more with the supermarket than with the customer, will therefore change in 2018. See also this previously mentioned article by Paul Lempers . How can you best arrange the data relationship under the GDPR? Option 1: Arrange nothing The customer and or Phone Number Database company do not arrange anything. So every time the prospect or customer visits a website or webshop, the (potential) customer will have to fill in a questionnaire in which you arrange all Phone Number Database mutual consents. Hope hassles on both sides. Option 2: Take an account with an identity provider.
The customer takes out an Phone Number Database account with an identity provider. The customer creates several identity profiles and chooses one of the following options (in fact he logs in as he can now log in with his Facebook or Twitter account), but then via the independent identity provider, for example Schlüss): Customer logs in Phone Number Database with identity layer data profile, for example only name and email. Customer logs in with identity means data profile, for example name, e-mail, name and address and payment details. Customer logs in with identity high data profile, for example with name, e-mail, name and address, payment details and permission to collect data omnichannel and store it for 6 months.