GDRP: revoke consent process | Community
Skip to main content
A
Anonymous
April 10, 2018
Question

GDRP: revoke consent process

  • April 10, 2018
  • 3 replies
  • 3709 views

Hi guys,

We are working in how we can proceed when a user request the revoke consent of their data. So is Marketo implementing a feature (if not done yet), to obfuscate a record or set it as read-only or similar?

The idea goes beyond that only mark it as unsubscribed, but to set it disabled or read-only.

Thank you!

Regards,

Raul

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

3 replies

Grégoire_Miche2
Grégoire_Miche2
Level 10
April 10, 2018

The response to this is not obfuscation or read only, it's anonymization. When someone asks to be removed, you really need to be able to remove any way to recognize that person, so making it read-only is not good enough. Obfuscation or deletion would have the drawback to also remove the data from all reports.

See here: , including @Dan Stevens' links to some articles.

-Greg

Dan_Stevens_
Dan_Stevens_
Level 10
April 10, 2018

And as far as I know, Marketo isn't working on any new features to help us become more GDPR compliant by May 25 (most of their engineers are tied up in working on the new UX).  Instead, it's up to each customer to create the customizations, processes, etc. required for compliance.

    A
    Anonymous
    April 10, 2018

    thanks guys for the quick responses, but regarding to this request, what are you guys doing?

    Thank you!

    Nicholas_Manojl
    Nicholas_Manojl
    Level 8
    April 10, 2018

    Delete person from Marketo flow step.

      Grégoire_Miche2
      Grégoire_Miche2
      Level 10
      April 11, 2018

      Agreed with Nicholas, if you cannot anonymize, you will have to delete it. Keeping the data, even "read only" is a breach of the regulation.

      -Greg

      Terms & ConditionsAccessibility statement

      Loading footer...