Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GDPR using zero1-gdpr extension // how do we anonymize data ?? #683

Closed
seansan opened this issue Apr 5, 2018 · 8 comments
Closed

GDPR using zero1-gdpr extension // how do we anonymize data ?? #683

seansan opened this issue Apr 5, 2018 · 8 comments

Comments

@seansan
Copy link
Contributor

seansan commented Apr 5, 2018

We use zero GDPR extension. To date the only solution for GDPR in magento 1.x.
Problem:
If customer requests data removal then we can do this
If no orders: account is deleted
If orders, then account is anonimized + all allowed data is erased (we cant even find it)
The problem is that the email is required: so this email address is anonimized (changed) + the user is unsubscribed from any newsletters

Problem=> changing the email never arrives in Mailchimp

This is a problem because we "officially" did not remove all the customers data: I mean I can find his email in mailchimp. So we are not compliant with GDPR and this is a real issue.

Important
To support this case: one could execute all the above steps manually to achieve the same result. The problem is that the mail address change never reaches Mailchimp: and personal data can still be found even when someone executed his right to removal of data

Option 1: Add ability to support change of email address: then the change of email arrives and combined with the anonimization of the email => we are compliant +++ this is the best solution because we dont want to loose the sales data

Option 2: create some kind of special event that the mailchimp extension watches and removes all data from mailchimp

Preconditions

  1. use https://marketplace.magento.com/zero1-zero1-gdpr.html
  2. or do the above steps manually
  3. customers requests complete! data removal
  4. we anonimize account, remove non essential data, change email, unsubscribe from newsletter
    5 save

Steps to reproduce

See above

Expected result

Customer unbsubscribed
Email address changed (to randomness)

Actual result

Customer unbsubscribed
Email address NOT changed

@Santiagoebizmarts
Copy link
Contributor

Hello @seansan

This is something that is not allowed at MailChimp side of things. Email addresses cannot be changed.
It is not extension-related, therefore there is nothing we can do here.
You can see the issue about the email address change at #17
Any additional information about GDPR can be added at #449

Regards.

@seansan
Copy link
Contributor Author

seansan commented Apr 5, 2018 via email

@Santiagoebizmarts
Copy link
Contributor

@seansan
Please note this will not be lost because I added links to both issues related.
Now in those issues there is a notification showing a link to this one. Since github does not allow issue merging, this is the closest thing we can do.

We cannot allow multiple issues related to the same subject, it would make it hard to keep up with what needs to be done.

Regards.

@seansan
Copy link
Contributor Author

seansan commented Apr 6, 2018 via email

@seansan
Copy link
Contributor Author

seansan commented Apr 6, 2018

in code this is issued, can we hang something on the delete() action??? Should delete not remove a customer from mailchimp anyways?

if ($subscriber->getId()) { $subscriber->unsubscribe(); $subscriber->delete(); }

@seansan
Copy link
Contributor Author

seansan commented Apr 7, 2018 via email

@mailchimp mailchimp deleted a comment from stevensagaar May 2, 2018
@Santiagoebizmarts
Copy link
Contributor

Hello @stevensagaar
Have you tested this? I don't think this extension is compatible with ours.
I don't see anywhere in the description about it calling our export event.

Regards.

@stevensagaar
Copy link

@Santiagoebizmarts Yes I have tested this and it says on their FAQ section as well

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants